Add project status control plane#2
Merged
Merged
Conversation
…nto codex/project-status-control-plane
Owner
Author
|
Cross-platform verification is now complete. Verification:
Final run: https://github.com/brendohxd/Project-Relay/actions/runs/29680296480 The canonical roadmap now records Linux verification as done and leaves human review as the only M1 blocker. Pages publication is planned after merge. |
brendohxd
marked this pull request as ready for review
July 19, 2026 09:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
project/status.jsonand generatedSTATUS.mddocs/Why
Project Relay needed one inspectable source of truth for implementation progress. This makes the current M1 blockers and later phases visible without mixing ITSM scientific claims into the Relay repository.
Boundary and impact
The ITSM card exposes operational readiness only. Equations, claims, datasets, results, manuscripts, evidence classifications, and scientific acceptance remain in the separate ITSM canon.
The system remains local-first, credential-free, and read-only. Publishing GitHub Pages is deliberately left blocked until Pages is configured and the account-level Actions restriction is resolved.
Validation
npm run checkReview notes
This is a stacked draft PR targeting
codex/m1-local-vertical-slice. Review the status vocabulary, milestone ordering, ITSM boundary, and whether the M1 blockers match the intended acceptance gate before merge.