Clarify team-neutral branch workflow wording

Author: ToolboxAid

docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md

@@ -93,7 +93,7 @@ OWNER override wording:
 `OWNER override approved: <reason>`
 
 OWNER follows the same safety rules:
-- One active OWNER branch at a time.
+- One active Team 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.

docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md

@@ -9,7 +9,8 @@ Keep active work attached to the correct assigned team, branch, and OWNER decisi
 
 ## Active Work Lock
 
-- Work must occur on the assigned team or OWNER branch.
+- Work must occur on the active team branch.
+- This rule applies to all teams: OWNER, Team Alfa, Team Bravo, Team Charlie, Team Delta, and any future team.
 - An assigned work item keeps its owner of record until complete or OWNER reassignment.
 - Work must not move to another team, branch, or PR without OWNER approval.
 - A team with no active assignment, active branch, or active PR is inactive.
@@ -26,7 +27,7 @@ Keep active work attached to the correct assigned team, branch, and OWNER decisi
 - Do not create a PR branch unless current branch is `main`, worktree is clean, `main...origin/main` is `0 0`, and `HEAD` SHA matches the published EOD SHA.
 - Follow the canonical START / WORK / END lifecycle in `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`.
 - Keep work on the active branch until the PR is merged, the branch is retired, EOD closeout begins, or OWNER says to return to `main`.
-- For OWNER-approved stacked/sequential workstreams, sequential PR work stays on the active branch/workstream during the day and does not return to `main` between PRs.
+- For OWNER-approved stacked/sequential workstreams, PR branches/commits stay on the active team branch/workstream during the day and do not return to `main` between PRs.
 - Do not commit directly to `main`.
 - HARD STOP before committing if current branch is `main`.
 - HARD STOP if the branch changes unexpectedly during implementation.

docs_build/dev/ProjectInstructions/addendums/pr_workflow.md

@@ -28,18 +28,19 @@ Define the standard pull request workflow for Game Foundry Studio.
 
 ## Daily Branch Workflow
 
-OWNER-approved daily workflow:
+Team-neutral daily workflow:
 
 - SOD starts from the latest synchronized `main`.
-- SOD creates or updates one active team, OWNER, or scoped workstream branch.
-- All implementation commits go to the active branch, not `main`.
-- Sequential PRs stay on the active branch/workstream during the day when OWNER assigned a stacked or sequential workstream.
+- SOD creates or updates one active team branch/workstream.
+- Work must be committed only to the active team branch.
+- PR branches/commits stay on the active team branch/workstream during the day when OWNER assigned a stacked or sequential workstream.
 - Do not return to `main` between stacked/sequential PRs in the same active workstream.
 - `main` is only the SOD baseline and the EOD return target, unless OWNER explicitly approves an intermediate merge checkpoint.
 - EOD merges or closes OWNER-approved work, pushes, returns to `main`, and verifies:
   - current branch is `main`
   - worktree clean
   - local/origin sync is `0 0`
+- This rule applies to all teams: OWNER, Team Alfa, Team Bravo, Team Charlie, Team Delta, and any future team.
 
 This section supersedes older active wording that implies returning to `main` between every PR inside an OWNER-approved stacked/sequential workstream.
 

docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md

