Merge branch 'main' into pr/26172-OWNER-017-project-instructions-bootstrap-install

# Conflicts:
#	docs_build/dev/reports/codex_changed_files.txt
#	docs_build/dev/reports/codex_review.diff

Author: ToolboxAid

docs_build/dev/PROJECT_INSTRUCTIONS.md

@@ -2032,9 +2032,29 @@ 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.
+- OWNER 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.
 
+## OWNER GOVERNANCE LANE
+
+The governance lane formerly referred to by the prior governance token is now OWNER.
+
+Rules:
+- Use Team OWNER for owner-governance PRs going forward.
+- PR names use the OWNER token going forward:
+  - `PR_<YYJJJ>_OWNER_<###>-<short-description>`
+- Branch names mirror OWNER ownership going forward:
+  - `pr/<YYJJJ>-OWNER-<###>-<short-description>`
+- Existing PRs, branches, reports, and ZIPs already uploaded with the prior governance token are historical and must not be renamed unless separately scoped.
+- Required override wording is:
+  - `OWNER override approved: <reason>`
+
+OWNER follows the same safety rules:
+- One active OWNER branch at a time.
+- One active OWNER assignment at a time.
+- OWNER may override team locks, but may not silently delete, rewrite, or remove protected instructions.
+- OWNER override must be explicitly documented.
+
 ## CODEX INSTRUCTION ENFORCEMENT START GATE
 
 Codex must run this gate before every PR execution and before any file changes.

docs_build/dev/PROJECT_MULTI_PC.txt

@@ -1,8 +1,8 @@
 I think this is the right operating model for GFS at your current stage, with a few modifications to fit how we've already organized the project.
 
-Master Control Responsibilities
+OWNER Responsibilities
 
-Master Control should own:
+OWNER should own:
 
 Product roadmap
 Tool priority
@@ -189,7 +189,7 @@ These become valuable after creators can build complete games.
 
 Immediate Queue
 
-If we start using Master Control today, my queue would be:
+If we start using OWNER today, my queue would be:
 
 Team Alpha
 PR_26171_001-game-journey-completion-model
@@ -232,7 +232,7 @@ No TTS generation yet.
 
 This establishes the foundation for dialog, narration, and speech consistency across games.
 
-Master Control Rule
+OWNER Rule
 
 Before any new PR is created, ask:
 
@@ -257,7 +257,7 @@ until a complete game can be built start-to-finish entirely inside Game Foundry
 ----------------------------------------------------------------------------------------
 If your goal is **maximum throughput**, I would have the three chats play different roles.
 
-## Master Control
+## OWNER
 
 Don't build anything here.
 
@@ -336,7 +336,7 @@ it keeps building there.
 
 ---
 
-## What should Master Control focus on?
+## What should OWNER focus on?
 
 Right now, for GFS, I would prioritize:
 
@@ -368,7 +368,7 @@ So I'd keep IST mostly as infrastructure work and focus development on tool comp
 
 ### 2. Create Tool Ownership Map
 
-Master Control should assign ownership:
+OWNER should assign ownership:
 
 ```text
 Team Alpha
@@ -411,9 +411,9 @@ Never have both teams working in the same tool at the same time.
 
 ## What I can do
 
-I can help you turn Master Control into a scheduler.
+I can help you turn OWNER into a scheduler.
 
-For example, in Master Control you can ask:
+For example, in OWNER you can ask:
 
 ```text
 Given everything we know about GFS:
@@ -424,7 +424,7 @@ What should Team Beta build next?
 Generate the next PR for each.
 ```
 
-Then Master Control outputs:
+Then OWNER outputs:
 
 ```text
 Team Alpha:
@@ -438,7 +438,7 @@ You paste those into the two development chats.
 
 Both Codex sessions work simultaneously.
 
