Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 34 additions & 4 deletions docs_build/dev/PROJECT_INSTRUCTIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -1999,7 +1999,7 @@ Required workflow:
10. Create Pull Request automatically.
11. Resolve merge conflicts if encountered.
12. Re-run validation after conflict resolution.
13. Merge PR.
13. Merge PR only after explicit owner/EOD approval.
14. Return to main.
15. Pull latest main.
16. Continue to next approved PR.
Expand All @@ -2008,8 +2008,8 @@ Rules:
- Do not ask the user if a PR should be created.
- Do not ask the user if a branch should be pushed.
- Treat PR creation as required.
- Treat branch push as required.
- Treat merge as required after validation passes.
- Treat branch push as required for scoped PR branch publishing.
- Treat merge as required only after validation passes and explicit owner/EOD approval is provided.
- If GitHub prompts `Would you like to create a Pull Request?`, answer YES automatically.
- If merge conflicts occur:
- preserve latest main
Expand All @@ -2031,9 +2031,39 @@ 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.
- Codex must not merge a PR or mark a workstream stable without explicit approval from the assigned Team Alpha, Team Beta, or Team Gamma 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.
- EOD merge and EOD push actions are owner-controlled and require explicit approval.

## SEQUENTIAL CODEX QUEUE MODE

Any TEAM owner may use Sequential Codex Queue Mode for ordered, fully scoped PR queues within that team's ownership area.

Sequential Codex Queue Mode means Codex receives one queue command containing multiple ordered PR scopes.

Each queued PR must still have:
- exact PR name
- TEAM token
- branch name
- exact scope
- validation scope
- required reports
- manual validation notes
- ZIP requirement

Rules:
- A queue command is not itself a PR unless explicitly named as one.
- Each queued PR must stay within the same TEAM ownership area unless Master Control explicitly splits or assigns cross-team work.
- ALPHA queues may only contain Alpha-owned scopes.
- BETA queues may only contain Beta-owned scopes.
- GAMMA queues may only contain Gamma-owned scopes.
- Cross-team queues are prohibited unless each PR is individually assigned to the correct TEAM token.
- Missing exact scope for any queued PR is a hard stop for that PR only.
- Codex may continue to the next queued PR only if the next PR has exact scope and does not depend on the stopped PR.
- Codex must not create empty ZIPs or package partial PRs.
- EOD merge/push is owner-controlled and requires explicit approval.
- This section supersedes older wording that implies every PR must be independently prompted when Master Control provides a fully scoped sequential queue.

## CODEX INSTRUCTION ENFORCEMENT START GATE

Expand Down
15 changes: 15 additions & 0 deletions docs_build/dev/PROJECT_MULTI_PC.txt
Original file line number Diff line number Diff line change
Expand Up @@ -524,6 +524,21 @@ Governance, recovery, diagnostics, and instruction-hardening PRs:
- Must document TEAM ownership compliance in the PR report.
- Recovery reports must include TEAM ownership.

Sequential Codex Queue Mode:
- Any TEAM owner may use Sequential Codex Queue Mode for ordered, fully scoped PR queues within that team's ownership area.
- Sequential Codex Queue Mode means Codex receives one queue command containing multiple ordered PR scopes.
- Each queued PR must still have exact PR name, TEAM token, branch name, exact scope, validation scope, required reports, manual validation notes, and ZIP requirement.
- A queue command is not itself a PR unless explicitly named as one.
- Each queued PR must stay within the same TEAM ownership area unless Master Control explicitly splits or assigns cross-team work.
- ALPHA queues may only contain Alpha-owned scopes.
- BETA queues may only contain Beta-owned scopes.
- GAMMA queues may only contain Gamma-owned scopes.
- Cross-team queues are prohibited unless each PR is individually assigned to the correct TEAM token.
- Missing exact scope for any queued PR is a hard stop for that PR only.
- Codex may continue to the next queued PR only if the next PR has exact scope and does not depend on the stopped PR.
- Codex must not create empty ZIPs or package partial PRs.
- EOD merge/push is owner-controlled and requires explicit approval.

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.
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# PR_26171_GAMMA_005 Instruction Compliance Checklist

- Read `docs_build/dev/PROJECT_INSTRUCTIONS.md`: PASS.
- Read `docs_build/dev/PROJECT_MULTI_PC.txt`: PASS.
- Checkout `main` before starting: PASS.
- Pull latest `main`: PASS.
- Verify branch is `main`: PASS.
- Verify clean status before branch creation: PASS.
- Verify PR name includes TEAM token: PASS.
- Verify TEAM owner matches Team Gamma governance/instruction-hardening ownership: PASS.
- Create requested branch `pr/26171-GAMMA-005-all-team-sequential-queue-governance`: PASS.
- Keep scope limited to requested docs and reports: PASS.
- Run docs/static validation only: PASS.
- Run `git diff --check`: PASS.
- Verify Sequential Codex Queue Mode is not Gamma-only: PASS.
- Verify TEAM ownership boundaries remain enforced: PASS.
- Verify automatic merge wording is constrained by owner-controlled EOD approval: PASS.
- Do not run Playwright: PASS.
- Do not run samples: PASS.
- Create required PR-specific report: PASS.
- Create manual validation notes: PASS.
- Create instruction compliance checklist: PASS.
- Create `codex_review.diff`: PASS.
- Create `codex_changed_files.txt`: PASS.
- Create repo-structured ZIP under `tmp/`: PASS.
- Do not merge before explicit EOD approval: PASS.
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# PR_26171_GAMMA_005 Manual Validation Notes

