feat: Sync Claude ACP adapter to v0.30.0 (SDK 0.2.112)

[charlesvien]

Problem

Adapter was pinned to v0.22.2 and missing several upstream fixes and features from the Claude ACP reference implementation.

Closes #1692

Changes

1. Bump claude-agent-sdk to 0.2.112, ACP SDK to 0.19.0 and anthropic SDK to 0.89.0
2. Add null-safe guards on all usage token fields from SDK
3. Fix SettingsManager race condition with initPromise to prevent concurrent initialize()/setCwd() corruption
4. Add idle state (session_state_changed) as end-of-turn signal via CLAUDE_CODE_EMIT_SESSION_STATE_EVENTS=1
5. Fire mid-stream usage_update from message_start/message_delta events
6. Add emitRawSDKMessages opt-in for raw SDK message relay
7. Add xhigh effort level and call applyFlagSettings on effort changes
8. Log warning for non-ENOENT settings file errors instead of silently swallowing

How did you test this?

Manually

[charlesvien]

• feat: Add usage limit detection and upgrade prompt #1750
• feat: Add auto permission mode for Claude adapter #1749
• feat: Sync Claude ACP adapter to v0.30.0 (SDK 0.2.112) #1748 👈 (View in Graphite)
• fix: Misc bugs and polish #1746
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Prompt To Fix All With AI

This is a comment left during a code review.
Path: packages/agent/src/adapters/claude/claude-agent.ts
Line: 595

Comment:
**Missing null-coalescing on `output_tokens` in `message_delta` handler**

Every other field in this block uses `?? lastStreamUsage.<field>` as a fallback, but `output_tokens` is assigned directly from `u.output_tokens`. If the SDK returns `null` here (the entire motivation for the null-safe guards in this PR), `lastStreamUsage.output_tokens` will silently become `null`, and `nextTotal` will be computed incorrectly since `null` coerces to `0` in JS arithmetic — dropping any previously accumulated output token count from the total.

```suggestion
                  output_tokens: u.output_tokens ?? lastStreamUsage.output_tokens,
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: packages/agent/src/adapters/claude/claude-agent.ts
Line: 1408-1411

Comment:
**Inconsistent `void` vs `await` for `applyFlagSettings`**

The first call to `applyFlagSettings` (when setting a new effort level) is `await`ed, but the reset path here and the `syncEffort` path (a few lines below) use `void` instead. If `applyFlagSettings` fails silently in the reset or sync paths, the SDK effort level state could diverge from `this.session.effort` without any observable error. Consider using `await` (or at minimum being intentional and adding a comment) for consistency.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "Sync Claude ACP adapter to v0.30.0 (SDK ..." | Re-trigger Greptile}

[charlesvien]

Merge activity

• Apr 21, 7:57 PM UTC: @charlesvien merged this pull request with Graphite.