Objective
Repair execution-auth pinning, plugin refresh, resume/fork candidate selection, thread persistence, and TUI safety-retry history without hiding user-visible state loss.
Finish Line
Pinned execution auth remains stable until its account is removed, plugin skills refresh after auth changes, resume/fork selects the correct state-backed rollout and thread identity, rollback persists correctly, and safety retries preserve steers/interruption notices without duplicated prompts or extra history items.
Current Status
State: waiting behind the current #706 → #707 release sequence; no implementation stage has started.
Run 31973347222 includes deterministic failures in account pinning, plugin routing after auth switch, three exec resume/fork tests, thread rollback, session provenance/turn environment restoration, and three TUI safety-buffering tests. These remain behavior failures rather than simple snapshot churn; the TUI snapshots show one extra retained history/rendered item and require behavior review before acceptance.
Next action when promoted by #703: remeasure the cluster from the then-current immutable main, classify persistence/auth defects separately from TUI safety behavior, and choose the smallest state-ownership stage with integration coverage.
Acceptance Criteria
Relationships
Objective
Repair execution-auth pinning, plugin refresh, resume/fork candidate selection, thread persistence, and TUI safety-retry history without hiding user-visible state loss.
Finish Line
Pinned execution auth remains stable until its account is removed, plugin skills refresh after auth changes, resume/fork selects the correct state-backed rollout and thread identity, rollback persists correctly, and safety retries preserve steers/interruption notices without duplicated prompts or extra history items.
Current Status
State: waiting behind the current #706 → #707 release sequence; no implementation stage has started.
Run
31973347222includes deterministic failures in account pinning, plugin routing after auth switch, three exec resume/fork tests, thread rollback, session provenance/turn environment restoration, and three TUI safety-buffering tests. These remain behavior failures rather than simple snapshot churn; the TUI snapshots show one extra retained history/rendered item and require behavior review before acceptance.Next action when promoted by #703: remeasure the cluster from the then-current immutable
main, classify persistence/auth defects separately from TUI safety behavior, and choose the smallest state-ownership stage with integration coverage.Acceptance Criteria
Relationships
31973347222.