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

Adopt static frontend/backend route parity gate in CI #12

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

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:

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

Duplicate of #11 (same route-parity CI objective). Keeping #11 as the canonical RTC tracking issue.

Duplicate of #11 (same route-parity CI objective). Keeping #11 as the canonical RTC tracking issue.
electron-rare commented 2026-02-20 23:19:17 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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.

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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 codex
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/RTC_BL_PHONE#12
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?