Skip to content

Commit cc69710

Browse files
committed
Merge remote-tracking branch 'origin/main' into codex/pr-26171-069-message-tts-profile-contract-alignment
# Conflicts: # docs_build/dev/reports/codex_changed_files.txt # docs_build/dev/reports/codex_review.diff
2 parents 98b8d0e + 43f3ead commit cc69710

11 files changed

Lines changed: 6037 additions & 23 deletions

docs_build/dev/PROJECT_INSTRUCTIONS.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2009,6 +2009,16 @@ Required Git workflow report fields:
20092009
- merge result
20102010
- final main commit
20112011

2012+
## OWNER-CONTROLLED STABLE AND MERGE APPROVAL
2013+
2014+
Stable promotion and merge approval are owner-controlled.
2015+
2016+
Rules:
2017+
- Codex may prepare scoped changes, reports, validation evidence, ZIP artifacts, branches, and PRs.
2018+
- Codex must not merge a PR or mark a workstream stable without explicit approval from the assigned Team Alpha or Team Beta owner.
2019+
- Master Control may recommend sequencing or assignment, but affected workstream owners control stable and merge approval.
2020+
- This targeted section supersedes older automatic-merge wording when approval ownership is in question.
2021+
20122022
## CODEX INSTRUCTION ENFORCEMENT START GATE
20132023

20142024
Codex must run this gate before every PR execution and before any file changes.
@@ -2017,7 +2027,7 @@ Required instruction reads:
20172027
- Read `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
20182028
- Read `docs_build/dev/PROJECT_MULTI_PC.txt`.
20192029
- Treat the newest applicable section in `PROJECT_INSTRUCTIONS.md` as authoritative when rules overlap.
2020-
- Treat the current owner/parity section in `PROJECT_MULTI_PC.txt` as authoritative for PC/Laptop routing.
2030+
- Treat the current owner/parity section in `PROJECT_MULTI_PC.txt` as authoritative for Team Alpha / Team Beta routing.
20212031

20222032
Required pre-change report:
20232033
- Codex must report instruction compliance as `PASS` or `FAIL` before making file changes.
@@ -2027,7 +2037,7 @@ Required pre-change report:
20272037
Hard stops before changes:
20282038
- If the current branch is not `main`, HARD STOP.
20292039
- If the repository is not clean before the PR branch is created, HARD STOP.
2030-
- If the PR owner does not match the PC/Laptop ownership map in `PROJECT_MULTI_PC.txt`, HARD STOP.
2040+
- If the PR owner does not match the Team Alpha / Team Beta ownership map in `PROJECT_MULTI_PC.txt`, HARD STOP.
20312041
- If the PR number parity does not match the assigned machine in `PROJECT_MULTI_PC.txt`, HARD STOP.
20322042
- If the PR asks for implementation and the implementation path is wrong, HARD STOP.
20332043
- 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

Lines changed: 25 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Naming governance
1111
Workflow governance
1212
Environment strategy
1313
PR sequencing
14-
Merge approval
14+
Stable and merge approval
1515

1616
It should never build code and never own implementation details.
1717

@@ -22,12 +22,12 @@ Requirements
2222
Acceptance Criteria
2323
Dependencies
2424
Priority
25-
Owner (PC/Laptop)
25+
Owner (Team Alpha / Team Beta)
2626
Recommended Workstream Split
2727

2828
Instead of arbitrary splits, split by Creator journey.
2929

30-
PC — Creator Journey
30+
Team Alpha — Creator Journey
3131

3232
Owns:
3333

@@ -57,7 +57,7 @@ Reason:
5757

5858
These tools are heavily connected.
5959

60-
Laptop — Content Creation
60+
Team Beta — Content Creation
6161

6262
Owns:
6363

@@ -85,7 +85,7 @@ These tools share asset pipelines and publishing workflows.
8585

8686
Messages Tool Placement
8787

88-
I would move Messages to Laptop ownership.
88+
I would move Messages to Team Beta ownership.
8989

9090
Reason:
9191

@@ -191,7 +191,7 @@ Immediate Queue
191191

192192
If we start using Master Control today, my queue would be:
193193

194-
PC
194+
Team Alpha
195195
PR_26171_001-game-journey-completion-model
196196

197197
Scope:
@@ -205,7 +205,7 @@ Sounds [17]
205205

206206
This solves the "xxx%" problem.
207207

208-
Laptop
208+
Team Beta
209209
PR_26171_002-messages-tool-foundation
210210

211211
Scope:
@@ -282,7 +282,7 @@ Not developer.
282282

283283
---
284284

285-
## PC Chat
285+
## Team Alpha Chat
286286

287287
Give it ownership of a workstream.
288288

@@ -309,7 +309,7 @@ it keeps building in that area.
309309

310310
---
311311

312-
## Laptop Chat
312+
## Team Beta Chat
313313

314314
Give it a different workstream.
315315

@@ -371,13 +371,13 @@ So I'd keep IST mostly as infrastructure work and focus development on tool comp
371371
Master Control should assign ownership:
372372

373373
```text
374-
PC
374+
Team Alpha
375375
Game Journey
376376
Game Hub
377377
Publish
378378
Share
379379

380-
Laptop
380+
Team Beta
381381
Audio
382382
MIDI
383383
Events
@@ -405,7 +405,7 @@ feature/game-hub
405405
feature/progress-tracking
406406
```
407407

408-
Never have both PCs working in the same tool at the same time.
408+
Never have both teams working in the same tool at the same time.
409409

410410
---
411411

@@ -418,19 +418,19 @@ For example, in Master Control you can ask:
418418
```text
419419
Given everything we know about GFS:
420420

421-
What should PC build next?
422-
What should Laptop build next?
421+
What should Team Alpha build next?
422+
What should Team Beta build next?
423423

424424
Generate the next PR for each.
425425
```
426426

427427
Then Master Control outputs:
428428

429429
```text
430-
PC:
430+
Team Alpha:
431431
PR_26171_002-game-hub-progress
432432

433-
Laptop:
433+
Team Beta:
434434
PR_26171_003-messages-tool-mvp
435435
```
436436

@@ -457,17 +457,17 @@ Codex must read this file before every PR execution.
457457

458458
Machine parity:
459459

460-
PC / Environment 1:
460+
Team Alpha / Environment 1:
461461
- Uses even-numbered PR sequence values.
462462
- Example: `PR_26171_064-*`.
463463

464-
Laptop / Environment 2:
464+
Team Beta / Environment 2:
465465
- Uses odd-numbered PR sequence values.
466466
- Example: `PR_26171_063-*`.
467467

468468
Owner map:
469469

470-
PC / Environment 1 owns Creator Journey work:
470+
Team Alpha / Environment 1 owns Creator Journey work:
471471
- Game Journey
472472
- Game Hub
473473
- Idea
@@ -483,7 +483,7 @@ PC / Environment 1 owns Creator Journey work:
483483
- Game Design
484484
- Game Crew
485485

486-
Laptop / Environment 2 owns Content Creation and asset/publishing work:
486+
Team Beta / Environment 2 owns Content Creation and asset/publishing work:
487487
- Graphics
488488
- Toolbox images
489489
- Audio
@@ -501,8 +501,12 @@ Governance, recovery, diagnostics, and instruction-hardening PRs:
501501
- Must not implement tool/runtime work from the opposite owner.
502502
- Must document owner/parity compliance in the PR report.
503503

504+
Stable and merge approval:
505+
- Stable promotion and merge approval are controlled by the assigned Team Alpha or Team Beta owner.
506+
- Master Control may recommend sequencing, but Codex must not merge or mark stable without explicit owner approval for the affected workstream.
507+
504508
Hard stop rules:
505509
- If the PR number parity does not match the current machine, stop before changes.
506510
- If the PR scope belongs to the other machine owner, stop before changes.
507-
- If the PR crosses PC and Laptop ownership, stop and require Master Control to split or assign the work.
511+
- If the PR crosses Team Alpha and Team Beta ownership, stop and require Master Control to split or assign the work.
508512
- If the requested implementation path conflicts with the active owner path, stop before changes.
Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
docs_build/dev/reports/codex_changed_files.txt
2+
docs_build/dev/reports/codex_review.diff
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
# PR_26171_071 Discarded / Unrelated Work Report
2+
3+
## Pre-cleanup State
4+
5+
The active merge had unrelated staged payload from upstream PR_26171_044 / PR_26171_067 and two singleton report conflicts.
6+
7+
```text
8+
## main...origin/main [ahead 1, behind 4]
9+
A docs_build/dev/reports/PR_26171_067-instruction-compliance-checklist.md
10+
A docs_build/dev/reports/PR_26171_067-manual-validation-notes.md
11+
A docs_build/dev/reports/PR_26171_067-message-tts-contract-checklist.md
12+
A docs_build/dev/reports/PR_26171_067-parent-child-table-checklist.md
13+
A docs_build/dev/reports/PR_26171_067-tts-profile-emotion-table-foundation.md
14+
A docs_build/dev/reports/PR_26171_067-validation.md
15+
UU docs_build/dev/reports/codex_changed_files.txt
16+
UU docs_build/dev/reports/codex_review.diff
17+
M docs_build/dev/reports/coverage_changed_js_guardrail.txt
18+
M docs_build/dev/reports/playwright_v8_coverage_report.txt
19+
A docs_build/pr/PR_26171_044-idea-board-game-hub-project-flow/APPLY_PR.md
20+
A docs_build/pr/PR_26171_044-idea-board-game-hub-project-flow/BUILD_PR.md
21+
A docs_build/pr/PR_26171_044-idea-board-game-hub-project-flow/PLAN_PR.md
22+
M src/dev-runtime/persistence/tool-repositories/game-workspace-mock-repository.js
23+
M tests/playwright/tools/GameWorkspaceMockRepository.spec.mjs
24+
M tests/playwright/tools/IdeaBoardTableNotes.spec.mjs
25+
M tests/playwright/tools/TextToSpeechFunctional.spec.mjs
26+
M tests/playwright/tools/ToolboxRoutePages.spec.mjs
27+
M tests/tools/Text2SpeechShell.test.mjs
28+
M toolbox/game-workspace/game-workspace.js
29+
M toolbox/game-workspace/index.html
30+
M toolbox/idea-board/index.html
31+
M toolbox/idea-board/index.js
32+
M toolbox/text-to-speech/index.html
33+
M toolbox/text-to-speech/text2speech.js
34+
```
35+
36+
## Conflicted Files
37+
38+
```text
39+
docs_build/dev/reports/codex_changed_files.txt
40+
docs_build/dev/reports/codex_review.diff
41+
```
42+
43+
## Untracked Files Before Cleanup
44+
45+
```text
46+
(none)
47+
```
48+
49+
## Recording Before Cleanup
50+
51+
- Full pre-cleanup recovery patch: `docs_build/dev/reports/PR_26171_071-recovery-precleanup.patch.md`.
52+
- Pre-cleanup status: `docs_build/dev/reports/PR_26171_071-status-before-cleanup.txt`.
53+
- Pre-cleanup conflicted file list: `docs_build/dev/reports/PR_26171_071-conflicted-files-before-cleanup.txt`.
54+
- Pre-cleanup untracked file list: `docs_build/dev/reports/PR_26171_071-untracked-files-before-cleanup.txt`.
55+
56+
## Cleanup Decision
57+
58+
The unrelated staged PR_26171_044 / PR_26171_067 work was removed from the index by aborting the interrupted merge. Latest upstream history was then reapplied through `git pull --rebase origin main`, so upstream committed work remains as history instead of as unresolved staged changes.
59+
60+
No Message/TTS implementation files were edited by this recovery PR.
Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
# PR_26171_071 Manual Validation Notes
2+
3+
## Commands Run
4+
5+
- `git status`
6+
- `git log --oneline -5`
7+
- `git diff --check`
8+
9+
## git status
10+
11+
```text
12+
On branch main
13+
Your branch is ahead of 'origin/main' by 1 commit.
14+
(use "git push" to publish your local commits)
15+
16+
Changes not staged for commit:
17+
(use "git add <file>..." to update what will be committed)
18+
(use "git restore <file>..." to discard changes in working directory)
19+
modified: docs_build/dev/reports/codex_changed_files.txt
20+
modified: docs_build/dev/reports/codex_review.diff
21+
22+
Untracked files:
23+
(use "git add <file>..." to include in what will be committed)
24+
docs_build/dev/reports/PR_26171_071-conflicted-files-before-cleanup.txt
25+
docs_build/dev/reports/PR_26171_071-discarded-unrelated-work-report.md
26+
docs_build/dev/reports/PR_26171_071-manual-validation-notes.md
27+
docs_build/dev/reports/PR_26171_071-merge-conflict-recovery-report.md
28+
docs_build/dev/reports/PR_26171_071-preserved-local-commit-report.md
29+
docs_build/dev/reports/PR_26171_071-recovery-precleanup.patch.md
30+
docs_build/dev/reports/PR_26171_071-status-before-cleanup.txt
31+
docs_build/dev/reports/PR_26171_071-untracked-files-before-cleanup.txt
32+
33+
no changes added to commit (use "git add" and/or "git commit -a")
34+
```
35+
36+
## git log --oneline -5
37+
38+
```text
39+
7dfb6ea5f Add multi-team merge authority governance - PR_26171_046-multi-team-merge-authority
40+
decd37141 PR_26171_044 Idea Board Game Hub project flow
41+
485e96c69 Merge remote-tracking branch 'origin/main' into codex/pr-26171-044-idea-board-game-hub-project-flow
42+
2a38796f8 Wire Idea Board projects into Game Hub
43+
83fa8ad9d PR_26171_067 tts profile emotion table foundation
44+
```
45+
46+
## git diff --check
47+
48+
Result: PASS
49+
50+
```text
51+
(no output)
52+
```
53+
54+
## ZIP Evidence
55+
56+
- ZIP path: `tmp/PR_26171_071-main-merge-conflict-recovery_delta.zip`
57+
- ZIP contents:
58+
- docs_build/dev/reports/codex_review.diff
59+
- docs_build/dev/reports/codex_changed_files.txt
60+
- docs_build/dev/reports/PR_26171_071-merge-conflict-recovery-report.md
61+
- docs_build/dev/reports/PR_26171_071-preserved-local-commit-report.md
62+
- docs_build/dev/reports/PR_26171_071-discarded-unrelated-work-report.md
63+
- docs_build/dev/reports/PR_26171_071-manual-validation-notes.md
64+
- docs_build/dev/reports/PR_26171_071-recovery-precleanup.patch.md
65+
- docs_build/dev/reports/PR_26171_071-status-before-cleanup.txt
66+
- docs_build/dev/reports/PR_26171_071-conflicted-files-before-cleanup.txt
67+
- docs_build/dev/reports/PR_26171_071-untracked-files-before-cleanup.txt
68+
69+
## Manual Notes
70+
71+
- Active merge source was inspected and recorded before cleanup.
72+
- Conflict files were identified as `docs_build/dev/reports/codex_changed_files.txt` and `docs_build/dev/reports/codex_review.diff`.
73+
- Local commit `390912b56` was preserved by branch before cleanup.
74+
- The active merge was aborted safely.
75+
- Latest `origin/main` was synced with rebase, preserving the governance commit as `7dfb6ea5f14e23f87d556bc7448e35cd95866d48`.
76+
- No Message/TTS implementation work was performed in this PR.
77+
- Playwright impacted: No, recovery/reporting workflow only.

0 commit comments

Comments
 (0)