Store artifact report in docs/evidence or CI artifact
Fail gate only when frontend routes are missing in backend set
Done criteria
Workflow step added
Report artifact produced
One successful CI run linked in issue
Cross-link to Zacus follow-up
Cross-repo
Zacus companion issue should mirror this pattern for Freenove WebUI endpoints.
## Context
Route drift caused web regressions earlier and required follow-up fixes (PR #7, PR #9).
Kill_LIFE now has a generic static gate script pattern:
- PR: https://github.com/electron-rare/Kill_LIFE/pull/2
- Script: `tools/gates/route_parity_check.py`
## Proposal
Integrate a route-parity check in RTC CI for web UI + firmware backend routes.
## Suggested implementation
- Run parity check against:
- backend: `src/**/*.cpp`, `src/**/*.h`
- frontend: `data/webui/**/*.js`, `data/webui/**/*.html`
- Store artifact report in docs/evidence or CI artifact
- Fail gate only when frontend routes are missing in backend set
## Done criteria
- [ ] Workflow step added
- [ ] Report artifact produced
- [ ] One successful CI run linked in issue
- [ ] Cross-link to Zacus follow-up
## Cross-repo
- Zacus companion issue should mirror this pattern for Freenove WebUI endpoints.
Update coordination: côté Zacus, la parité endpoints Web réseau est mergée via PR #95 (https://github.com/electron-rare/le-mystere-professeur-zacus/pull/95). On peut maintenant avancer sur le gate de parité de routes sans bloquer l’intégration firmware.
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.
Context
Route drift caused web regressions earlier and required follow-up fixes (PR #7, PR #9).
Kill_LIFE now has a generic static gate script pattern:
tools/gates/route_parity_check.pyProposal
Integrate a route-parity check in RTC CI for web UI + firmware backend routes.
Suggested implementation
src/**/*.cpp,src/**/*.hdata/webui/**/*.js,data/webui/**/*.htmlDone criteria
Cross-repo
Duplicate of #11 (same route-parity CI objective). Keeping #11 as the canonical RTC tracking issue.
Update coordination: côté Zacus, la parité endpoints Web réseau est mergée via PR #95 (https://github.com/electron-rare/le-mystere-professeur-zacus/pull/95). On peut maintenant avancer sur le gate de parité de routes sans bloquer l’intégration firmware.