Add multi-team merge authority governance - PR_26171_046-multi-team-merge-authority

Author: ToolboxAid

docs_build/dev/PROJECT_INSTRUCTIONS.md

@@ -2009,6 +2009,16 @@ Required Git workflow report fields:
 - merge result
 - final main commit
 
+## OWNER-CONTROLLED STABLE AND MERGE APPROVAL
+
+Stable promotion and merge approval are owner-controlled.
+
+Rules:
+- Codex may prepare scoped changes, reports, validation evidence, ZIP artifacts, branches, and PRs.
+- Codex must not merge a PR or mark a workstream stable without explicit approval from the assigned Team Alpha or Team Beta owner.
+- Master Control may recommend sequencing or assignment, but affected workstream owners control stable and merge approval.
+- This targeted section supersedes older automatic-merge wording when approval ownership is in question.
+
 ## CODEX INSTRUCTION ENFORCEMENT START GATE
 
 Codex must run this gate before every PR execution and before any file changes.
@@ -2017,7 +2027,7 @@ Required instruction reads:
 - Read `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
 - Read `docs_build/dev/PROJECT_MULTI_PC.txt`.
 - Treat the newest applicable section in `PROJECT_INSTRUCTIONS.md` as authoritative when rules overlap.
-- Treat the current owner/parity section in `PROJECT_MULTI_PC.txt` as authoritative for PC/Laptop routing.
+- Treat the current owner/parity section in `PROJECT_MULTI_PC.txt` as authoritative for Team Alpha / Team Beta routing.
 
 Required pre-change report:
 - Codex must report instruction compliance as `PASS` or `FAIL` before making file changes.
@@ -2027,7 +2037,7 @@ Required pre-change report:
 Hard stops before changes:
 - If the current branch is not `main`, HARD STOP.
 - If the repository is not clean before the PR branch is created, HARD STOP.
-- If the PR owner does not match the PC/Laptop ownership map in `PROJECT_MULTI_PC.txt`, HARD STOP.
+- If the PR owner does not match the Team Alpha / Team Beta ownership map in `PROJECT_MULTI_PC.txt`, HARD STOP.
 - If the PR number parity does not match the assigned machine in `PROJECT_MULTI_PC.txt`, HARD STOP.
 - If the PR asks for implementation and the implementation path is wrong, HARD STOP.
 - If a PR asks for functional parity and only placeholder-only work is possible, HARD STOP and report the missing source or blocker.

docs_build/dev/PROJECT_MULTI_PC.txt

@@ -11,7 +11,7 @@ Naming governance
 Workflow governance
 Environment strategy
 PR sequencing
-Merge approval
+Stable and merge approval
 
 It should never build code and never own implementation details.
 
@@ -22,12 +22,12 @@ Requirements
 Acceptance Criteria
 Dependencies
 Priority
-Owner (PC/Laptop)
+Owner (Team Alpha / Team Beta)
 Recommended Workstream Split
 
 Instead of arbitrary splits, split by Creator journey.
 
-PC — Creator Journey
+Team Alpha — Creator Journey
 
 Owns:
 
@@ -57,7 +57,7 @@ Reason:
 
 These tools are heavily connected.
 
-Laptop — Content Creation
+Team Beta — Content Creation
 
 Owns:
 
@@ -85,7 +85,7 @@ These tools share asset pipelines and publishing workflows.
 
 Messages Tool Placement
 
-I would move Messages to Laptop ownership.
+I would move Messages to Team Beta ownership.
 
 Reason:
 
@@ -191,7 +191,7 @@ Immediate Queue
 
 If we start using Master Control today, my queue would be:
 
-PC
+Team Alpha
 PR_26171_001-game-journey-completion-model
 
 Scope:
@@ -205,7 +205,7 @@ Sounds [17]
 
 This solves the "xxx%" problem.
 
-Laptop
+Team Beta
 PR_26171_002-messages-tool-foundation
 
 Scope:
@@ -282,7 +282,7 @@ Not developer.
 
 ---
 
-## PC Chat
+## Team Alpha Chat
 
 Give it ownership of a workstream.
 
@@ -309,7 +309,7 @@ it keeps building in that area.
 
 ---
 
-## Laptop Chat
+## Team Beta Chat
 
 Give it a different workstream.
 
@@ -371,13 +371,13 @@ So I'd keep IST mostly as infrastructure work and focus development on tool comp
 Master Control should assign ownership:
 
 ```text
