Add Tool MVP stacked PR standard

Author: ToolboxAid

docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md

@@ -56,6 +56,8 @@ Existing Project Instructions outside `docs_build/dev/ProjectInstructions/` rema
 
 `docs_build/dev/ProjectInstructions/addendums/koti_layout_contract.md` defines the King of the Iceberg layout data contract.
 
+`docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md` defines the Creator-facing stacked PR standard for tool MVP work.
+
 ## Single Source and Main Lock Governance
 
 `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` defines the single active Project Instructions source, canonical START / WORK / END branch lifecycle, EOD main lock, next-day reset, team branch creation gate, daily synchronization baseline, and mandatory hard stops.

docs_build/dev/ProjectInstructions/README.txt

@@ -59,3 +59,4 @@ Addendum index:
 - Workspace V2 Playwright Gate: docs_build/dev/ProjectInstructions/addendums/workspace_v2_playwright_gate.md
 - Samples2Tools Adapter Guidance: docs_build/dev/ProjectInstructions/addendums/samples2tools_adapter_guidance.md
 - King of the Iceberg Layout Contract: docs_build/dev/ProjectInstructions/addendums/koti_layout_contract.md
+- Tool MVP Stacked PR Standard: docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md

docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md

@@ -34,6 +34,24 @@ Codex responses must include:
 - Merge commit(s)
 - Validation results
 
+## Tool MVP PR Report Requirements
+
+Every tool MVP PR report must include:
+- Creator-testable outcome
+- What Playwright tests
+- What Mr. Q should manually test
+- Whether the PR is part of a stacked MVP sequence
+- Previous PR dependency
+- Next PR dependency
+
+The report must answer:
+
+```text
+What can Mr. Q test after applying this ZIP?
+```
+
+If a tool MVP PR has no Playwright lane, the report must state why and list the manual Creator validation instead.
+
 ## Code Change Reporting
 
 When a ZIP is uploaded, report executable code changes only.

docs_build/dev/ProjectInstructions/addendums/pr_workflow.md

@@ -118,6 +118,28 @@ For governance, documentation, and administrative work, use Batch Governance Mod
 
 Use stacked sequential PRs only when dependency order requires it.
 
+## Tool MVP Stacked PRs
+
+Tool MVP work must follow:
+
+`docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md`
+
+For tool MVPs, use one large Codex command, multiple focused stacked PRs, and one testable Creator outcome per PR.
+
+Do not create one giant PR.
+
+Do not stop after every small PR unless blocked by branch state, failed validation, missing source files, Project Instructions conflict, or an unresolved dependency from a prior PR.
+
+Each tool MVP PR plan or template must include:
+- Creator-testable outcome
+- What Playwright tests
+- What Mr. Q should manually test
+- Whether the PR is part of a stacked MVP sequence
+- Previous PR dependency
+- Next PR dependency
+
+Visible acceptance must be Creator-facing first. Architecture can be handled under the covers, but the PR purpose must be user-testable.
+
 ## OWNER Shortcut: PRs
 
 Keyword:

docs_build/dev/ProjectInstructions/addendums/release_gate.md

@@ -44,6 +44,7 @@ The release gate should confirm these files when relevant to the PR:
 - `docs_build/dev/ProjectInstructions/addendums/workspace_v2_playwright_gate.md`
 - `docs_build/dev/ProjectInstructions/addendums/samples2tools_adapter_guidance.md`
 - `docs_build/dev/ProjectInstructions/addendums/koti_layout_contract.md`
+- `docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md`
 - `docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md`
 - `docs_build/dev/admin-notes/Installs required.txt` when present
 - `docs_build/dev/admin-notes/Table layout.txt` when present

docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md

