PR_26171_ALPHA_075 team based PR naming

docs_build/dev/PROJECT_INSTRUCTIONS.md

@@ -11,22 +11,38 @@ PLAN_PR → BUILD_PR → APPLY_PR
 
 PR names MUST follow:
 
-`PR_<YYJJJ>_<###>-<short-description>`
+`PR_<YYJJJ>_<TEAM>_<###>-<short-description>`
 
 Where:
 - `YY` = year (2 digit)
-- `JJJ` = Julian day (001–365)
+- `JJJ` = Julian day (001-365)
+- `TEAM` = required team ownership token from `docs_build/dev/PROJECT_MULTI_PC.txt`
 - `###` = sequence for the day (001+)
 
 Example:
-- `PR_26124_001-palette-baseline`
-- `PR_26124_002-tool-fix-asset-manager`
+- `PR_26171_ALPHA_065-message-studio-parent-child-table-foundation`
+- `PR_26171_BETA_069-message-tts-profile-contract-alignment`
+- `PR_26171_GAMMA_071-main-merge-conflict-recovery`
+
+Branch names MUST mirror PR ownership:
+
+`pr/<YYJJJ>-<TEAM>-<###>-<short-description>`
+
+Branch examples:
+- `pr/26171-ALPHA-065-message-studio-parent-child-table-foundation`
+- `pr/26171-BETA-069-message-tts-profile-contract-alignment`
+- `pr/26171-GAMMA-071-main-merge-conflict-recovery`
 
 Rules:
 - Must be unique per day
 - Must be sortable
+- `TEAM` is required
+- `TEAM` ownership comes from `docs_build/dev/PROJECT_MULTI_PC.txt`
+- Team ownership is independent of machine, workspace, laptop, desktop, or environment
 - Description must be short and hyphenated
 - Do NOT reuse old `PR_11_*` format for new PRs
+- Existing PC/LAPTOP, desktop/laptop, workspace, environment, or machine-parity examples are historical only
+- Future PR reports, recovery reports, validation reports, and manual validation notes must include TEAM ownership
 
 ## CHATGPT EXECUTION ROLE
 
@@ -817,7 +833,7 @@ If the user says `NEXT`:
 
 Use the current naming standard:
 
-`PR_<YYJJJ>_<###>-<short-description>`
+`PR_<YYJJJ>_<TEAM>_<###>-<short-description>`
 
 Do NOT continue old `PR_11_*` naming for new work.
 
@@ -2027,18 +2043,18 @@ 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 Team Alpha / Team Beta routing.
+- Treat the current team ownership section in `PROJECT_MULTI_PC.txt` as authoritative for TEAM routing.
 
 Required pre-change report:
 - Codex must report instruction compliance as `PASS` or `FAIL` before making file changes.
-- The report must include branch, clean status, PR owner, PR parity, implementation path, validation scope, required report list, and ZIP requirement.
+- The report must include branch, clean status, PR TEAM owner, implementation path, validation scope, required report list, and ZIP requirement.
 - Any `FAIL` is a hard stop unless the PR explicitly scopes branch audit or recovery documentation without implementation.
 
 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 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 name does not include a required TEAM token, HARD STOP.
+- If the PR TEAM owner does not match the team ownership map 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.
 - If scoped validation is skipped without a documented reason, HARD STOP.

docs_build/dev/PROJECT_MULTI_PC.txt

@@ -22,7 +22,7 @@ Requirements
 Acceptance Criteria
 Dependencies
 Priority
-Owner (Team Alpha / Team Beta)
+Owner (Team Alpha / Team Beta / Team Gamma)
 Recommended Workstream Split
 
 Instead of arbitrary splits, split by Creator journey.
@@ -451,23 +451,35 @@ That is probably the fastest path to doubling throughput without creating chaos.
 
 ----------------------------------------------------------------------------------------
 
-Current Authoritative Multi-PC Gate
+Current Authoritative Team Ownership Gate
 
 Codex must read this file before every PR execution.
 
-Machine parity:
+PR naming:
 
-Team Alpha / Environment 1:
-- Uses even-numbered PR sequence values.
-- Example: `PR_26171_064-*`.
+- PR names must include the owning TEAM token:
+  - `PR_<YYJJJ>_<TEAM>_<###>-<description>`
+- Branch names must mirror PR ownership:
+  - `pr/<YYJJJ>-<TEAM>-<###>-<description>`
+- `TEAM` is required.
+- Team ownership is independent of machine, workspace, laptop, desktop, or environment.
+- Do not infer PR ownership from PR number parity or current machine.
 
