chore(cc-drift): v4.8.18 — maxTested → v2.1.157

[askalf]

Auto-drafted by cc-drift-watch.yml

The drift watcher flagged CC v2.1.157 as outside the current supported range. This PR:

1. Bumps SUPPORTED_CC_RANGE.maxTested from 2.1.156 → 2.1.157 in src/live-fingerprint.ts
2. Bumps package.json version → 4.8.18
3. Promotes ## [Unreleased] in CHANGELOG.md to ## [4.8.18] - 2026-05-29 and appends the drift-fix bullet

Items in the drift report

• compat.range (medium) — CC v2.1.157 is beyond SUPPORTED_CC_RANGE.maxTested (v2.1.156). Run the e2e suite against the new CC and bump maxTested in src/live-fingerprint.ts — users on the new CC currently get a soft "untested-above" warning from dario doctor.
• template.version (low) — baked cc-template-data.json is v2.1.156; npm latest is v2.1.157. Re-capture the template (MITM a real CC v2.1.157 request) if any fingerprint-sensitive field (system prompt, header order, metadata shape, beta flags) changed.

What happens when you merge this

A separate workflow (cc-drift-auto-release.yml) fires on merge of any version-bumping PR to master. It reads package.json from master, tags v4.8.18, creates the GitHub release, and runs npm publish --provenance + the GHCR docker push inline — all in one run (the old separate publish.yml was removed in #369). Net: merging this PR ships @askalf/dario@4.8.18 to npm within ~3 minutes, no further maintainer action.

Maintainer checklist before merging

• Install the new CC locally: npm install -g @anthropic-ai/claude-code@2.1.157
• Run dario doctor and confirm it comes back clean against v2.1.157
• Template fingerprint is auto-verified every 30 min by cc-drift-template-watch.yml (live capture on the self-hosted runner); if the wire format actually drifts it opens its own bot/template-rebake-* PR. No manual capture needed here unless that watcher is failing.
• Confirm the CHANGELOG entry under ## [4.8.18] reads cleanly. The bot wrote a short factual line; feel free to rewrite with more context.
• Mark as ready for review + merge. Auto-merge will ship it through CI, and the auto-release workflow handles the tag + release + npm publish.

About this auto-draft

Only compat.range items are auto-patched by this script. Template re-capture is auto-handled separately by cc-drift-template-watch.yml. The remaining categories (scope rotations, URL / clientId / tokenUrl changes) require judgment and stay manual — the bot opens the plain drift-issue for those as before.

---

Generated by scripts/auto-draft-drift-fix.mjs. Closes the detection-latency arc: #112 (CF bypass), #113 (hourly cadence), #114 (auto-draft PR).

[github-actions]

Compat test: ✅ PASSED

Ran node test/compat.mjs against dario proxy --passthrough on the self-hosted runner for commit a41a7e562223c38b083a3da1f1cb37bab45dbd61.

Output

============================================================
  dario Compatibility Validation (direct Anthropic, x-api-key)
  2026-05-29T21:09:21.634Z
============================================================

--- Anthropic Messages API (Hermes) ---
✅ #1 Anthropic non-stream: "COMPAT OK" | thinking_injected=false | service_tier=-
✅ #2 Anthropic stream: 8 events | order=correct | "**STREAM COMPAT**"
✅ #3 SSE framing: event:/data: pairs correctly paired

--- Passthrough Verification --- (skipped: requires routing through dario)
--- OpenAI Compat --- (skipped: requires dario OpenAI shim)

--- Tool Use (OpenClaw) ---
✅ #4 Tool use: tool=get_weather | input={"location":"Tokyo"}
✅ #5 Tool use stream: 12 events | tool_use=true | input_json_delta=true

--- Header Visibility ---
✅ #6 Header visibility: request-id=true | ratelimit=true (12 headers)

============================================================
  RESULTS: 6 passed, 0 failed, 0 warnings
============================================================

Full workflow run