-PC
+Team Alpha
   Game Journey
   Game Hub
   Publish
   Share
 
-Laptop
+Team Beta
   Audio
   MIDI
   Events
@@ -405,7 +405,7 @@ feature/game-hub
 feature/progress-tracking
 ```
 
-Never have both PCs working in the same tool at the same time.
+Never have both teams working in the same tool at the same time.
 
 ---
 
@@ -418,19 +418,19 @@ For example, in Master Control you can ask:
 ```text
 Given everything we know about GFS:
 
-What should PC build next?
-What should Laptop build next?
+What should Team Alpha build next?
+What should Team Beta build next?
 
 Generate the next PR for each.
 ```
 
 Then Master Control outputs:
 
 ```text
-PC:
+Team Alpha:
 PR_26171_002-game-hub-progress
 
-Laptop:
+Team Beta:
 PR_26171_003-messages-tool-mvp
 ```
 
@@ -457,17 +457,17 @@ Codex must read this file before every PR execution.
 
 Machine parity:
 
-PC / Environment 1:
+Team Alpha / Environment 1:
 - Uses even-numbered PR sequence values.
 - Example: `PR_26171_064-*`.
 
-Laptop / Environment 2:
+Team Beta / Environment 2:
 - Uses odd-numbered PR sequence values.
 - Example: `PR_26171_063-*`.
 
 Owner map:
 
-PC / Environment 1 owns Creator Journey work:
+Team Alpha / Environment 1 owns Creator Journey work:
 - Game Journey
 - Game Hub
 - Idea
@@ -483,7 +483,7 @@ PC / Environment 1 owns Creator Journey work:
 - Game Design
 - Game Crew
 
-Laptop / Environment 2 owns Content Creation and asset/publishing work:
+Team Beta / Environment 2 owns Content Creation and asset/publishing work:
 - Graphics
 - Toolbox images
 - Audio
@@ -501,8 +501,12 @@ Governance, recovery, diagnostics, and instruction-hardening PRs:
 - Must not implement tool/runtime work from the opposite owner.
 - Must document owner/parity compliance in the PR report.
 
+Stable and merge approval:
+- Stable promotion and merge approval are controlled by the assigned Team Alpha or Team Beta owner.
+- Master Control may recommend sequencing, but Codex must not merge or mark stable without explicit owner approval for the affected workstream.
+
 Hard stop rules:
 - If the PR number parity does not match the current machine, stop before changes.
 - If the PR scope belongs to the other machine owner, stop before changes.
-- If the PR crosses PC and Laptop ownership, stop and require Master Control to split or assign the work.
+- If the PR crosses Team Alpha and Team Beta ownership, stop and require Master Control to split or assign the work.
 - If the requested implementation path conflicts with the active owner path, stop before changes.

docs_build/dev/reports/codex_changed_files.txt

@@ -1,54 +1,5 @@
-PR_26171_044-idea-board-game-hub-project-flow
-
-Changed files:
-- docs_build/pr/PR_26171_044-idea-board-game-hub-project-flow/PLAN_PR.md
-- docs_build/pr/PR_26171_044-idea-board-game-hub-project-flow/BUILD_PR.md
-- docs_build/pr/PR_26171_044-idea-board-game-hub-project-flow/APPLY_PR.md
-- docs_build/dev/reports/codex_review.diff
-- docs_build/dev/reports/codex_changed_files.txt
-- src/dev-runtime/persistence/tool-repositories/game-workspace-mock-repository.js
-- tests/playwright/tools/GameWorkspaceMockRepository.spec.mjs
-- tests/playwright/tools/IdeaBoardTableNotes.spec.mjs
-- tests/playwright/tools/ToolboxRoutePages.spec.mjs
-- toolbox/game-workspace/game-workspace.js
-- toolbox/game-workspace/index.html
-- toolbox/idea-board/index.html
-- toolbox/idea-board/index.js
-
-Requirement PASS evidence:
-- PASS: Create Project appears only for Ready ideas. Evidence: Idea Board actions remain Edit/Create Project/Delete for Ready rows and switch to Open in Game Hub/Archive after creation in targeted Playwright.
-- PASS: Create Project uses the shared Game Hub project contract. Evidence: Idea Board calls the existing game-workspace server repository client createGame method; Playwright asserts the createGame repository request occurs.
-- PASS: Create Project sets Idea status to Project. Evidence: targeted Playwright asserts the row status becomes Project.
-- PASS: Project ideas and notes are read-only. Evidence: targeted Playwright asserts no Edit/Delete/Add Note/note actions remain for the Project row.
-- PASS: Project row actions are Open in Game Hub and Archive. Evidence: targeted Playwright asserts exact action labels.
-- PASS: Project ideas cannot be edited or deleted while Project. Evidence: Project rows do not render Edit/Delete actions and deletion guard remains active.
-- PASS: Project ideas cannot add/edit/delete notes. Evidence: expanded Project notes render without Add Note or note actions.
-- PASS: Archived ideas remain hidden by default and show Restore/Delete when visible. Evidence: targeted Playwright archives, shows Archived through the filter, and asserts Restore/Delete.
-- PASS: Game Hub shows creator-facing Project Information. Evidence: Game Hub HTML/JS replaces internal record display with Project Information and targeted Game Hub Playwright passes.
-- PASS: Game Hub shows read-only Source Idea fields. Evidence: Idea Board-to-Game Hub Playwright asserts Idea, Pitch, and Notes from the source idea render in Game Hub.
-- PASS: Game Hub avoids internal IDs, DB/API/mock/debug/seed wording in creator-facing display. Evidence: touched runtime files pass creator-visible text scan and targeted Playwright checks the navigated Game Hub main content.
-- PASS: Open in Game Hub navigates to the related project. Evidence: targeted Playwright waits for /toolbox/game-workspace/index.html?game=lantern-reef-* and asserts the linked project renders.
-- PASS: No Game Journey expansion beyond existing link/reference. Evidence: implementation does not add Game Journey creation or new journey wiring.
-
-Validation evidence:
-- PASS: node --check toolbox/idea-board/index.js
-- PASS: node --check toolbox/game-workspace/game-workspace.js
-- PASS: node --check toolbox/game-workspace/game-workspace-api-client.js
-- PASS: node --check src/dev-runtime/persistence/tool-repositories/game-workspace-mock-repository.js
-- PASS: node --check tests/playwright/tools/IdeaBoardTableNotes.spec.mjs
-- PASS: node --check tests/playwright/tools/ToolboxRoutePages.spec.mjs
-- PASS: node --check tests/playwright/tools/GameWorkspaceMockRepository.spec.mjs
-- PASS: npx playwright test tests/playwright/tools/IdeaBoardTableNotes.spec.mjs --project=playwright --workers=1 --reporter=line
-- PASS: npx playwright test tests/playwright/tools/ToolboxRoutePages.spec.mjs --project=playwright --workers=1 --reporter=line --grep "Idea Board launches"
-- PASS: npx playwright test tests/playwright/tools/GameWorkspaceMockRepository.spec.mjs --project=playwright --workers=1 --reporter=line --grep "Game Hub"
-- PASS: npm run test:workspace-v2
-- PASS: git diff --check
-
-Git workflow:
-- Current branch: codex/pr-26171-044-idea-board-game-hub-project-flow
-- Created branch: codex/pr-26171-044-idea-board-game-hub-project-flow
-- Commit hash: 2a38796f81aae2dceb4151095b8f89a276cd2d32
-- Push result: pushed to origin/codex/pr-26171-044-idea-board-game-hub-project-flow
-- PR URL: https://github.com/ToolboxAid/HTML-JavaScript-Gaming/pull/22
-- Merge result: to be reported after merge
-- Final main commit: to be reported after returning to main and pulling latest
+docs_build/dev/PROJECT_INSTRUCTIONS.md
+docs_build/dev/PROJECT_MULTI_PC.txt
+docs_build/dev/reports/codex_review.diff
+docs_build/dev/reports/codex_changed_files.txt
+docs_build/dev/reports/team_alpha_beta_owner_approval_report.md