-Then when PRs come back, Master Control decides:
+Then when PRs come back, OWNER decides:
 
 ```text
 Merge
@@ -479,6 +479,25 @@ Historical examples:
 
 Owner map:
 
+Team OWNER owns owner-governance routing and explicit override decisions:
+- Product roadmap
+- Tool priority
+- Architecture
+- Naming governance
+- Workflow governance
+- Environment strategy
+- PR sequencing
+- Stable and merge approval recommendations
+- Team lock override decisions
+
+Team OWNER follows the same safety rules:
+- One active OWNER branch at a time.
+- One active OWNER assignment at a time.
+- OWNER may override team locks, but may not silently delete, rewrite, or remove protected instructions.
+- OWNER override must be explicitly documented.
+- Required override wording:
+  - `OWNER override approved: <reason>`
+
 Team Alpha owns Creator Journey work:
 - Game Journey
 - Game Hub
@@ -519,18 +538,26 @@ Team Gamma owns governance, recovery, diagnostics, and instruction-hardening wor
 - Static docs governance
 
 Governance, recovery, diagnostics, and instruction-hardening PRs:
-- Use the TEAM token assigned by Master Control.
+- Use the TEAM token assigned by OWNER.
+- OWNER governance PRs use the OWNER token going forward.
 - Must not implement tool/runtime work from the opposite owner.
 - Must document TEAM ownership compliance in the PR report.
 - Recovery reports must include TEAM ownership.
 
 Stable and merge approval:
 - Stable promotion and merge approval are controlled by the assigned Team Alpha, Team Beta, or Team Gamma owner.
-- Master Control may recommend sequencing, but Codex must not merge or mark stable without explicit owner approval for the affected workstream.
+- OWNER may recommend sequencing, but Codex must not merge or mark stable without explicit owner approval for the affected workstream.
+
+OWNER naming rule:
+- Use Team OWNER for owner-governance work going forward.
+- Use OWNER override wording going forward.
+- Required override wording is:
+  - `OWNER override approved: <reason>`
+- Existing uploaded PRs, branches, reports, and ZIPs with the prior governance token are historical and are not renamed by this rule unless separately scoped.
 
 Hard stop rules:
 - If the PR name does not include a TEAM token, stop before changes.
-- If the TEAM token does not match the owner map or explicit Master Control assignment, stop before changes.
+- If the TEAM token does not match the owner map or explicit OWNER assignment, stop before changes.
 - If the PR scope belongs to another TEAM owner, stop before changes.
-- If the PR crosses multiple team ownership areas, stop and require Master Control to split or assign the work.
+- If the PR crosses multiple team ownership areas, stop and require OWNER to split or assign the work.
 - If the requested implementation path conflicts with the active owner path, stop before changes.

docs_build/dev/reports/PR_26172_OWNER_010-owner-governance-rename-instruction-compliance-checklist.md

@@ -0,0 +1,13 @@
+# PR_26172_OWNER_010 Instruction Compliance Checklist
+
+- PASS: Read `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
+- PASS: Read `docs_build/dev/PROJECT_MULTI_PC.txt`.
+- PASS: Owner decision explicitly approved OWNER as the governance lane token going forward.
+- PASS: Branch name mirrors PR ownership: `pr/26172-OWNER-010-owner-governance-rename`.
+- PASS: Implementation path is active documentation only.
+- PASS: Existing uploaded MASTER-named ZIPs were not renamed.
+- PASS: Existing Project Instructions were updated only for the requested OWNER governance rename.
+- PASS: No runtime code changed.
+- PASS: No direct commit to `main`.
+- PASS: Required review artifacts are produced.
+- PASS: Required ZIP path is `tmp/PR_26172_OWNER_010-owner-governance-rename_delta.zip`.

docs_build/dev/reports/PR_26172_OWNER_010-owner-governance-rename-manual-validation-notes.md

@@ -0,0 +1,10 @@
+# PR_26172_OWNER_010 Manual Validation Notes
+
+- Confirmed branch was created from latest `main`.
+- Confirmed existing uploaded MASTER-named ZIPs were not renamed.
+- Confirmed active docs now define Team OWNER for owner-governance work going forward.
+- Confirmed required override wording is `OWNER override approved: <reason>`.
+- Confirmed OWNER safety rules are documented.
+- Confirmed no runtime/UI files changed.
+- Did not run Playwright because this is documentation-only.
+- Did not run samples.

docs_build/dev/reports/PR_26172_OWNER_010-owner-governance-rename.md

