Cette PR formalise une spécification orchestrateur pour le backlog WebUI/API sur RTC, afin de stabiliser la coordination et l'exécution des issues ouvertes.
Avoir une source de vérité exécutable avant d'ouvrir des PR d'implémentation pour #10/#11.
## Contexte
Cette PR formalise une spécification orchestrateur pour le backlog WebUI/API sur RTC, afin de stabiliser la coordination et l'exécution des issues ouvertes.
Issues couvertes:
- #10 (couverture WebUI des routes backend)
- #11 (gate CI de parité routes WebUI/backend)
## Contenu
- Ajout de la spec: `docs/spec_webui_route_parity_and_coverage_v1.md`
- Index docs mis à jour: `docs/README.md`
## Ce que la spec fixe
- périmètre in/out,
- exigences fonctionnelles (parity gate + coverage UI),
- exigences non fonctionnelles,
- plan de livraison en phases,
- critères d'acceptation et artefacts de preuve,
- coordination cross-repo (Kill_LIFE + Zacus).
## Pourquoi
Avoir une source de vérité exécutable avant d'ouvrir des PR d'implémentation pour #10/#11.
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
### 💡 Codex Review
Here are some automated review suggestions for this pull request.
**Reviewed commit:** `4e75899208`
<details> <summary>ℹ️ About Codex in GitHub</summary>
<br/>
[Your team has set up Codex to review pull requests in this repo](http://chatgpt.com/codex/settings/general). Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
</details>
This spec anchors cross-repo coordination to le-mystere-professeur-zacus#94, but the companion artifact provided for this change is Zacus PR #96; keeping the old issue reference here makes reviewers and release tracking follow the wrong thread when validating parity evidence and DoD updates. Please update this line to the actual companion PR so the orchestrator spec remains a reliable source of truth.
Useful? React with 👍 / 👎.
**<sub><sub></sub></sub> Point companion link to the active Zacus PR**
This spec anchors cross-repo coordination to `le-mystere-professeur-zacus#94`, but the companion artifact provided for this change is Zacus PR #96; keeping the old issue reference here makes reviewers and release tracking follow the wrong thread when validating parity evidence and DoD updates. Please update this line to the actual companion PR so the orchestrator spec remains a reliable source of truth.
Useful? React with 👍 / 👎.
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.
Contexte
Cette PR formalise une spécification orchestrateur pour le backlog WebUI/API sur RTC, afin de stabiliser la coordination et l'exécution des issues ouvertes.
Issues couvertes:
Contenu
docs/spec_webui_route_parity_and_coverage_v1.mddocs/README.mdCe que la spec fixe
Pourquoi
Avoir une source de vérité exécutable avant d'ouvrir des PR d'implémentation pour #10/#11.
Cross-repo companion spec:\n- Zacus PR: https://github.com/electron-rare/le-mystere-professeur-zacus/pull/96\n\n@codex review
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:
4e75899208ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
@@ -0,0 +96,4 @@## 8. Coordination inter-repos- Pattern source: `Kill_LIFE` PR #2 (route parity gate pattern).- Companion Zacus: issue `le-mystere-professeur-zacus#94`.This spec anchors cross-repo coordination to
le-mystere-professeur-zacus#94, but the companion artifact provided for this change is Zacus PR #96; keeping the old issue reference here makes reviewers and release tracking follow the wrong thread when validating parity evidence and DoD updates. Please update this line to the actual companion PR so the orchestrator spec remains a reliable source of truth.Useful? React with 👍 / 👎.