@@ -0,0 +1,70 @@
+# Tool MVP Stacked PR Standard
+
+Status: Approved
+Owner: OWNER
+
+## Purpose
+
+Define how Codex plans and executes Creator-facing tool MVP work without creating one giant PR or stopping after every small PR.
+
+## Standard
+
+For tool MVPs, use:
+
+```text
+One large Codex command -> multiple focused stacked PRs -> each PR has a testable Creator outcome.
+```
+
+## Rules
+
+- Do not create one giant PR.
+- Do not stop after every small PR unless blocked.
+- Each PR must be independently scoped.
+- Each PR must produce a Creator-testable outcome.
+- Each PR must answer:
+
+```text
+What can Mr. Q test after applying this ZIP?
+```
+
+- Codex must continue through the stacked PR sequence unless blocked by:
+  - branch state
+  - failed validation
+  - missing source files
+  - Project Instructions conflict
+  - unresolved dependency from a prior PR
+
+## Creator-Facing Acceptance
+
+For tool MVP PR planning, visible acceptance must be Creator-facing first.
+
+Architecture can be handled under the covers, but PR purpose must be user-testable.
+
+Each tool MVP PR must state:
+- Creator-testable outcome
+- What Playwright tests
+- What Mr. Q should manually test
+- Whether the PR is part of a stacked MVP sequence
+- Previous PR dependency
+- Next PR dependency
+
+## Hitboxes MVP Example Stack
+
+Example Hitboxes MVP stack:
+
+- PR 1: Creator can open the tool and choose a real/test object.
+- PR 2: Creator can see the object and draw a rectangle hitbox.
+- PR 3: Creator can move/resize/save/reload hitboxes.
+- PR 4: Creator can test Object A vs Object B collision.
+- PR 5: Creator can test speed/animation so fast objects do not skip collision.
+- PR 6: Polish and regression coverage.
+
+## Lifecycle Relationship
+
+Tool MVP stacks are explicitly documented stacked PR chains.
+
+Each PR in the stack still follows the canonical START / WORK / END lifecycle and must produce required reports and a repo-structured ZIP.
+
+When OWNER gives one large Codex command for a tool MVP stack, Codex may continue from one completed PR to the next without stopping for a conversational checkpoint, unless a blocker listed in this standard occurs.
+
+The final PR in the stack must perform normal closeout and stop all work after returning to synchronized main.

docs_build/dev/pr/BUILD_PR.md

@@ -18,6 +18,8 @@ This `docs_build/dev/pr/BUILD_PR.md`, `docs_build/dev/pr/PLAN_PR.md`, and the us
 - Move active governance/contract docs from `docs_build/dev/` root into `docs_build/dev/ProjectInstructions/addendums/`.
 - Move audit outputs from `docs_build/dev/` root into `docs_build/dev/reports/audits/`.
 - Delete stale one-off bundle metadata from `docs_build/dev/` root.
+- Add Tool MVP Stacked PR Standard under `docs_build/dev/ProjectInstructions/`.
+- Update PR planning/template and report requirements for tool MVP PRs.
 - Keep preserved historical ProjectInstructions material reference-only.
 - Keep `project-instructions/` out of this PR except for a tiny deprecated pointer.
 - Update active team start/governance docs to reference only `docs_build/dev/ProjectInstructions/`.
@@ -34,6 +36,7 @@ This `docs_build/dev/pr/BUILD_PR.md`, `docs_build/dev/pr/PLAN_PR.md`, and the us
 - `docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md`
 - `docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md`
 - `docs_build/dev/ProjectInstructions/addendums/*.md`
+- `docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md`
 - `docs_build/dev/reports/audits/*.md`
 - `project-instructions/README.md` (tiny deprecated pointer only)
 - `docs_build/dev/PROJECT_INSTRUCTIONS.md` (delete)
@@ -86,6 +89,7 @@ Test-Path docs_build/dev/css-audit.md
 Test-Path docs_build/dev/bundle_readme.md
 Test-Path docs_build/dev/validation_checklist.txt
 rg -n 'only active Project Instructions source|docs_build/dev/ProjectInstructions/' docs_build/dev/ProjectInstructions
