Scored across 27 tools
Several clusters overlap: load_context and resume are explicitly described as producing the same markdown resume, and task_status, task_audit, and load_context all surface task state with only subtle differences in scope. Likewise bundle_inspect, bundle_import_plan, and bundle_import form a three-way cluster where the read-only vs write distinction must be inferred. The descriptions do include usage guidance ("prefer load_context at task start"), so an attentive agent can separate them, but the boundaries are not self-evident.
Strong noun-prefix grouping with a verb/target pattern: task_* (start, update, list, finalize, park, switch, status, audit, handoff, update_verification), bundle_* (export, inspect, import, import_plan), record_* (decision, dead_end, source), usage_* (report, link). Minor deviations are the bare single-word tools checkpoint, resume, diff, and replay, which break the pattern, plus record_source sitting outside the task_* family. Predictable overall.
At 27 tools the surface is heavy, sitting just over the point where a set becomes hard to scan, and it spans several sub-domains (task lifecycle, ledger records, bundles, usage analytics, release preflight). Niche tools like diff, replay, and release_preflight are defensible but add sprawl. The core of the server is well-scoped; the peripheral features are what push it over.
Lifecycle coverage is excellent: task start/update/verify/finalize/park/switch/list/status/audit/handoff plus checkpoints, resume, and replay cover the full working loop, and bundle export/inspect/plan/import covers the transfer loop symmetrically. The notable gap is that nothing can delete, forget, or prune durable state — no way to remove a stale decision, dead end, evidence item, or task — leaving cleanup as a dead end. There is also no configuration or initialization tool.
