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
{{ message }}
Repository navigation
Commit 6616095
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/contracts/behavior-contracts.yaml
+35-1Lines changed: 35 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -750,7 +750,7 @@ contracts:
750
750
751
751
- id: ACTIVITY-STATE-004
752
752
title: Interrupted turns cannot leave the compact notch running
753
-
status: active
753
+
status: superseded
754
754
statement: A rollout records serial turns for one Codex thread. If a later task_started event appears for that thread before an earlier turn has a terminal event, the earlier turn is superseded and must no longer count as active or keep the compact quota indicator moving. A terminal event explicitly naming a superseded or unknown turn is ignored and must not finish the replacement turn. Active turns from separate rollout files retain their normal priority; when no active task remains, the most recent completion still shows the completion checkmark.
755
755
rationale: A missing terminal event previously left an orphan active turn in a continuously modified rollout file. Because active staleness used the file modification time, the orphan could hold the compact notch in its running animation for hours after the visible task completed.
positive: "A child rollout with a task_started event and no terminal event contributes neither an active row nor a running count; a completed child rollout is absent from recent conversations; a direct `source: vscode` rollout remains eligible."
798
+
negative: "A child-agent nickname appears in the expanded list, a child-only orphan keeps the compact notch in the running state, or decoding a direct string source causes the top-level rollout to disappear."
Copy file name to clipboardExpand all lines: docs/decisions/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,5 +12,6 @@ Record decisions here only when they affect active behavior contracts, could be
12
12
|[008-local-thread-summary-titles](008-local-thread-summary-titles.md)| active |`CONVERSATION-TITLE-041`, `PRIVACY-BOUNDARY-005`| Resolve row labels from Codex's read-only thread summaries rather than rollout messages |
13
13
|[009-keep-notch-visible-across-full-screen-apps](009-keep-notch-visible-across-full-screen-apps.md)| active |`NOTCH-VISIBILITY-042`| Keep the requested notch surface available in native and borderless full-screen applications |
14
14
|[010-layer-backed-quota-motion](010-layer-backed-quota-motion.md)| active |`QUOTA-SEMANTICS-043`| Keep 8 FPS visual motion while moving persistent ring and wave frames out of SwiftUI |
15
+
|[011-ignore-subagent-rollouts](011-ignore-subagent-rollouts.md)| active |`ACTIVITY-STATE-005`, `CONVERSATION-TITLE-041`| Ignore child-agent rollouts in notch activity and conversation history |
15
16
16
17
New decisions must include `status`, `contract_ids`, rejected alternatives, and consequences. When a decision changes, retain the old document and point to the new one with `superseded_by`.
0 commit comments