Strengthen Product Owner testable governance

Author: ToolboxAid

docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md

@@ -37,7 +37,7 @@ Codex responses must include:
 ## Tool MVP PR Report Requirements
 
 Every tool MVP PR report must include:
-- Creator-testable outcome
+- Product Owner testable outcome
 - What Playwright tests
 - What Mr. Q should manually test
 - Whether the PR is part of a stacked MVP sequence
@@ -50,7 +50,7 @@ The report must answer:
 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.
+If a tool MVP PR has no Playwright lane, the report must state why and list the manual Product Owner validation instead.
 
 ## Code Change Reporting
 

docs_build/dev/ProjectInstructions/addendums/no_mock_repository_runtime_source.md

@@ -20,7 +20,7 @@ Browser -> API -> Database
 ## Rules
 
 - Mock repositories are 100% technical debt.
-- "Mock repository ready" is not a valid Creator-testable completion state.
+- "Mock repository ready" is not a valid Product Owner testable completion state.
 - Page arrays are not product-data sources of truth.
 - JSON source files are not product-data sources of truth.
 - `/tmp` files are not product-data sources of truth.
@@ -38,7 +38,7 @@ If a temporary mock repository exists for transition, it must be documented as t
 - affected files
 - removal PR
 - replacement API/DB path
-- Creator-testable limitation
+- Product Owner testable limitation
 
 Temporary mock repositories do not make a feature complete. They may only document a transition state.
 
@@ -52,4 +52,4 @@ Completion requires Game Configuration data to load through:
 Browser → API → Database
 ```
 
-The Creator-testable completion state must prove that browser-visible Game Configuration data was read back through the API/service contract backed by the database.
+The Product Owner testable completion state must prove that browser-visible Game Configuration data was read back through the API/service contract backed by the database.

docs_build/dev/ProjectInstructions/addendums/pr_workflow.md

@@ -143,14 +143,14 @@ 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.
+For tool MVPs, use one large Codex command, multiple focused stacked PRs, and one Product Owner testable 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
+- Product Owner testable outcome
 - What Playwright tests
 - What Mr. Q should manually test
 - Whether the PR is part of a stacked MVP sequence
@@ -161,15 +161,29 @@ Visible acceptance must be Creator-facing first. Architecture can be handled und
 
 ## Product Owner Testable Definition
 
-A request to complete a page, tool, or testable MVP means Product Owner testable.
+A request to complete a page, tool, MVP, or testable experience means Product Owner testable by default. Codex must deliver a working Product Owner testable feature, not a shell or foundation page, unless the Product Owner explicitly requests a shell/foundation PR.
+
+A Product Owner testable outcome means the Product Owner can:
+
+- open the page/tool
+- perform the primary workflow
+- save/load data where applicable
+- observe expected results
+- validate success and failure states
+- follow manual validation steps from the PR report
 
 Not acceptable as a completed/testable page or tool:
 
 - shell-only page
+- route-only page
+- navigation-only PR
+- template-only page
+- placeholder controls
+- static table with no workflow
 - `Not implemented yet`
+- `coming soon`
 - placeholder-only workspace, inspector, or output sections
 - planned-only tile
-- template-only page
 - route that loads but cannot be used
 
 Required for Product Owner testable completion:
@@ -182,6 +196,10 @@ Required for Product Owner testable completion:
 - manual validation steps for Product Owner
 - targeted Playwright coverage where impacted.
 
+## No-Shell Completion Rule
+
+A PR requested to complete a page, tool, MVP, or testable experience must not stop after route creation, shell creation, placeholder UI, static mock layout, or navigation activation unless the Product Owner explicitly requested a shell/foundation PR.
+
 ## OWNER Shortcut: PRs
 
 Keyword:

docs_build/dev/ProjectInstructions/addendums/test_structure_standardization.md

@@ -34,7 +34,7 @@ Regression tests:
 - Tool tests validate tool functionality.
 - Regression tests validate platform behavior.
 - New tests follow the canonical structure.
-- Every user-accessible page must have at least one page-level Playwright test.
+- Every user-accessible page must have at least one matching page-level Playwright test before it can be considered complete.
 - Runtime page path determines the page-level Playwright test path.
 - Primary page-level Playwright test file should be `index.spec.mjs`.
 - Do not organize new page-level Playwright tests only by feature nickname or technology bucket when a page path exists.
@@ -56,6 +56,8 @@ Minimum page-level test:
 - page renders
 - navigation works
 - no visible placeholder-only state for completed/testable pages
+- primary workflow is covered where the PR claims Product Owner testable completion
+- save/load and validation are covered where applicable
 - no runtime console errors when feasible
 
 Additional scenario files may use:

docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md

@@ -12,15 +12,15 @@ Define how Codex plans and executes Creator-facing tool MVP work without creatin
 For tool MVPs, use:
 
 ```text