+rg -n 'Tool MVP Stacked PR Standard|Creator-testable outcome|What can Mr\\. Q test after applying this ZIP|What Playwright tests|What Mr\\. Q should manually test|Previous PR dependency|Next PR dependency' docs_build/dev/ProjectInstructions
 rg -n 'docs_build/dev/PROJECT_INSTRUCTIONS.md.*source of truth|Codex must always read `docs_build/dev/PROJECT_INSTRUCTIONS.md`|Read `docs_build/dev/PROJECT_INSTRUCTIONS.md`' docs_build/dev/ProjectInstructions project-instructions
 git diff --name-status $(git merge-base HEAD origin/main) -- project-instructions
 git diff --name-status $(git merge-base HEAD origin/main) -- docs_build/dev/pr docs_build/dev/ProjectInstructions/addendums docs_build/dev/reports/audits

docs_build/dev/pr/PLAN_PR.md

@@ -13,6 +13,8 @@ Make `docs_build/dev/ProjectInstructions/` the only active Project Instructions
 - Move active governance/contract docs from `docs_build/dev/` root into `docs_build/dev/ProjectInstructions/addendums/`.
 - Move audit outputs from `docs_build/dev/` root into `docs_build/dev/reports/audits/`.
 - Delete stale one-off bundle metadata from `docs_build/dev/` root.
+- Add Tool MVP Stacked PR Standard under `docs_build/dev/ProjectInstructions/`.
+- Update PR planning/template and report requirements for tool MVP PRs.
 - Preserve historical ProjectInstructions-style sources only as deprecated reference material.
 - Keep `project-instructions/` out of the PR except for a tiny deprecated pointer.
 - Move active legacy addendums into `docs_build/dev/ProjectInstructions/addendums/`.
@@ -35,6 +37,8 @@ Make `docs_build/dev/ProjectInstructions/` the only active Project Instructions
 4. Confirm docs_build/dev root no longer contains active loose instruction, audit, contract, or PR files.
 5. Confirm moved active governance/contract docs are under `docs_build/dev/ProjectInstructions/addendums/`.
 6. Confirm moved audit outputs are under `docs_build/dev/reports/audits/`.
-7. Confirm EOD/Next Day and canonical START / WORK / END branch lifecycle rules appear in active governance docs.
-8. Confirm no product/runtime files changed.
-9. Run `git diff --check`.
+7. Confirm Tool MVP Stacked PR Standard appears in active ProjectInstructions.
+8. Confirm tool MVP PR template/report requirements include Creator-testable outcome, Playwright tests, Mr. Q manual test, stack membership, and previous/next dependency.
+9. Confirm EOD/Next Day and canonical START / WORK / END branch lifecycle rules appear in active governance docs.
+10. Confirm no product/runtime files changed.
+11. Run `git diff --check`.

docs_build/dev/reports/PR_26177_OWNER_007-project-instructions-single-source-eod-lock.md

@@ -2,7 +2,7 @@
 
 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, and docs_build/dev root cleanup
+Scope: Project Instructions single-source governance, EOD main lock, branch lifecycle governance, docs_build/dev root cleanup, and Tool MVP stacked PR governance
 Status: PASS
 
 ## Summary
@@ -16,11 +16,26 @@ Status: PASS
 - Moved active governance/contract root docs into docs_build/dev/ProjectInstructions/addendums/.
 - Moved audit outputs into docs_build/dev/reports/audits/.
 - Deleted stale one-off bundle metadata from docs_build/dev root.