@@ -0,0 +1,28 @@
+# PR_26172_OWNER_010-owner-governance-rename
+
+## Scope
+
+Rename the owner-governance lane from the previous governance token to OWNER in active documentation.
+
+## Changes
+
+- Updated `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
+- Updated `docs_build/dev/PROJECT_MULTI_PC.txt`.
+- Replaced active `Master Control` wording with OWNER wording.
+- Added OWNER governance lane rules.
+- Added OWNER PR and branch naming rules going forward.
+- Added required override wording: `OWNER override approved: <reason>`.
+- Added OWNER safety rules for active branch, active assignment, protected instructions, and explicit documentation.
+- Preserved existing uploaded PRs, branches, reports, and ZIPs with prior names as historical artifacts.
+
+## Validation
+
+- `git diff --check`
+- Text check confirmed no active `Master Control`, `Team MASTER`, or `MASTER override` wording remains in active instruction files.
+- Text check confirmed `Team OWNER`, `OWNER override approved`, and OWNER safety rules exist.
+- Playwright skipped: documentation-only.
+- Samples skipped: not requested.
+
+## ZIP
+
+`tmp/PR_26172_OWNER_010-owner-governance-rename_delta.zip`

docs_build/dev/reports/codex_review.diff

@@ -760,3 +760,133 @@ index 000000000..0b63c376f
 +
 +Merge to main is EOD-only and owner-approved, unless the owner explicitly says:
 +"Merge this PR now."
+diff --git a/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install-instruction-compliance-checklist.md b/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install-instruction-compliance-checklist.md
+new file mode 100644
+index 000000000..af8e94480
+--- /dev/null
++++ b/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install-instruction-compliance-checklist.md
+@@ -0,0 +1,17 @@
++# PR_26172_OWNER_017 Instruction Compliance Checklist
++
++- [x] Read `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
++- [x] Read `docs_build/dev/PROJECT_MULTI_PC.txt`.
++- [x] OWNER override documented by user.
++- [x] Started from latest `main`.
++- [x] Created branch `pr/26172-OWNER-017-project-instructions-bootstrap-install`.
++- [x] Installed ProjectInstructions physical structure.
++- [x] Created required anchor files.
++- [x] Populated files with approved governance from OWNER PRs 001-016.
++- [x] Did not redesign governance.
++- [x] Did not create unrelated new governance.
++- [x] Did not delete existing documentation.
++- [x] Did not commit directly to `main`.
++- [x] Did not merge any PR.
++- [x] Ran docs/static validation.
++- [x] Created repo-structured delta ZIP.
+diff --git a/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install-manual-validation-notes.md b/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install-manual-validation-notes.md
+new file mode 100644
+index 000000000..4e7f24dd2
+--- /dev/null
++++ b/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install-manual-validation-notes.md
+@@ -0,0 +1,12 @@
++# PR_26172_OWNER_017 Manual Validation Notes
++
++- Verified branch was created from latest `main`.
++- Verified `docs_build/dev/ProjectInstructions/` did not exist on `main` before installation.
++- Verified required physical structure exists.
++- Verified required anchor files exist.
++- Verified installed files preserve approved ProjectInstructions governance content.
++- Verified active override wording uses OWNER.
++- Verified `BACKLOG_MASTER.md` filename remains preserved.
++- Verified no existing documentation was deleted.
++- Verified no runtime, UI, Playwright, or sample files changed.
++- Verified no merge to `main` was performed.
+diff --git a/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install-tree.txt b/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install-tree.txt
+new file mode 100644
+index 000000000..81c6d761b
+--- /dev/null
++++ b/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install-tree.txt
+@@ -0,0 +1,21 @@
++docs_build/dev/ProjectInstructions/
++|-- PROJECT_INSTRUCTIONS.md
++|-- README.txt
++|-- TEAM_START_COMMANDS.md
++|-- addendums/
++|   |-- build_path_sync.md
++|   |-- deprecation.md
++|   |-- multi_team.md
++|   |-- preservation.md
++|   |-- team_release_readiness.md
++|   `-- tile_overlay_status.md
++|-- archive/
++|   |-- README.md
++|   `-- history/
++|       `-- .gitkeep
++|-- backlog/
++|   `-- BACKLOG_MASTER.md
++|-- deprecation/
++|   `-- README.md
++`-- team_assignments/
++    `-- TEAM_ASSIGNMENTS.md
+diff --git a/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install.md b/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install.md
+new file mode 100644
+index 000000000..8ecbc95af
+--- /dev/null
++++ b/docs_build/dev/reports/PR_26172_OWNER_017-project-instructions-bootstrap-install.md
+@@ -0,0 +1,56 @@
++# PR_26172_OWNER_017-project-instructions-bootstrap-install
++
++## Purpose
++
++Install the missing ProjectInstructions operating system into the repository.
++
++This is an installation PR, not a governance-design PR.
++
++## Source
++
++The installed files use governance already approved across OWNER/Master-to-OWNER ProjectInstructions PRs 001-016:
++
++- ProjectInstructions root and README bootstrap
++- preservation and archive governance
++- backlog governance and Game Journey MVP population
++- team assignments and team registry
++- release readiness gate
++- team start commands
++- all-team Codex execution method
++- Day Work / EOD Merge rule
++- Build Path sync and tile overlay status governance
++- deprecation workflow
++- OWNER override and OWNER safety rules
++
++## Files Installed
++
++- `docs_build/dev/ProjectInstructions/README.txt`
++- `docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md`
++- `docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md`
++- `docs_build/dev/ProjectInstructions/addendums/build_path_sync.md`
++- `docs_build/dev/ProjectInstructions/addendums/deprecation.md`
++- `docs_build/dev/ProjectInstructions/addendums/multi_team.md`
++- `docs_build/dev/ProjectInstructions/addendums/preservation.md`
++- `docs_build/dev/ProjectInstructions/addendums/team_release_readiness.md`
++- `docs_build/dev/ProjectInstructions/addendums/tile_overlay_status.md`
++- `docs_build/dev/ProjectInstructions/archive/README.md`
++- `docs_build/dev/ProjectInstructions/archive/history/.gitkeep`
++- `docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md`
++- `docs_build/dev/ProjectInstructions/deprecation/README.md`
++- `docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md`
++
++## Validation
++
++- `git diff --check`
++- `git diff --cached --check`
++- Physical tree verification for `docs_build/dev/ProjectInstructions/`
++- Targeted text verification for OWNER override, OWNER safety rules, team registry, EOD merge rule, and required anchor files
++
++## Skipped Lanes
++
++- Playwright skipped: documentation-only installation.
++- Samples skipped: documentation-only installation.
++
++## Package
++
++- `tmp/PR_26172_OWNER_017-project-instructions-bootstrap-install_delta.zip`