PR_26177_OWNER_007-project-instructions-single-source-eod-lock#218
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 174c3407e3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. 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".
| - `docs_build/dev/bundle_readme.md` (delete) | ||
| - `docs_build/dev/validation_checklist.txt` (delete) | ||
| - `docs_build/dev/dod/tool_ui_readiness_dod.md` (move to root archive) | ||
| - `docs_build/dev/roadmaps/MASTER_ROADMAP_ENGINE.md` (move to root archive) |
There was a problem hiding this comment.
Moving docs_build/dev/roadmaps/MASTER_ROADMAP_ENGINE.md to the archive leaves active repo consumers pointing at the deleted path. I checked the published npm script check:phase24-closeout-guard, which reads docs_build/dev/toolbox/checkPhase24CloseoutExecutionGuard.baseline.json, and it now exits with Roadmap path missing: docs_build/dev/roadmaps/MASTER_ROADMAP_ENGINE.md; the top-level README and docs_build/operations/dev/ROADMAP_GUARDRAILS.md also still treat this path as the active roadmap. Any local/CI closeout validation or onboarding link that uses those active references will fail until the guard/docs are updated to the new path or the roadmap remains in its active location.
Useful? React with 👍 / 👎.
|
|
||
| ## Active Source | ||
|
|
||
| `docs_build/dev/ProjectInstructions/` is the only active Project Instructions source. |
There was a problem hiding this comment.
With this line making docs_build/dev/ProjectInstructions/ the only active source and the old root PROJECT_INSTRUCTIONS.md deleted, any rule that was not copied into this tree becomes inactive. I checked the active ProjectInstructions tree (excluding archived history) for several previously mandatory sections such as TOOL STATUS GOVERNANCE, PLAYWRIGHT DEPTH AND COVERAGE REQUIREMENT, and HTML FILE RESTRICTIONS, and found no replacements, so future tool/runtime PRs lose those gates despite this being a consolidation rather than a policy removal. Please migrate or link the existing rules before deprecating the old file.
Useful? React with 👍 / 👎.
| - `docs_build/dev/PROJECT_INSTRUCTIONS.md` (delete) | ||
| - `docs_build/dev/PROJECT_MULTI_PC.txt` (delete) |
There was a problem hiding this comment.
Deleting these root instruction files leaves existing queued work orders under docs_build/pr/ pointing at paths that no longer exist. I checked active PR docs outside archives/reports and found examples such as docs_build/pr/PR_26171_042-idea-board-navigation-fallback-cleanup/BUILD_PR.md still telling Codex to use both docs_build/dev/PROJECT_INSTRUCTIONS.md and docs_build/dev/PROJECT_MULTI_PC.txt; running those work orders now starts with missing source-of-truth files. Please either keep compatibility stubs or update the queued PR docs to the new docs_build/dev/ProjectInstructions/ paths before removing the old files.
Useful? React with 👍 / 👎.
2 participants
PR_26177_OWNER_007-project-instructions-single-source-eod-lock
Date: 2026-06-26
Branch: PR_26177_OWNER_007-project-instructions-single-source-eod-lock
Scope: Project Instructions single-source governance, EOD main lock, branch lifecycle governance, docs_build/dev root cleanup, Tool MVP stacked PR governance, no-mock runtime source governance, and legacy docs archiving
Status: PASS
Summary
Legacy Docs Archived
Moved verified old/superseded DoD material:
Moved verified old/superseded roadmap material:
Folders:
No Mock Repository Runtime Source
Added governance:
Validation
Artifact