electron-rare/Kill_LIFE
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add frontend-backend route parity gate pattern (cross-repo) #1

New Issue
Closed
opened 2026-02-20 22:26:57 +00:00 by electron-rare · 8 comments
electron-rare commented 2026-02-20 22:26:57 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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

  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.
## 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.
electron-rare commented 2026-02-20 22:27:36 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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.

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.
electron-rare commented 2026-02-20 22:50:19 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Additional concrete case:

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.
electron-rare commented 2026-02-20 23:13:26 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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.

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.
electron-rare commented 2026-02-20 23:18:08 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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.

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.
electron-rare commented 2026-02-20 23:18:26 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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 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.
electron-rare commented 2026-02-20 23:21:01 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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: 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.
electron-rare commented 2026-02-20 23:26:43 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Update coordination:

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.
electron-rare commented 2026-02-21 01:18:25 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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.
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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
electron (Clément Saillant)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: electron-rare/Kill_LIFE#1
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?