fix(server): ignore Claude command lifecycle messages

[naveed949]

What Changed

• Ignore Claude SDK command_lifecycle wire messages at the adapter boundary.
• Add focused regression coverage for both started and completed lifecycle notifications.
• Preserve the existing warning path for genuinely unknown or high-priority SDK messages.

Why

Claude Code emits command_lifecycle messages as routine command bookkeeping. The adapter previously treated these unrecognized wire messages as runtime.warning events, which made healthy turns appear as red failures in the Work Log. Consuming them silently at the provider boundary keeps the canonical runtime model and clients free of provider-only bookkeeping.

Closes #6093.

Validation

• vp test run apps/server/src/provider/Layers/ClaudeAdapter.test.ts — 68 passed.
• Server test suite — 230 test files passed, 2 skipped; 2,507 tests passed, 7 skipped.
• Focused formatting, lint, and server typechecking passed.
• One code-review pass completed against 038560e58036d51b2576b3c2cd9170a194cefe9e on both Standards and Spec axes; valid findings were fixed and focused tests rerun.

Checklist

• This PR is small and focused
• I explained what changed and why
• No UI changes; screenshots are not applicable
• No animation or interaction changes; video is not applicable

Note

Ignore command_lifecycle SDK messages in handleSdkMessage

Adds an early return in ClaudeAdapter.ts to drop SDK messages of type command_lifecycle before they reach the main switch, preventing any runtime events or lifecycle actions from being emitted. A test in ClaudeAdapter.test.ts verifies that only a runtime.warning for the processed system notification is observed.

^{Macroscope summarized ec0126c.}

---

Note

Low Risk
Small, provider-boundary change with regression tests; no auth, data, or API contract changes.

Overview
Stops routine Claude SDK command_lifecycle wire messages (started / completed) from surfacing as runtime.warning events in the Work Log.

handleSdkMessage in ClaudeAdapter now returns early for that message type after logging and thread binding, so provider-only bookkeeping never reaches the main switch or unknown-message warning path. A focused adapter test asserts that started and completed lifecycle notifications produce no runtime events while high-priority system notifications still emit warnings as before.

^{Reviewed by Cursor Bugbot for commit ec0126c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6558255d-350c-4fe4-aabf-a2ea2b025137

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved ec0126c

This PR adds a 5- line early return to silently consume internal ' command_ life cycle' messages, preventing unnecessary runtime warnings. The change is minimal, uses existing patterns, and has comprehensive test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}