Manual validation status: PASS.

Manual checks performed:
- Reviewed `docs_build/dev/PROJECT_INSTRUCTIONS.md` Sequential Codex Queue Mode section for all-team wording.
- Reviewed `docs_build/dev/PROJECT_MULTI_PC.txt` ownership section for Alpha, Beta, and Gamma queue boundaries.
- Confirmed queue mode is not Gamma-only.
- Confirmed cross-team queues remain prohibited unless each PR is assigned to the correct TEAM token.
- Confirmed EOD merge/push remains owner-controlled and requires explicit approval.
- Confirmed Playwright and samples are skipped because this PR changes docs/workflow governance only.

Expected outcome:
- Team Alpha, Team Beta, and Team Gamma may each use Sequential Codex Queue Mode for fully scoped queues inside their own ownership area.
- Cross-team work must still be split or explicitly assigned with the correct TEAM token per PR.
- Codex must not package empty ZIPs or partial PRs.

Out of scope:
- Runtime behavior.
- Tool implementation.
- Admin UI implementation.
- Database migration or connection behavior.
- Playwright validation.
- Samples validation.
Original file line number Diff line number Diff line change
@@ -0,0 +1,71 @@
# PR_26171_GAMMA_005-all-team-sequential-queue-governance

## Summary

Team ownership: GAMMA.

Purpose: generalize Sequential Codex Queue Mode from Gamma-only governance to all TEAM owners while preserving Alpha, Beta, and Gamma ownership boundaries and owner-controlled EOD merge approval.

## Scope

Changed files:
- `docs_build/dev/PROJECT_INSTRUCTIONS.md`
- `docs_build/dev/PROJECT_MULTI_PC.txt`
- `docs_build/dev/reports/PR_26171_GAMMA_005-all-team-sequential-queue-governance.md`
- `docs_build/dev/reports/PR_26171_GAMMA_005-all-team-sequential-queue-governance-manual-validation-notes.md`
- `docs_build/dev/reports/PR_26171_GAMMA_005-all-team-sequential-queue-governance-instruction-compliance-checklist.md`
- `docs_build/dev/reports/codex_review.diff`
- `docs_build/dev/reports/codex_changed_files.txt`

## Instruction Compliance

Start gate: PASS.

- Required instruction reads: PASS. Read `docs_build/dev/PROJECT_INSTRUCTIONS.md` and `docs_build/dev/PROJECT_MULTI_PC.txt`.
- Checkout `main` before starting: PASS.
- Pull latest `main`: PASS.
- Verify branch is `main`: PASS.
- Verify clean status before PR branch: PASS.
- Created branch: `pr/26171-GAMMA-005-all-team-sequential-queue-governance`.
- PR TEAM owner: GAMMA.
- Implementation path: docs-only governance update in `docs_build/dev/PROJECT_INSTRUCTIONS.md` and `docs_build/dev/PROJECT_MULTI_PC.txt`.
- Validation scope: docs/static only.
- Required reports: PASS. PR report, manual validation notes, instruction compliance checklist, `codex_review.diff`, and `codex_changed_files.txt`.
- ZIP requirement: PASS. Required final ZIP path is `tmp/PR_26171_GAMMA_005-all-team-sequential-queue-governance_delta.zip`.

## Requirement Checklist

- Generalize Sequential Codex Queue Mode from Gamma-only to all TEAM owners: PASS.
- Replace Gamma-only permission with any TEAM owner permission: PASS.
- Preserve Alpha ownership boundaries: PASS.
- Preserve Beta ownership boundaries: PASS.
- Preserve Gamma ownership boundaries: PASS.
- Prohibit cross-team queues unless each PR is individually assigned to the correct TEAM token: PASS.
- Keep exact PR name, TEAM token, branch name, exact scope, validation scope, required reports, manual notes, and ZIP requirement per queued PR: PASS.
- Keep missing exact scope as a hard stop for that PR only: PASS.
- Keep EOD merge/push owner-controlled: PASS.

## Validation

Lanes executed:
- docs/static - governance docs only.