-One large Codex command -> multiple focused stacked PRs -> each PR has a testable Creator outcome.
+One large Codex command -> multiple focused stacked PRs -> each PR has a Product Owner testable 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 produce a Product Owner testable outcome.
 - Each PR must answer:
 
 ```text
@@ -40,15 +40,29 @@ 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.
 
-A request to complete a page, tool, or testable MVP means Product Owner testable.
+A request to complete a page, tool, MVP, or testable experience means Product Owner testable by default. Codex must deliver a working Product Owner testable feature, not a shell or foundation page, unless the Product Owner explicitly requests a shell/foundation PR.
+
+A Product Owner testable outcome means the Product Owner can:
+
+- open the page/tool
+- perform the primary workflow
+- save/load data where applicable
+- observe expected results
+- validate success and failure states
+- follow manual validation steps from the PR report
 
 Not acceptable as complete/testable:
 
 - shell-only page
+- route-only page
+- navigation-only PR
+- template-only page
+- placeholder controls
+- static table with no workflow
 - `Not implemented yet`
+- `coming soon`
 - placeholder-only workspace, inspector, or output sections
 - planned-only tile
-- template-only page
 - route that loads but cannot be used
 
 Required for Product Owner testable completion:
@@ -62,7 +76,7 @@ Required for Product Owner testable completion:
 - targeted Playwright coverage where impacted.
 
 Each tool MVP PR must state:
-- Creator-testable outcome
+- Product Owner testable outcome
 - What Playwright tests
 - What Mr. Q should manually test
 - Whether the PR is part of a stacked MVP sequence
@@ -71,6 +85,8 @@ Each tool MVP PR must state:
 
 ## Runtime Data Completion Boundary
 
+A PR requested to complete a page, tool, MVP, or testable experience must not stop after route creation, shell creation, placeholder UI, static mock layout, or navigation activation unless the Product Owner explicitly requested a shell/foundation PR.
+
 A PR outcome must not be described as complete if the visible data is coming from:
 
 - mock repositories

docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment.md

@@ -24,6 +24,9 @@ No runtime code, UI code, API code, database code, start_of_day files, history s
   - The rule applies to all teams: OWNER, Team Alfa, Team Bravo, Team Charlie, Team Delta, and any future team.
   - `main` is only the SOD baseline and EOD return target unless OWNER approves a merge checkpoint.
 - Added Product Owner testable completion definition.
+- Replaced validation/completion-gate `Creator-testable` wording with Product Owner testable wording while preserving product-facing Creator language where appropriate.
+- Added the no-shell completion rule for page/tool/MVP requests.
+- Strengthened page-level Playwright completion gates for primary workflows, save/load, and validation coverage where applicable.
 - Confirmed `Browser -> API -> Database`, one API/service contract across environments, and `Local API` as the shared API running locally.
 - Added page-path Playwright organization rules and examples.
 - Fixed active team registry mismatch in `TEAM_ASSIGNMENTS.md`.
@@ -42,7 +45,8 @@ No runtime code, UI code, API code, database code, start_of_day files, history s
 - PASS: no active instruction permits direct PR commits to `main`.
 - PASS: EOD/main-return wording is clarified as closeout or OWNER-approved merge checkpoint, not between stacked/sequential PRs.
 - PASS: Product Owner testable definition exists.
-- PASS: page-level Playwright organization exists.
+- PASS: shell/template/navigation-only completion is explicitly disallowed unless requested by Product Owner.
+- PASS: page-level Playwright completion gate exists.
 - PASS: API/environment wording is consistent.
 - PASS: active registry and assignment table agree for current Delta active assignment.
 

docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_manual-validation-notes.md

@@ -9,7 +9,10 @@ Date: 2026-06-26
 - Confirm stacked/sequential PR branches/commits stay on the active team branch/workstream during the day.
 - Confirm this branch workflow applies to all teams: OWNER, Team Alfa, Team Bravo, Team Charlie, Team Delta, and any future team.
 - Confirm Product Owner testable excludes shell-only, placeholder-only, planned-only, or route-only completion.
+- Confirm Product Owner testable means the Product Owner can open the page/tool, perform the primary workflow, save/load where applicable, observe expected results, validate success/failure states, and follow PR-report manual steps.
+- Confirm page/tool/MVP completion PRs cannot stop at route creation, shell creation, placeholder UI, static mock layout, or navigation activation unless Product Owner requested a shell/foundation PR.
 - Confirm page-level Playwright tests follow runtime page paths.
+- Confirm page-level Playwright completion gates cover primary workflows and save/load/validation where applicable.
 - Confirm `Local API` means the shared API running locally.
 - Confirm Team Charlie owns Sprites canvas editor MVP.
 - Confirm Sprites planning requires canvas/grid editor, width/height controls, Palette/Colors-only reusable colors, pixel painting, API/database save/load, and Product Owner manual validation.

docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_requirements-checklist.md

@@ -8,6 +8,10 @@ Date: 2026-06-26
 | Daily branch workflow documented | PASS | Added SOD/day-work/EOD wording. |
 | Branch workflow is team-neutral | PASS | Active wording says work commits and sequential PR branches/commits stay on the active team branch/workstream and applies to all teams. |
 | Product Owner testable definition documented | PASS | Added in PR workflow and Tool MVP standard. |
+| Ambiguous Creator-testable completion wording replaced | PASS | Completion/validation gates now use Product Owner testable wording; product-facing Creator language is preserved. |
+| No-shell PR rule added | PASS | Completion requests may not stop at routes, shells, placeholder UI, static mock layouts, or navigation activation unless explicitly requested. |
+| Product Owner testable outcome definition expanded | PASS | Defines opening the page/tool, primary workflow, save/load where applicable, expected results, success/failure states, and PR-report manual steps. |
+| Page-level Playwright completion gate strengthened | PASS | Requires matching page-level tests before completion, including primary workflow and save/load/validation where applicable. |
 | API/environment rule confirmed | PASS | Added `Browser -> API -> Database`, shared API contract, and Local API definition. |
 | Page-level Playwright organization added | PASS | Added runtime path to test path rules and examples. |
 | Active team registry consistency fixed | PASS | `TEAM_ASSIGNMENTS.md` now matches the active registry for Delta assignment. |

docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_validation-lane.md

@@ -9,7 +9,8 @@ Date: 2026-06-26
 git diff --check
 git diff --name-only
 rg -n "Always return to main before starting the next PR|Sprite Studio V2" docs_build/dev/ProjectInstructions
-rg -n "Product Owner testable|page-level Playwright|Browser -> API -> Database|Local API" docs_build/dev/ProjectInstructions
+rg -n "Creator-testable|testable Creator outcome|manual Creator validation" docs_build/dev/ProjectInstructions
+rg -n "Product Owner testable|no-shell|route-only page|static table with no workflow|page-level Playwright|primary workflow is covered|Browser -> API -> Database|Local API" docs_build/dev/ProjectInstructions
 ```
 
 ## Results