-Team Beta / Environment 2:
-- Uses odd-numbered PR sequence values.
-- Example: `PR_26171_063-*`.
+Current examples:
+- `PR_26171_ALPHA_065-message-studio-parent-child-table-foundation`
+- `PR_26171_BETA_069-message-tts-profile-contract-alignment`
+- `PR_26171_GAMMA_071-main-merge-conflict-recovery`
+- `pr/26171-ALPHA-065-message-studio-parent-child-table-foundation`
+- `pr/26171-BETA-069-message-tts-profile-contract-alignment`
+- `pr/26171-GAMMA-071-main-merge-conflict-recovery`
+
+Historical examples:
+- Older PC/LAPTOP, desktop/laptop, workspace, environment, and machine-parity examples are historical only.
+- Older parity-only examples such as `PR_26171_064-*` and `PR_26171_063-*` are historical only.
 
 Owner map:
 
-Team Alpha / Environment 1 owns Creator Journey work:
+Team Alpha owns Creator Journey work:
 - Game Journey
 - Game Hub
 - Idea
@@ -483,7 +495,7 @@ Team Alpha / Environment 1 owns Creator Journey work:
 - Game Design
 - Game Crew
 
-Team Beta / Environment 2 owns Content Creation and asset/publishing work:
+Team Beta owns Content Creation and asset/publishing work:
 - Graphics
 - Toolbox images
 - Audio
@@ -496,17 +508,29 @@ Team Beta / Environment 2 owns Content Creation and asset/publishing work:
 - Community
 - Arcade
 
+Team Gamma owns governance, recovery, diagnostics, and instruction-hardening work:
+- PR naming governance
+- Git workflow governance
+- Recovery reports
+- Workspace recovery
+- Main merge conflict recovery
+- Diagnostics
+- Instruction enforcement
+- Static docs governance
+
 Governance, recovery, diagnostics, and instruction-hardening PRs:
-- Follow PR number parity unless Master Control explicitly assigns an owner.
+- Use the TEAM token assigned by Master Control.
 - Must not implement tool/runtime work from the opposite owner.
-- Must document owner/parity compliance in the PR report.
+- 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 or Team Beta owner.
+- 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.
 
 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 Team Alpha and Team Beta ownership, stop and require Master Control to split or assign the work.
+- 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 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 requested implementation path conflicts with the active owner path, stop before changes.

docs_build/dev/reports/PR_26171_ALPHA_075-team-based-pr-naming-manual-validation-notes.md

@@ -0,0 +1,17 @@
+# PR_26171_ALPHA_075-team-based-pr-naming Manual Validation Notes
+
+Generated: 2026-06-20T21:34:35.616Z
+
+## TEAM Ownership
+
+- TEAM owner: ALPHA
+
+## Manual Review
+
+- Confirmed PROJECT_INSTRUCTIONS.md documents the required TEAM token in PR names.
+- Confirmed PROJECT_INSTRUCTIONS.md documents branch names mirroring PR ownership.
+- Confirmed PROJECT_MULTI_PC.txt makes team ownership independent of machine, workspace, laptop, desktop, and environment.
+- Confirmed older PC/LAPTOP and parity examples are marked historical only.
+- Confirmed recovery reports are required to include TEAM ownership.
+
+No browser or runtime validation was required because this PR is docs/static only.

docs_build/dev/reports/PR_26171_ALPHA_075-team-based-pr-naming-validation.md

@@ -0,0 +1,34 @@
+# PR_26171_ALPHA_075-team-based-pr-naming Validation
+
+Generated: 2026-06-20T21:34:35.616Z
+
+## TEAM Ownership
+
+- TEAM owner: ALPHA
+- Validation scope: docs/static validation only
+
+## Commands
+
+```text
+git diff --check
+```
+
+## Results
+
+- Initial docs diff check: PASS
+
+Output:
+
+```text
+warning: in the working copy of 'docs_build/dev/reports/codex_review.diff', LF will be replaced by CRLF the next time Git touches it
+```
+
+## Final Validation
+
+- Final full diff check after report generation: PASS
+
+Output:
+
+```text
+(no output)
+```

