lsm / neokai / 25830865787

81%

push

github

feat: add publish_task and archive_task MCP tools (#1893)

* feat: add publish_task and archive_task MCP tools for draft lifecycle

Adds two new MCP tools to enable full draft task lifecycle management
through the MCP tool surface, fixing the inability to transition tasks
from draft to open or archived status.

- publish_task: transitions draft → open, making tasks eligible for
  orchestration by the runtime tick loop
- archive_task: transitions tasks to archived (terminal state) from
  any status that allows it (draft, done, cancelled, blocked, review,
  approved)

Both tools are registered in space-agent-tools (always available) and
node-agent-tools (via optional callbacks wired by TaskAgentManager).

Closes #1892

* fix: emit space.task.updated events from node-agent publish/archive callbacks

The onPublishTask and onArchiveTask callbacks in TaskAgentManager did not
emit `space.task.updated` events, so the archive cleanup pipeline
(subscribeToTaskArchiveEvents → session teardown, worktree removal) was
never triggered when a node agent archived a task.

Also corrects the archive_task tool description: `open` is not a valid
source status for the `archived` transition (valid: draft, done, cancelled,
blocked, review, approved).

* fix: route archive through setTaskStatus and log event-publish failures

P1: SpaceTaskManager.archiveTask() now delegates to setTaskStatus()
instead of calling taskRepo.archiveTask() directly. This ensures
pendingCheckpointType/pendingCompletion* fields are cleared when
leaving 'review', and postApproval* fields are cleared when leaving
'approved' — preventing stale workflow metadata on archived tasks.

P2: Replaced silent .catch(() => {}) in onPublishTask/onArchiveTask
event emission with .catch((err) => log.warn(...)) to surface
diagnostic info when the event bus publish fails.

* fix: update archiveTask error message assertions after setTaskStatus refactor

The existing tests expected the old error message format from
arch... (continued)

8334 of 11605 branches covered (71.81%)

Branch coverage included in aggregate %.

112 of 158 new or added lines in 5 files covered. (70.89%)

65934 of 78629 relevant lines covered (83.85%)

291.11 hits per line