fix: distiller MCP-tool pin + capture status; yvh diagnosis (0.25.1)

[Shahinyanm]

yvh diagnosis: the worker is NOT under-recording

Investigated the claim that the classify-worker under-records (claude-memory-yvh). Evidence says it's healthy:

• pending/ queue: 0 files — fully drained.
• Telemetry: 12,642 classifications, 0 errors across all projects, rich distribution (5,964 findings, 1,465 rejections, 1,285 decisions, 2,376 evidence, …; 9,181 confirmed + 3,461 suggested).

So a task like tj-aknbh66f8n looking "interrupted" was genuinely incomplete (investigation without conclusion) + compaction markers — complete left it open correctly. Not a capture bug. No worker fix shipped (don't fix what isn't broken).

The real find: the global .capture-disabled marker was set (from an earlier debugging step this session), silencing auto-capture across all projects — re-enabled at runtime with capture on.

Code changes

1. Distiller subagent: drop fragile MCP tool pin. task-journal-distiller listed the journal MCP tools under one marketplace-specific prefix (mcp__plugin_task-journal_task-journal__*). On any install with a different prefix the agent would silently lack event_add and be useless. Dropped the explicit tools: list so it inherits the session tools and can always reach the journal MCP. (Found in review of feat: in-session compaction distiller subagent + advisory (0.25.0) #44.)
2. task-journal capture status — reports ON/OFF of the realtime-capture marker without changing it (the bare capture had only on/off).

Tests

capture_status_reports_current_state (ON fresh, OFF after off, status doesn't flip). Full local gate green.

🤖 Generated with Claude Code