+- Added docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md.
+- Updated PR workflow governance so tool MVP PR plans/templates include Creator-testable outcome, Playwright test scope, Mr. Q manual test scope, stacked MVP sequence membership, and previous/next PR dependencies.
+- Updated Codex artifact/reporting governance so every tool MVP PR report includes those same fields and answers what Mr. Q can test after applying the ZIP.
 - Corrected project-instructions/** scope so the PR only adds a tiny deprecated pointer README there.
 - Preserved project-instructions/addendums/** unchanged in the PR; unique current governance content is carried by docs_build/dev/ProjectInstructions/addendums/.
 - Confirmed docs_build/dev root no longer contains active loose instruction, audit, contract, or PR files.
 - No product/runtime, start_of_day, feature, or legacy SQLite file changes were made.
 
+## Tool MVP Stacked PR Standard
+
+Added governance:
+- One large Codex command -> multiple focused stacked PRs -> each PR has a testable Creator outcome.
+- No one giant PR.
+- No stopping after every small PR unless blocked.
+- Each PR is independently scoped and Creator-testable.
+- Each PR answers: What can Mr. Q test after applying this ZIP?
+- Codex continues through the stack unless blocked by branch state, failed validation, missing source files, Project Instructions conflict, or unresolved prior-PR dependency.
+- Visible acceptance for tool MVP planning is Creator-facing first.
+- Hitboxes MVP example stack is included.
+
 ## Moved To ProjectInstructions SSoT
 
 - docs_build/dev/workspace_v2_playwright_gate.md -> docs_build/dev/ProjectInstructions/addendums/workspace_v2_playwright_gate.md
@@ -68,22 +83,16 @@ Deleted stale one-off root files:
 - docs_build/dev/bundle_readme.md
 - docs_build/dev/validation_checklist.txt
 
-## Ambiguous Old Docs Handling
-
-- Reviewed loose root docs before moving or deleting them.
-- Moved active/contract content into docs_build/dev/ProjectInstructions/addendums/.
-- Moved one-off PR docs into docs_build/dev/pr/ instead of deleting them by filename.
-- Moved audit outputs into docs_build/dev/reports/audits/.
-- Removed project-instructions/addendums/** edits from the PR so old files remain historical reference, not a second active source.
-- Added only project-instructions/README.md as a tiny deprecated pointer to docs_build/dev/ProjectInstructions/.
-
 ## Validation
 
 - PASS: current branch is PR_26177_OWNER_007-project-instructions-single-source-eod-lock.
 - PASS: docs_build/dev root file list is empty after cleanup.
 - PASS: targeted path checks confirm duplicate root instruction files, moved root files, and listed stale one-off files are absent.
 - PASS: project-instructions/** PR diff is limited to project-instructions/README.md.
 - PASS: active moved governance/contract docs are indexed in docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md and README.txt.
+- PASS: Tool MVP Stacked PR Standard exists and includes required governance text.
+- PASS: PR workflow/template requirements include Creator-testable outcome, Playwright tests, Mr. Q manual test, stack membership, and previous/next dependency.
+- PASS: Codex report requirements include Creator-testable outcome, Playwright tests, Mr. Q manual test, stack membership, and previous/next dependency.
 - PASS: targeted grep found no active duplicate ProjectInstructions source-of-truth claim outside the active source.
 - PASS: targeted grep confirmed canonical lifecycle language appears in active governance docs.
 - PASS: product/runtime and start_of_day changed-file check returned no files.

docs_build/dev/reports/PR_26177_OWNER_007-project-instructions-single-source-eod-lock_branch-validation.md

@@ -6,6 +6,7 @@ Status: PASS
 - PASS: Branch is not main during WORK.
 - PASS: Worktree changes are scoped to governance/docs cleanup, reports, and the required delta artifact.
 - PASS: docs_build/dev root contains no loose files after moving PR docs, active addendums, and audit outputs.
+- PASS: Tool MVP Stacked PR Standard was added under docs_build/dev/ProjectInstructions/addendums/.
 - PASS: project-instructions/** is limited to a tiny deprecated pointer README in the PR diff.
 - PASS: No product/runtime files changed.
 - PASS: No start_of_day files changed.