@@ -91,7 +91,7 @@ main...origin/main
 HEAD equals published EOD SHA
 ```
 
-Only after ALL four pass may a branch be created or the active OWNER-approved workstream branch be updated.
+Only after ALL four pass may a branch be created or the active team branch/workstream be updated.
 
 Create the PR branch:
 
@@ -112,11 +112,13 @@ From branch creation until merge:
 - Remain on the PR branch.
 - Never checkout `main`.
 - Commit only on the PR branch.
+- Work must be committed only to the active team branch.
 - Push only the PR branch.
 - Execute validation from the PR branch.
 - Open/update the PR from the PR branch.
-- For OWNER-approved stacked/sequential workstreams, remain on the active workstream branch between sequential PRs during the day.
+- For OWNER-approved stacked/sequential workstreams, PR branches/commits stay on the active team branch/workstream between sequential PRs during the day.
 - Do not return to `main` between sequential PRs in the same active workstream unless OWNER explicitly approves an EOD or intermediate merge checkpoint.
+- This rule applies to all teams: OWNER, Team Alfa, Team Bravo, Team Charlie, Team Delta, and any future team.
 
 Hard Stops:
 

docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md

@@ -102,6 +102,8 @@ Each PR in the stack still follows the canonical START / WORK / END lifecycle an
 
 When OWNER gives one large Codex command for a tool MVP stack, Codex may continue from one completed PR to the next without stopping for a conversational checkpoint, unless a blocker listed in this standard occurs.
 
-During an OWNER-approved day workstream, sequential PRs stay on the active workstream branch and do not return to `main` between PRs.
+During an OWNER-approved day workstream, PR branches/commits stay on the active team branch/workstream and do not return to `main` between PRs.
+
+This rule applies to all teams: OWNER, Team Alfa, Team Bravo, Team Charlie, Team Delta, and any future team.
 
 The final PR in the stack must perform normal EOD closeout or OWNER-approved merge-checkpoint closeout and stop all work after returning to synchronized main.

docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment.md

@@ -18,8 +18,10 @@ No runtime code, UI code, API code, database code, start_of_day files, history s
 
 - Clarified SOD/day-work/EOD workflow:
   - SOD starts from latest synchronized `main`.
-  - Active work happens on one active team, OWNER, or scoped workstream branch.
-  - Sequential PRs stay on the active workstream branch during the day.
+  - Active work happens on one active team branch/workstream.
+  - Work must be committed only to the active team branch.
+  - PR branches/commits stay on the active team branch/workstream during the day.
+  - The rule applies to all teams: OWNER, Team Alfa, Team Bravo, Team Charlie, Team Delta, and any future team.
   - `main` is only the SOD baseline and EOD return target unless OWNER approves a merge checkpoint.
 - Added Product Owner testable completion definition.
 - Confirmed `Browser -> API -> Database`, one API/service contract across environments, and `Local API` as the shared API running locally.
@@ -52,4 +54,4 @@ No runtime code, UI code, API code, database code, start_of_day files, history s
 
 Reviewers should verify that daily team work now has one clear model:
 
-SOD from synchronized `main`, work on active workstream branch, no return to `main` between stacked/sequential PRs, and EOD return to synchronized `main`.
+SOD from synchronized `main`, work on the active team branch/workstream, no return to `main` between stacked/sequential PRs, and EOD return to synchronized `main`.

docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_branch-validation.md

@@ -7,7 +7,7 @@ Date: 2026-06-26
 | --- | --- | --- |
 | Started from `main` | PASS | `main...origin/main` was `0 0` before branch creation. |
 | Worktree clean before branch | PASS | Start gate passed. |
-| Work committed only to OWNER branch | PASS | Branch is `PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment`. |
+| Work committed only to active team branch | PASS | Branch is `PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment`; no commit was made to `main`. |
 | No direct commit to `main` | PASS | No commit was made on `main`. |
 | Active instruction files only | PASS | Changes are under `docs_build/dev/ProjectInstructions/` plus required reports. |
 | Runtime files changed | PASS | None. |

docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_manual-validation-notes.md

@@ -6,7 +6,8 @@ Date: 2026-06-26
 ## Reviewer Checklist
 
 - Confirm `main` is described as SOD baseline and EOD return target, not the place for day-work commits.
-- Confirm stacked/sequential PRs stay on the active workstream branch during the day.
+- Confirm stacked/sequential PR branches/commits stay on the active team branch/workstream during the day.
+- Confirm this branch workflow applies to all teams: OWNER, Team Alfa, Team Bravo, Team Charlie, Team Delta, and any future team.
 - Confirm Product Owner testable excludes shell-only, placeholder-only, planned-only, or route-only completion.
 - Confirm page-level Playwright tests follow runtime page paths.
 - Confirm `Local API` means the shared API running locally.

docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_requirements-checklist.md

@@ -6,6 +6,7 @@ Date: 2026-06-26
 | Requirement | Result | Notes |
 | --- | --- | --- |
 | Daily branch workflow documented | PASS | Added SOD/day-work/EOD wording. |
+| Branch workflow is team-neutral | PASS | Active wording says work commits and sequential PR branches/commits stay on the active team branch/workstream and applies to all teams. |
 | Product Owner testable definition documented | PASS | Added in PR workflow and Tool MVP standard. |
 | API/environment rule confirmed | PASS | Added `Browser -> API -> Database`, shared API contract, and Local API definition. |
 | Page-level Playwright organization added | PASS | Added runtime path to test path rules and examples. |

docs_build/dev/reports/PR_26177_OWNER_009-project-instructions-workflow-testable-tests-alignment_validation-lane.md

@@ -18,6 +18,8 @@ rg -n "Product Owner testable|page-level Playwright|Browser -> API -> Database|L
 - PASS: changed files are active Project Instructions plus required reports only.
 - PASS: no runtime/UI/API/database/start_of_day files changed.
 - PASS: no `Sprite Studio V2` active backlog owner remains.
+- PASS: no OWNER-only branch workflow wording remains.
+- PASS: active branch workflow says commits and sequential PR branches/commits stay on the active team branch/workstream.
 - PASS: Product Owner testable text exists.
 - PASS: page-level Playwright organization text exists.
 - PASS: API/environment contract text exists.