chore: release v0.0.24

[ScriptedAlchemy]

🤖 New release

• tracedecay: 0.0.23 -> 0.0.24

Changelog

0.0.24 - 2026-07-02

Added

• (automation) combined reflector+skill scheduler pass (Hermes G9/R7)
• (cli) enforce MCP tool CLI/skill parity and rich subcommand help

Fixed

• satisfy clippy pedantic lints in windows read retry
• (sync) retry transient Windows file locks in read_source_file

Other

• (claude) tolerate CRLF agent frontmatter
• Merge remote-tracking branch 'origin/master' into codex/host-integration-parity
• Merge remote-tracking branch 'origin/master' into codex/host-integration-parity
• Merge pull request feat(automation): couple scheduler triggering to LCM session activity #218 from ScriptedAlchemy/codex/activity-coupled-triggering
• Merge pull request [codex] Track automation-applied outcome feedback #226 from ScriptedAlchemy/codex/hermes-parity-r10-outcomes
• Merge pull request feat(cli): enforce MCP tool CLI/skill parity and rich subcommand help #213 from ScriptedAlchemy/codex/tool-skill-cli-parity
• (cli) trim tool help test commentary

Added

• Claude Code installs now register SessionStart and PostToolUse lifecycle hooks, matching the freshness/steering coverage Cursor, Codex, and Kiro already had: SessionStart reports index freshness and injects the LCM context-recovery hint after compaction; PostToolUse notifies the daemon for targeted incremental sync after edits and shell commands. Existing installs pick the hooks up via the post-upgrade backfill or tracedecay doctor.
• The CLI-fallback steering ("if MCP fails, use tracedecay tool ...") now reaches every host with a prompt-rules surface — Claude Code, Copilot/VS Code, Gemini, OpenCode, Kimi, Vibe, and Kiro — instead of only the Cursor rule and Codex session hook.

Fixed

• serve no longer exits when project resolution fails at startup — MCP hosts (Cursor especially) never retry a failed server spawn, so one startup exit over a recoverable config problem (uninitialized project, ambiguous global fallback, bad --path) turned every later tool call in the session into "Timed out waiting for connection". serve now stays alive in a degraded mode: it completes the MCP handshake, lists the real tools, and answers each tool call with an actionable error naming the failure, the fix, and the tracedecay tool … CLI fallback. It rechecks the project on every tool call and recovers in-session once tracedecay init (or a corrected path) makes resolution succeed — no server toggle or window reload needed.
• serve now tolerates a literal unexpanded --path ${workspaceFolder} — Cursor's headless agent-session MCP scopes spawn the plugin's serve command without expanding the template variable and never retry the failed scope, which surfaced as "Timed out waiting for connection" on every tool call. serve now discards an unexpanded ${...} template value with a stderr warning and falls back to project discovery where possible, requiring a unique registered project when discovery reaches the global registry in this mode. Rationale and details in cursor-plugin/README.md.

Added

• tracedecay doctor --agent cursor now diagnoses dead Cursor MCP scopes — best-effort scan of Cursor's recent MCP logs for tracedecay spawn failures (literal unexpanded ${workspaceFolder} paths, Connection failed: MCP error -32000, degraded-mode notices) with concrete remediation ("toggle the MCP server in Cursor Settings → MCP or reload the window"), plus a plugin-bundle-version-vs-binary-version staleness check that points at tracedecay update-plugin.

---

This PR was generated with release-plz.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 934d0b8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR