chore(cc-drift): v6.13.10: maxTested to v2.1.296

[askalf]

Drafted by cc-drift-watch.yml

The drift watcher found CC v2.1.296 above the supported range. This PR:

1. Bumps SUPPORTED_CC_RANGE.maxTested from 2.1.295 to 2.1.296 in src/live-fingerprint.ts
2. Bumps the package.json and package-lock.json versions to 6.13.10
3. Adds a ## [6.13.10] - 2026-10-09 section to CHANGELOG.md under ## [Unreleased], with the release note

Items in the drift report

• compat.range (medium): CC v2.1.296 is beyond SUPPORTED_CC_RANGE.maxTested (v2.1.295). 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.295; npm latest is v2.1.296. Re-capture and re-bake the template if any request-shape field changed.
• cch.seed (info): No cch seed for CC v2.1.296 in src/cch.ts (CCH_SEEDS). dario OMITS the cch token for it. This is correct while CC v2.1.296 sends none (2.1.199+). Only add a seed if scripts/check-wire-drift.mjs reports CC re-introduced cch; then run node scripts/cch-calibrate.mjs on a host with claude v2.1.296. dario#528.

Merge and release

• Merge: the platform review gate squash-merges this PR after the required checks pass (build (18|20|22), validate-package-json, analyze, actionlint) and Redline approves. The master ruleset requires an approving review and dismisses it on any later push. It merges only while its package.json version is above the one on master.
• Release: after merge, cc-drift-auto-release.yml tags v6.13.10 and publishes @askalf/dario@6.13.10 to npm (with --provenance) and GHCR. The box autodeploy timer picks it up within about 15 minutes.
• Template: cc-drift-template-watch.yml captures real CC traffic on the self-hosted runner every 30 minutes. If the bundled template drifts against v2.1.296, it opens a separate bot/template-rebake-* PR.

If a required check fails, the PR stays open with the failure visible and the bot branch is kept.

Scope of this script

Only compat.range items are patched here. Template re-capture is handled by cc-drift-template-watch.yml. Scope rotations and URL, clientId, or tokenUrl changes need judgment and stay manual; the bot opens a drift issue for those.

[github-actions]

Live test: ✅ PASS

Head d1a1bd09fe8fb186d9e2abd086b347956ba40f9b on the self-hosted runner: All stages PASS: install/build/cc-detect/cli/doctor/live-probe(pong)

Stages

install: PASS
build: PASS
cc-detect: PASS
cli: PASS
doctor: PASS (exit 1, 19 rows; no credentials, reported cleanly)
live: PASS (pong)

Full workflow run

[sprayberry-redline]

Verdict: approve. The updated bound makes CC 2.1.296 pass the existing compatibility check, whose tests cover the upper boundary and versions above it. The package and lockfile versions agree, and the changelog accurately describes the warning change.