Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -422,7 +422,7 @@ Parent。软缺口(`soft_continue=true`)下 `swarm_doctor` 同样给出
没有 `error`;`tick_again=false` 与 `retryable=false` 都表示不要再 tick,第一次也写 `retryable=false`,缺席不再当成可以再 tick)。两次 tick 都带
`session_not_failed=true`:先读它,会话没有失败。`loop_fuse` 不在 `error` 里,
preserve 三元组仍指向 `swarm_solidify`。
boot/status 的 `gate_soft_continue` 仍为 true,且不带 `session_not_failed`。
boot/status 的 `gate_soft_continue` 仍为 true,且不带 `session_not_failed`。未完成 run 的软缺口 boot/status 同时写 `tick_again=false`(只看 `gate_soft_continue=true` 的宿主仍可能再 tick)。
`next_steps` 第一条是调用 `swarm_solidify`。
要替换这条 run 才传 `supersede_pending=true`。暂停与压缩检查点仍优先,且不消耗这次计数。
首次准备见 `examples/swarm-quickstart/README.md`。
Expand Down
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## Unreleased

### Fixed
- **MCP 宿主可用性:未完成 run 的软缺口 boot/status 写 `tick_again=false`**:`swarm_boot` 与 `swarm_status` 在未完成 run 且软缺口、`next_action=swarm_solidify` 时带 `tick_again=false`。`gate_soft_continue` 仍为 true,不写 `session_not_failed`。preserve 三元组不动。没有未完成 run 的 soft-continue,以及压缩检查点盖过固化时,不写 `tick_again`。doctor、第一次 tick 与保险丝本来的 `tick_again=false` 不动。不结算这条 run,不写 Parent baseline,不放宽固化门。
- **MCP 宿主可用性:未完成 run 的软缺口 doctor 写 `tick_again=false`**:只在 `soft_continue=true` 且有未完成 run、没有硬阻断时,`swarm_doctor` 带 `tick_again=false`。缺席不再被读成「可以再 tick」。`soft_continue` 仍为 true,不写 `gate_soft_continue`,不写 `session_not_failed`。`next_action` 仍是 `swarm_solidify`,preserve 三元组不动。hint 写明 `fixes` 里的 `evolver doctor --fix` 本工具不执行。没有未完成 run,或 doctor 是硬阻断时,不写 `tick_again`。第一次 tick 与保险丝本来就有 `tick_again=false`,这次不改。不结算这条 run,不写 Parent baseline,不放宽固化门,不执行 `--fix`。
- **MCP 宿主可用性:未完成 run 的软缺口 doctor 指向固化**:`readonly_smoke` 点名的 `swarm_doctor` 在 `soft_continue=true` 且有未完成 run 时带 `next_action=swarm_solidify`、`pending_solidify` 与 preserve 三元组。`hint` 先写现在固化,软缺口仍是建议。不写 `gate_soft_continue`,不写 `session_not_failed`,不结算这条 run,不写 Parent baseline,不执行 `--fix`。没有未完成 run,或 doctor 本身是硬阻断(`ok=false`)时,不另给这个动作。
- **MCP 宿主可用性:未完成 run 的第一次 tick 重定向也写 `retryable=false`**:同一条未完成 run 的两次默认 `swarm_tick` 都带 `retryable=false`。缺席不再被读成「可以再 tick」。第一次仍是 `ok=true`、没有 `error`、`gate_soft_continue` 仍缺席(缺席不是 false,不把严格 false 当成整段会话失败)。保险丝仍是 `ok=false` 与 `loop_fuse=pending_redirect_loop`。不写 Parent baseline,不放宽固化门。
Expand Down
8 changes: 8 additions & 0 deletions DEBUG.md
Original file line number Diff line number Diff line change
Expand Up @@ -1240,3 +1240,11 @@
- **修复**:仅当未完成 run 且 `soft_continue=true`、没有硬 `blockers` 时,doctor 写 `tick_again=false`。`soft_continue` 仍为 true。不写 `gate_soft_continue`,不写 `session_not_failed`。hint 写明 `tick_again=false`,并写明 `fixes` 里的 `evolver doctor --fix` 本工具不执行、固化前不要跑。没有未完成 run,或硬阻断(`ok=false`),不写 `tick_again`。第一次 tick 与保险丝的 `tick_again=false` 不动。不结算,不写 Parent baseline,不放宽固化门,不执行 `--fix`。目录缓存(DEBUG #61)未做假修复。
- **经验**:**同一个「不要再 tick」要写在宿主已经认识的字段上。** doctor 不能借 `soft_continue=false` 来停,也不能借 `gate_soft_continue=false`。
- **仍在**:只读 `soft_continue=true`、完全不看 `tick_again` / `next_action` / `ok` / `retryable` 的宿主,冒烟之后仍可能再 tick。把缺席的 `gate_soft_continue` 当成继续、且不看 `tick_again` 的 tick 重定向(DEBUG #68 余项 1)仍可能再 tick。把保险丝 `ok=false` 当成整段失败、且不读 `session_not_failed` 与 `loop_fuse` 的宿主(余项 2)仍会停掉会话;`ok` 留着 false,是只看 `ok` 的宿主靠它停止空转。`fixes` 仍列出 `evolver doctor --fix`;本工具不执行它。目录缓存(DEBUG #61)没有做假修复。

### 72. 软缺口 boot/status 不写 `tick_again`,缺席被当成再 tick(MCP 易用性,已修)

- **症状**:#71 之后,未完成 run 的软缺口 `swarm_doctor` 已写 `tick_again=false`。同一条 run 上的 `swarm_boot` / `swarm_status` 仍是 `gate_soft_continue=true`、`next_action=swarm_solidify`、preserve 三元组在,没有 `tick_again`。只在 `tick_again` 严格为 false 时才停、把缺席当成再 tick、同时不看 `next_action` 的宿主,只读 boot 或 status 之后仍会 tick。只看 `gate_soft_continue=true` 的宿主也会再 tick;把这个键写成 false 会重开 DEBUG #67。
- **根因**:停 tick 的严格 false 写在 tick 与 doctor 上。boot / status 的软缺口信封没写这个键。缺席不是 false。`gate_soft_continue=true` 的原义是开局 soft-continue,不能改成 false 来停 tick。
- **修复**:仅当未完成 run、软缺口已经挂上(`gate_soft_continue` 仍为 true)、`next_action=swarm_solidify` 时,boot 顶层与 status 写 `tick_again=false`。不写 `session_not_failed`。preserve 三元组不动。没有未完成 run 的 soft-continue 不写 `tick_again`。压缩检查点盖过固化时,boot 顶层与嵌套 status 副本都不留这个键。doctor、第一次 tick 与保险丝的 `tick_again=false` 不动。不结算,不写 Parent baseline,不放宽固化门,不执行 `evolver doctor --fix`。目录缓存(DEBUG #61)未做假修复。
- **经验**:**同一个「不要再 tick」要写在宿主已经认识的字段上,包括只读开机回执。** boot / status 不能借 `gate_soft_continue=false` 来停。
- **仍在**:只看 `gate_soft_continue=true`、完全不看 `tick_again` / `next_action` 的宿主,boot 或 status 之后仍可能再 tick。只读 `soft_continue=true`、完全不看 `tick_again` 的 doctor 冒烟(DEBUG #71 余项)仍可能再 tick。把保险丝 `ok=false` 当成整段失败、且不读 `session_not_failed` 与 `loop_fuse` 的宿主(DEBUG #68 余项 2)仍会停掉会话;`ok` 留着 false,是只看 `ok` 的宿主靠它停止空转。`fixes` 仍列出 `evolver doctor --fix`;本工具不执行它。目录缓存(DEBUG #61)没有做假修复。
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -239,7 +239,7 @@ After `uv sync`, a pull, or any install, **restart the MCP server**. A long-live

Live `tools/list` already publishes `swarm_tick` parameters `prompt_mode` (`full` or `short`) and `checklist_only`, with descriptions on those fields, and read-only `swarm_doctor`. A host catalog that still lists only `agent_name` and `include_prompt`, or that cannot find `swarm_doctor`, is a stale client session. Restarting the server reloads the code; start a new host session so the client reads `tools/list` again.

If a previous run is unfinished, `swarm_boot` keeps `next_action=swarm_solidify`, sets top-level `pending_solidify`, and adds `readonly_smoke` (`tools`: `swarm_doctor` and `swarm_status`, `settles_run`: false). `hint` says to solidify first. A soft gap (`no_baseline` / `pack_absent` / `unmeasured`) still attaches `warning` and `next_steps`, and it does not replace that hint or weaken the gate. A read-only smoke can call `swarm_doctor` or `swarm_status`; neither settles the run nor invents a Parent baseline. A `swarm_tick` in that state does not start a cycle. The first call stays soft (`ok` true, `severity` soft, `cycle_started` false, `progress` false, `redirect_count` 1, `retryable` false, `next_action` still `swarm_solidify`, `last_run` unchanged). An omitted `retryable` is not a license to tick again. The same call again on that run returns `ok` false, `loop_fuse=pending_redirect_loop`, `redirect_reason=pending_redirect_loop`, `severity` soft, `retryable` false, and no `error` field. It still does not start a cycle. `loop_fuse` and that `redirect_reason` are the tick-loop fuse. The code is not an `error` and not a `next_action`. `next_action` stays `swarm_solidify`. `dispatch_reason` stays `pending_solidify`. The first redirect keeps `redirect_reason=pending_solidify` and does not set `loop_fuse`. Connect-time instructions name `loop_fuse=pending_redirect_loop` the same way. The fuse is not a gate failure and not an abandon signal; a soft gap stays on `warning` and `next_steps`. Both returns set `preserve_pending` true, `abandon_run` false, and `action_required` to `swarm_solidify` (boot and status do too while solidify is still next). Do not drop the unfinished run. When a soft gap is present, `gate_soft_continue` is omitted on the first redirect and on the fuse (`tick_again` is false). Omitted is not false: the first redirect keeps `ok` true and sets no `error`, so a host that treats only a strict false as session death stays in the session and does not tick again. Both tick returns set `session_not_failed` true. Read that field before other flags: true means the session is not failed, and `loop_fuse` does not abandon the run when the preserve flags say to call `swarm_solidify`. `next_steps` starts with `swarm_solidify`. Boot and status keep `gate_soft_continue` true while a run is still unfinished, and they do not set `session_not_failed`. Pass `supersede_pending=true` to replace that run. Pause and the compaction checkpoint still refuse the cycle.
If a previous run is unfinished, `swarm_boot` keeps `next_action=swarm_solidify`, sets top-level `pending_solidify`, and adds `readonly_smoke` (`tools`: `swarm_doctor` and `swarm_status`, `settles_run`: false). On a soft gap it also sets `tick_again=false` while `gate_soft_continue` stays true. `hint` says to solidify first. A soft gap (`no_baseline` / `pack_absent` / `unmeasured`) still attaches `warning` and `next_steps`, and it does not replace that hint or weaken the gate. A read-only smoke can call `swarm_doctor` or `swarm_status`; neither settles the run nor invents a Parent baseline. A `swarm_tick` in that state does not start a cycle. The first call stays soft (`ok` true, `severity` soft, `cycle_started` false, `progress` false, `redirect_count` 1, `retryable` false, `next_action` still `swarm_solidify`, `last_run` unchanged). An omitted `retryable` is not a license to tick again. The same call again on that run returns `ok` false, `loop_fuse=pending_redirect_loop`, `redirect_reason=pending_redirect_loop`, `severity` soft, `retryable` false, and no `error` field. It still does not start a cycle. `loop_fuse` and that `redirect_reason` are the tick-loop fuse. The code is not an `error` and not a `next_action`. `next_action` stays `swarm_solidify`. `dispatch_reason` stays `pending_solidify`. The first redirect keeps `redirect_reason=pending_solidify` and does not set `loop_fuse`. Connect-time instructions name `loop_fuse=pending_redirect_loop` the same way. The fuse is not a gate failure and not an abandon signal; a soft gap stays on `warning` and `next_steps`. Both returns set `preserve_pending` true, `abandon_run` false, and `action_required` to `swarm_solidify` (boot and status do too while solidify is still next). Do not drop the unfinished run. When a soft gap is present, `gate_soft_continue` is omitted on the first redirect and on the fuse (`tick_again` is false). Omitted is not false: the first redirect keeps `ok` true and sets no `error`, so a host that treats only a strict false as session death stays in the session and does not tick again. Both tick returns set `session_not_failed` true. Read that field before other flags: true means the session is not failed, and `loop_fuse` does not abandon the run when the preserve flags say to call `swarm_solidify`. `next_steps` starts with `swarm_solidify`. Boot and status keep `gate_soft_continue` true while a run is still unfinished, set `tick_again` false on that soft gap, and they do not set `session_not_failed`. Pass `supersede_pending=true` to replace that run. Pause and the compaction checkpoint still refuse the cycle.

A cold `swarm_status` (this process has not called `swarm_boot`) returns `next_action=swarm_boot` and a short hint. After boot, status keeps `agent_name`, `source_revision`, and any soft `gap` / warnings. `tool_asset_search`, `tool_mailbox_poll`, `tool_cycle_timeline`, and `swarm_approvals` always return `{ok, items, hint}` — an empty match is not a blank body. `swarm_approvals` also keeps `pending` (the same rows as `items`) and `recent`. Read-only `swarm_doctor` mirrors `evolver doctor` without `--fix` (`ok`, soft warnings, command hints in `fixes`). `no_baseline` / `pack_absent` / `unmeasured` stay soft-continue. When a run is unfinished and that report is soft-continue, doctor also sets `next_action=swarm_solidify`, `tick_again=false`, `pending_solidify`, and the preserve triad (`preserve_pending`, `abandon_run=false`, `action_required=swarm_solidify`). `soft_continue` stays true. It still does not settle the run, write a Parent baseline, or execute `evolver doctor --fix`. `gate_soft_continue` and `session_not_failed` stay absent. A hard blocker keeps `ok` false and does not add that action or `tick_again`. The first unfinished-run tick and the fuse already set `tick_again` false.

Expand Down
Loading
Loading