Repository navigation
fix(mcp): drop doctor --fix from unfinished tick and fuse envelopes - #29
Merged
Merged
Conversation
The first unfinished-run tick and the pending_redirect_loop fuse still listed evolver doctor --fix as a current step. Strip that exact command the same way boot, status, and doctor already do, and leave the soft-gap flags unchanged. Co-authored-by: Steper Lin <linker.lin@live.com>
1 task done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
未完成 run 的软缺口固化引导上,第一次
swarm_tick和loop_fuse=pending_redirect_loop不再把精确的evolver doctor --fix当成当前步骤。引导仍是swarm_solidify,与 #28 对 doctor / boot / status 的口径相同。What changed
_pending_tick_redirect在第一次重定向和保险丝上调用既有的_defer_doctor_fix_on_steer:commands去掉精确的evolver doctor --fix,next_steps里点名它的句子改成先固化。evolver bench freeze/evolver bench baseline仍留在清单里。没有未完成 run 的 tick、boot、doctor 仍列出evolver doctor --fix。gate_soft_continue在这两份 tick 信封上仍缺席,不写成 false。tick_again=false与保险丝的ok=false不动。本工具不执行--fix,不写 Parent baseline,不放宽固化门。How to test
uv run pytest tests/test_mcp_host_usability_pending_smoke.py tests/test_mcp_host_usability_p0.py tests/test_mcp_host_usability_p1.py tests/test_mcp_host_usability_p2.py tests/test_mcp_host_usability_polish.py tests/test_swarm.py::TestTick tests/test_swarm.py::TestBootAndStatus tests/test_mcp_server.py tests/test_mcp_protocol.py tests/test_open_box_setup_doctor.pyuv run ruff check src tests && uv run ruff format --check src tests && uv run mypy srccommands不含精确的evolver doctor --fix,next_action仍是swarm_solidify。没有未完成 run 的 tick 仍列出该命令。Risk
Low -- MCP 宿主回执文案与命令清单。不改固化门、Parent baseline、
ok或软缺口旗标。Harness/evaluator governance
Upstream governance surface: swarm instrument wording and unfinished-run tick envelopes only
Downstream EvoX impact: N/A
Rollout-local scope: N/A
Promotion boundary: N/A
Evaluator mismatch sets: N/A
Non-regression evidence: pending-smoke, sibling usability, tick/boot, MCP protocol, and open-box tests
Fix-severity review: low
Owner approval: N/A
Security boundary: does not execute
evolver doctor --fixand does not write a Parent baselineRollback: revert this commit
Live promotion: no
Autonomous evaluator self-editing: no
Self-check
uv run pytest(related suites),uv run ruff check src tests,uv run ruff format --check src tests,uv run mypy src.Related
Follows #28. That change left the first unfinished-run tick and the fuse envelopes listing
evolver doctor --fix.