You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs_build/database/seed/messages.json
+2-5Lines changed: 2 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -24,12 +24,9 @@
24
24
"Sad",
25
25
"Mysterious"
26
26
],
27
-
"messages_tts_profiles": [
28
-
"Browser Speech Default",
29
-
"Narration Preview"
30
-
],
27
+
"messages_tts_profiles": [],
31
28
"messages_records": [],
32
29
"messages_segments": []
33
30
},
34
-
"note": "Seed names are applied by the server-side Messages Postgres service. Browser pages must not seed authoritative records."
31
+
"note": "Seed names are applied by the server-side Messages Postgres service. Browser pages must not seed authoritative records. Retired TTS parent profiles Default Balanced Profile, Hero, Merchant, Neutral, and Robot are pruned server-side and must not be reintroduced as seed records. Empty TTS parent profiles without child emotion settings are also pruned instead of repaired with fallback children."
Copy file name to clipboardExpand all lines: docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -145,7 +145,9 @@ Rules:
145
145
- Each PR must be committed, pushed, and opened as a draft PR.
146
146
- Each PR starts at PR Open after the branch and PR identity are named.
147
147
- Each PR plans and builds on the same source branch after PR Open.
148
-
- Each PR reaches Closed only after main-return, clean-worktree, local/origin `0/0`, no-untracked-files, required-report, required-ZIP, backlog, applicable tool-state, and retained-branch-disposition gates pass.
148
+
- During assigned team-day work, sequential PRs must remain on the assigned team branch until EOD or an owner-approved merge checkpoint.
149
+
- Returning to `main` between sequential team PRs is prohibited.
150
+
- Each PR reaches Closed only after clean-worktree, local/origin sync for the active source branch, no-untracked-files, required-report, required-ZIP, backlog, applicable tool-state, retained-branch-disposition gates, and the applicable EOD/main-verification gate pass.
149
151
- A team must not begin another PR until its previous PR is Closed unless OWNER documented an explicit stacked PR chain.
150
152
- Do not commit directly to main.
151
153
- Do not merge without explicit owner approval.
@@ -174,6 +176,7 @@ Rules:
174
176
- Each PR may be committed and pushed during active work.
175
177
- Each PR may be opened as a draft PR during active work.
176
178
- Each PR must move through PR Open, Plan, Build, Validation, Approved, Merged, Main Verified, and Closed in order.
179
+
- For assigned team-day work, Main Verified occurs only at EOD or an owner-approved merge checkpoint; it is not permission to return to `main` between sequential PRs.
177
180
- Plan, Build, validation, reports, ZIP packaging, and closeout must stay tied to the same PR identity and source branch.
178
181
- Source branches are retained by default after merge and closeout.
179
182
- A team must not begin another PR until its previous PR is Closed unless OWNER documented an explicit stacked PR chain.
@@ -188,6 +191,7 @@ Rules:
188
191
Conflict note:
189
192
- Older wording that says each PR must create its own branch remains preserved.
190
193
- This all-team clarification allows an approved existing team, OWNER, or scoped PR branch when the owner assigns that dependency model.
194
+
- The Day Work / EOD Merge Rule below overrides older main-return wording during assigned team-day sequences.
191
195
- If a branch model is unclear, owner approval is required before continuing.
192
196
193
197
## Day Work / EOD Merge Rule
@@ -198,7 +202,11 @@ During active work:
198
202
- Pushes are allowed and expected.
199
203
- Draft PRs are allowed and expected.
200
204
- Direct commits to main are prohibited.
205
+
- Codex must stay on the assigned team branch until EOD or an owner-approved merge checkpoint.
206
+
- Returning to `main` between sequential PRs in the same assigned team-day workstream is prohibited.
201
207
- Merges to main are prohibited unless explicitly approved by the owner.
208
+
- Any staged changes, unstaged changes, unmerged state, or direct commit on `main` during team work is a governance failure.
209
+
- If that failure occurs, Codex must hard-stop, move the scoped work to the active team branch, restore `main` to a clean state, document the correction, and continue only from the team branch.
0 commit comments