Commands run:
- `git diff --check` - PASS.
- `rg -n "Any TEAM owner may use Sequential Codex Queue Mode|Team Gamma may use Sequential Codex Queue Mode|ALPHA queues may only contain|BETA queues may only contain|GAMMA queues may only contain|Cross-team queues are prohibited" docs_build/dev/PROJECT_INSTRUCTIONS.md docs_build/dev/PROJECT_MULTI_PC.txt` - PASS. Found all-team language and ownership-boundary rules; no Gamma-only permission remained.
- `rg -n "Team Gamma may use Sequential Codex Queue Mode" docs_build/dev/PROJECT_INSTRUCTIONS.md docs_build/dev/PROJECT_MULTI_PC.txt` - PASS. No matches.
- `rg -n "Merge PR only after explicit owner/EOD approval|Treat merge as required only after validation passes and explicit owner/EOD approval is provided|EOD merge/push is owner-controlled and requires explicit approval|Codex must not merge a PR or mark a workstream stable without explicit approval" docs_build/dev/PROJECT_INSTRUCTIONS.md docs_build/dev/PROJECT_MULTI_PC.txt` - PASS.

Skipped lanes:
- Playwright: SKIP. Docs/workflow-only PR with no UI, tool runtime, toolState, or workspace behavior changes.
- Samples: SKIP. Docs/workflow-only PR with no sample loader, sample JSON, or sample runtime changes.
- Runtime, integration, and engine: SKIP. No runtime, handoff, shared parser, or engine behavior changed.

## Git Workflow

- Current branch: `pr/26171-GAMMA-005-all-team-sequential-queue-governance`.
- Created branch: `pr/26171-GAMMA-005-all-team-sequential-queue-governance`.
- Push result: PASS. Pushed `pr/26171-GAMMA-005-all-team-sequential-queue-governance` to `origin`.
- PR URL: `https://github.com/ToolboxAid/HTML-JavaScript-Gaming/pull/29`.
- Merge result: not merged; EOD approval required.
- Final main commit before branch: `eaee83f93`.
43 changes: 8 additions & 35 deletions docs_build/dev/reports/codex_changed_files.txt
Original file line number Diff line number Diff line change
@@ -1,35 +1,8 @@
docs_build/dev/reports/PR_26171_BETA_071-tts-profile-emotion-table-manual-validation-notes.md
docs_build/dev/reports/PR_26171_BETA_071-tts-profile-emotion-table-validation.md
docs_build/dev/reports/PR_26171_BETA_071-tts-profile-emotion-table.md
docs_build/dev/reports/codex_changed_files.txt
docs_build/dev/reports/codex_review.diff
docs_build/dev/reports/coverage_changed_js_guardrail.txt
docs_build/dev/reports/dependency_gating_report.md
docs_build/dev/reports/dependency_hydration_reuse_report.md
docs_build/dev/reports/execution_graph_reuse_report.md
docs_build/dev/reports/failure_fingerprint_report.md
docs_build/dev/reports/filesystem_scan_reduction_report.md
docs_build/dev/reports/incremental_validation_report.md
docs_build/dev/reports/lane_compilation_report.md
docs_build/dev/reports/lane_deduplication_report.md
docs_build/dev/reports/lane_input_validation_report.md
docs_build/dev/reports/lane_runtime_optimization_report.md
docs_build/dev/reports/lane_snapshot_report.md
docs_build/dev/reports/lane_warm_start_report.md
docs_build/dev/reports/monolith_trigger_removal_report.md
docs_build/dev/reports/persistent_lane_manifest_report.md
docs_build/dev/reports/playwright_discovery_ownership_report.md
docs_build/dev/reports/playwright_discovery_scope_report.md
docs_build/dev/reports/playwright_structure_audit.md
docs_build/dev/reports/playwright_v8_coverage_report.txt
docs_build/dev/reports/retry_suppression_report.md
docs_build/dev/reports/slow_path_pruning_report.md
docs_build/dev/reports/static_validation_report.md
docs_build/dev/reports/targeted_file_manifest_report.md
docs_build/dev/reports/test_cleanup_performance_report.md
docs_build/dev/reports/test_cleanup_routing_report.md
docs_build/dev/reports/testing_lane_execution_report.md
docs_build/dev/reports/validation_cache_report.md
docs_build/dev/reports/zero_browser_preflight_report.md
tests/playwright/tools/TextToSpeechFunctional.spec.mjs
toolbox/text-to-speech/text2speech.js
M docs_build/dev/reports/PR_26171_GAMMA_005-all-team-sequential-queue-governance.md

docs_build/dev/PROJECT_INSTRUCTIONS.md | 38 ++++++++++--
docs_build/dev/PROJECT_MULTI_PC.txt | 15 +++++
...-governance-instruction-compliance-checklist.md | 26 ++++++++
...ial-queue-governance-manual-validation-notes.md | 24 ++++++++
...MMA_005-all-team-sequential-queue-governance.md | 71 ++++++++++++++++++++++
5 files changed, 170 insertions(+), 4 deletions(-)
Loading
Loading