Add a lightweight gate/checklist pattern in Kill_LIFE for "Frontend route map vs backend exposed API" to prevent UI regressions caused by endpoint drift.
Why
In RTC_BL_PHONE, the static Web UI drifted from firmware HTTP routes and called removed/non-existent endpoints.
A dedicated route-parity check would have caught this before release.
Maintain canonical backend route list (generated or documented source-of-truth).
Validate frontend route usage against this list (static check).
Fail CI if unknown/removed routes are referenced.
Attach route-parity artifact in evidence pack.
Done criteria
Runbook snippet added to Kill_LIFE docs/workflows or standards.
Minimal script example added (grep/static extraction + diff).
Mentioned in evidence pack checklist.
## Proposal
Add a lightweight gate/checklist pattern in Kill_LIFE for "Frontend route map vs backend exposed API" to prevent UI regressions caused by endpoint drift.
## Why
In RTC_BL_PHONE, the static Web UI drifted from firmware HTTP routes and called removed/non-existent endpoints.
A dedicated route-parity check would have caught this before release.
## Cross-repo references
- RTC fix PR: https://github.com/electron-rare/RTC_BL_PHONE/pull/7
- RTC interop baseline PR (merged): https://github.com/electron-rare/RTC_BL_PHONE/pull/5
- Zacus coordination issue: https://github.com/electron-rare/le-mystere-professeur-zacus/issues/90
## Suggested gate content
1. Maintain canonical backend route list (generated or documented source-of-truth).
2. Validate frontend route usage against this list (static check).
3. Fail CI if unknown/removed routes are referenced.
4. Attach route-parity artifact in evidence pack.
## Done criteria
- [ ] Runbook snippet added to Kill_LIFE docs/workflows or standards.
- [ ] Minimal script example added (grep/static extraction + diff).
- [ ] Mentioned in evidence pack checklist.
This confirms route-parity drift is a real regression class worth gating.
Cross-repo update:
The concrete RTC case referenced in this issue is now merged:
- https://github.com/electron-rare/RTC_BL_PHONE/pull/7
This confirms route-parity drift is a real regression class worth gating.
This further supports the need for a route-parity gate plus route inventory artifact in evidence packs.
Additional concrete case:
- RTC follow-up PR for web route expansion is open: https://github.com/electron-rare/RTC_BL_PHONE/pull/8
This further supports the need for a route-parity gate plus route inventory artifact in evidence packs.
Cross-repo status update (2026-02-20):\n- RTC follow-up merged: https://github.com/electron-rare/RTC_BL_PHONE/pull/9\n- Zacus coordination PR merged: https://github.com/electron-rare/le-mystere-professeur-zacus/pull/92\n\nThe route-parity gate proposal in this issue remains relevant as a preventive CI pattern. Keeping this issue open for implementation in Kill_LIFE.
Implementation PR opened for this proposal:\n- https://github.com/electron-rare/Kill_LIFE/pull/2\n\nIt adds the static route-parity gate script, runbook usage snippet, and evidence/compliance checklist references.
L'approche est volontairement simple (regex statique sur endpoints) pour bloquer vite les divergences UI/API.
Suggestion Kill_LIFE: reprendre le même gate de cohérence routes si/quant une WebUI API est exposée, pour garder la triade RTC/Zacus/Kill_LIFE alignée.
Update coordination cross-repo:
- RTC a maintenant une PR de gate de parité routes WebUI/backend: https://github.com/electron-rare/RTC_BL_PHONE/pull/13
- L'approche est volontairement simple (regex statique sur endpoints) pour bloquer vite les divergences UI/API.
Suggestion Kill_LIFE: reprendre le même gate de cohérence routes si/quant une WebUI API est exposée, pour garder la triade RTC/Zacus/Kill_LIFE alignée.
Le pattern est prêt à être repris dans Kill_LIFE quand la surface API web sera stabilisée.
Update: le gate RTC route-parity est maintenant mergé.
- PR: https://github.com/electron-rare/RTC_BL_PHONE/pull/13
- Commit: d2925d2521e095f7653ff0f589be721711923707
Le pattern est prêt à être repris dans Kill_LIFE quand la surface API web sera stabilisée.
Le check gère désormais les appels imbriqués type Promise.all([...requestJson(...)...]).
Si vous reprenez le gate côté Kill_LIFE, partez sur cette version corrigée.
Update coordination:
- RTC a mergé la correction parser route-parity: https://github.com/electron-rare/RTC_BL_PHONE/pull/15
- Le check gère désormais les appels imbriqués type `Promise.all([...requestJson(...)...])`.
Si vous reprenez le gate côté Kill_LIFE, partez sur cette version corrigée.
Le pattern de gate parité frontend/backend est ajouté dans:
tools/gates/route_parity_check.py
zeroclaw_dual_orchestrator.yml et docs/specs associées.
Résolu via PR #2 (merge commit 42c0702).
Le pattern de gate parité frontend/backend est ajouté dans:
- `tools/gates/route_parity_check.py`
- `zeroclaw_dual_orchestrator.yml` et docs/specs associées.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Proposal
Add a lightweight gate/checklist pattern in Kill_LIFE for "Frontend route map vs backend exposed API" to prevent UI regressions caused by endpoint drift.
Why
In RTC_BL_PHONE, the static Web UI drifted from firmware HTTP routes and called removed/non-existent endpoints.
A dedicated route-parity check would have caught this before release.
Cross-repo references
Suggested gate content
Done criteria
Cross-repo update:
The concrete RTC case referenced in this issue is now merged:
This confirms route-parity drift is a real regression class worth gating.
Additional concrete case:
This further supports the need for a route-parity gate plus route inventory artifact in evidence packs.
Cross-repo status update (2026-02-20):\n- RTC follow-up merged: https://github.com/electron-rare/RTC_BL_PHONE/pull/9\n- Zacus coordination PR merged: https://github.com/electron-rare/le-mystere-professeur-zacus/pull/92\n\nThe route-parity gate proposal in this issue remains relevant as a preventive CI pattern. Keeping this issue open for implementation in Kill_LIFE.
Implementation PR opened for this proposal:\n- https://github.com/electron-rare/Kill_LIFE/pull/2\n\nIt adds the static route-parity gate script, runbook usage snippet, and evidence/compliance checklist references.
Update coordination cross-repo:
Suggestion Kill_LIFE: reprendre le même gate de cohérence routes si/quant une WebUI API est exposée, pour garder la triade RTC/Zacus/Kill_LIFE alignée.
Update: le gate RTC route-parity est maintenant mergé.
Le pattern est prêt à être repris dans Kill_LIFE quand la surface API web sera stabilisée.
Update coordination:
Promise.all([...requestJson(...)...]).Si vous reprenez le gate côté Kill_LIFE, partez sur cette version corrigée.
Résolu via PR #2 (merge commit
42c0702).Le pattern de gate parité frontend/backend est ajouté dans:
tools/gates/route_parity_check.pyzeroclaw_dual_orchestrator.ymlet docs/specs associées.