@@ -20,8 +21,11 @@ rg -n "Product Owner testable|page-level Playwright|Browser -> API -> Database|L
 - PASS: no `Sprite Studio V2` active backlog owner remains.
 - PASS: no OWNER-only branch workflow wording remains.
 - PASS: active branch workflow says commits and sequential PR branches/commits stay on the active team branch/workstream.
+- PASS: no `Creator-testable`, `testable Creator outcome`, or `manual Creator validation` completion-gate wording remains.
+- PASS: Product Owner testable outcome definition includes primary workflow, save/load where applicable, expected results, success/failure states, and PR-report manual steps.
+- PASS: no-shell completion rule exists.
 - PASS: Product Owner testable text exists.
-- PASS: page-level Playwright organization text exists.
+- PASS: page-level Playwright completion gate includes primary workflow and save/load/validation coverage where applicable.
 - PASS: API/environment contract text exists.
 
 ## Playwright

docs_build/dev/reports/codex_changed_files.txt

@@ -1,10 +1,9 @@
-docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md
-docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md
+docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md
+docs_build/dev/ProjectInstructions/addendums/no_mock_repository_runtime_source.md
 docs_build/dev/ProjectInstructions/addendums/pr_workflow.md
-docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md
+docs_build/dev/ProjectInstructions/addendums/test_structure_standardization.md
 docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md
 docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment.md
-docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_branch-validation.md
 docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_manual-validation-notes.md
 docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_requirements-checklist.md
 docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_validation-lane.md