docs_build/dev/reports/PR_26171_ALPHA_075-team-based-pr-naming.md

@@ -0,0 +1,62 @@
+# PR_26171_ALPHA_075-team-based-pr-naming
+
+Generated: 2026-06-20T21:34:35.616Z
+
+## Purpose
+
+Replace machine-based PR naming examples with team-based ownership naming.
+
+## TEAM Ownership
+
+- TEAM owner: ALPHA
+- Ownership source: docs_build/dev/PROJECT_MULTI_PC.txt
+- Scope classification: static docs governance
+- Machine/workspace/environment ownership: not used for PR naming or branch naming
+
+## Scope
+
+Updated only:
+
+- docs_build/dev/PROJECT_INSTRUCTIONS.md
+- docs_build/dev/PROJECT_MULTI_PC.txt
+
+## Naming Contract
+
+Authoritative PR format:
+
+`PR_<YYJJJ>_<TEAM>_<###>-<description>`
+
+Authoritative branch format:
+
+`pr/<YYJJJ>-<TEAM>-<###>-<description>`
+
+Required examples are documented for ALPHA, BETA, and GAMMA.
+
+## Instruction Compliance
+
+- Read PROJECT_INSTRUCTIONS.md first: PASS
+- Read PROJECT_MULTI_PC.txt before edits: PASS
+- Started from main: PASS
+- Pulled latest main before branch: PASS
+- Clean repo before branch: PASS
+- Created branch: pr/26171-ALPHA-075-team-based-pr-naming
+- TEAM token required: PASS
+- TEAM ownership comes from PROJECT_MULTI_PC.txt: PASS
+- Future reports include TEAM ownership: PASS
+
+## Git Workflow Status
+
+- Starting HEAD: b31b319983dc62a240ab7095b8430b7c6ed182bd
+- origin/main at start: b31b319983dc62a240ab7095b8430b7c6ed182bd
+- origin/main...HEAD after branch creation: 0	0
+- Push result: pending at report generation
+- PR URL: pending at report generation
+- Merge result: pending at report generation
+- Final main commit: pending at report generation
+
+## Changed Files Before Report Generation
+
+```text
+docs_build/dev/PROJECT_INSTRUCTIONS.md
+docs_build/dev/PROJECT_MULTI_PC.txt
+```

docs_build/dev/reports/codex_changed_files.txt

@@ -1,17 +1,7 @@
-A	docs_build/dev/reports/PR_26171_069-manual-validation-notes.md
-A	docs_build/dev/reports/PR_26171_069-message-tts-ownership-checklist.md
-A	docs_build/dev/reports/PR_26171_069-message-tts-profile-contract-alignment.md
-A	docs_build/dev/reports/PR_26171_069-parent-child-table-checklist.md
-A	docs_build/dev/reports/PR_26171_069-validation.md
-A	docs_build/pr/PR_26171_069-message-tts-profile-contract-alignment/APPLY_PR.md
-A	docs_build/pr/PR_26171_069-message-tts-profile-contract-alignment/BUILD_PR.md
-A	docs_build/pr/PR_26171_069-message-tts-profile-contract-alignment/PLAN_PR.md
-M	tests/playwright/tools/MessagesTool.spec.mjs
-M	tests/playwright/tools/TextToSpeechFunctional.spec.mjs
-M	tests/tools/Text2SpeechShell.test.mjs
-M	toolbox/messages/index.html
-M	toolbox/messages/message-tts-service-registry.js
-M	toolbox/messages/messages.js
-M	toolbox/text-to-speech/text2speech.js
-M	docs_build/dev/reports/codex_review.diff
-M	docs_build/dev/reports/codex_changed_files.txt
+docs_build/dev/PROJECT_INSTRUCTIONS.md
+docs_build/dev/PROJECT_MULTI_PC.txt
+docs_build/dev/reports/PR_26171_ALPHA_075-team-based-pr-naming-manual-validation-notes.md
+docs_build/dev/reports/PR_26171_ALPHA_075-team-based-pr-naming-validation.md
+docs_build/dev/reports/PR_26171_ALPHA_075-team-based-pr-naming.md
+docs_build/dev/reports/codex_changed_files.txt
+docs_build/dev/reports/codex_review.diff