Repository navigation
Sign-off: fractal#1547 suspended-seat upgrade #4911
Description
Source
Merge SHA: not merged.
Question for Nathan
Does Nathan accept a coordinated fleet upgrade with fail-closed refusal until every peer is upgraded, as in #1185, or which compatible alternative is required?
Risk
high — The proposal changes a shared contract or authority/privacy boundary.
Evidence
- Johannes's assistant: ready PRs waiting on you (conflicts and red checks), 2026-10-14 #2744 (comment)
- Defer launch changes for suspended seats as a visible apply blocker (#1532) #1547
Completion rule
Compounding Manager records Nathan's answer or sign-off before this sub-issue closes. Agents do not wait for Nathan to self-merge, but all normal gates, exact-head GOs, checks and rulesets still apply. No --admin and no auto-merge. If the source is not merged, Compounding Manager records its merge SHA and asks Nathan for review after merge.
Posted on behalf of @schickling
| field | value |
|---|---|
agent_identity |
unknown |
session |
unknown |
agent_persona |
unknown |
agent_supervisor |
unavailable |
agent_tool |
unknown |
agent_tool_version |
unknown |
agent_runtime |
unknown |
agent_model |
unknown |
worktree |
unknown |
Metadata
Metadata
Assignees
Labels
No labels
Activity