@askalf/dario 5.2.10 → 5.2.12

package/dist/accounts.d.ts

@@ -160,3 +160,36 @@ export declare function ensureLoginCredentialsInPool(alias?: string): Promise<st
  * back-filled snapshot.
  */
 export declare function resyncLoginFromCredentialsIfStale(): Promise<'no-pool' | 'no-login' | 'no-creds' | 'in-sync' | 'resynced' | 'creds-stale'>;
+/**
+ * Mirror the pool's freshly-refreshed `login` account token back into the
+ * legacy `~/.dario/credentials.json` store. dario#808.
+ *
+ * The divergence #805 fixed runs one way (credentials.json stale, login.json
+ * fresh) but left the two files diverged: the pool's refresh loop advances
+ * accounts/login.json while nothing ever writes credentials.json, so the
+ * legacy file stays frozen at the last `dario login`. Consequences:
+ *   - `dario doctor` reads credentials.json for its OAuth row and prints
+ *     'expired'/'expiring' in pool-of-1 mode even when the live pool token is
+ *     fresh and the fleet is 200-healthy — an alarm-inducing false positive.
+ *   - any other reader of credentials.json (a co-resident Claude Code, an ops
+ *     script) sees a stale token indefinitely.
+ *
+ * Fix: whenever the pool refreshes the `login` account, mirror the new token
+ * into credentials.json so the legacy file tracks the pool store. Only the
+ * `login` alias is mirrored — it's the one back-filled FROM credentials.json
+ * (ensureLoginCredentialsInPool), so it's the only account whose canonical
+ * home is that file; `work`/`personal` accounts have no legacy counterpart.
+ *
+ * Freshness-guarded, symmetric with #805: mirror only when the refreshed login
+ * token is strictly NEWER than the current credentials.json (by `expiresAt`).
+ * A newer-or-equal credentials.json means another process (e.g. a concurrent
+ * `dario login --force-reauth`) just wrote a fresher family — never clobber it;
+ * resyncLoginFromCredentialsIfStale pulls that direction on next startup.
+ *
+ * Best-effort: a mirror failure must never fail the refresh that produced the
+ * live token. Returns one of:
+ *   - 'skip-not-login' : alias isn't the reserved `login` — nothing to mirror
+ *   - 'mirrored'       : credentials.json updated to the pool token
+ *   - 'creds-newer'    : credentials.json is newer-or-equal — left untouched
+ */
+export declare function mirrorLoginToCredentials(refreshed: AccountCredentials): Promise<'skip-not-login' | 'mirrored' | 'creds-newer'>;

package/dist/accounts.js

@@ -23,7 +23,7 @@ import { homedir } from 'node:os';
 import { randomUUID, randomBytes, createHash } from 'node:crypto';
 import { createServer } from 'node:http';
 import { detectCCOAuthConfig } from './cc-oauth-detect.js';
-import { loadCredentials, buildManualAuthorizeUrl, parseManualPaste, readLineFromStdin, enumerateKeychainCredentials } from './oauth.js';
+import { loadCredentials, saveCredentialsTokens, buildManualAuthorizeUrl, parseManualPaste, readLineFromStdin, enumerateKeychainCredentials } from './oauth.js';
 import { openBrowser } from './open-browser.js';
 import { redactSecrets } from './redact.js';
 import { durableWriteFile } from './durable-write.js';
@@ -619,3 +619,53 @@ export async function resyncLoginFromCredentialsIfStale() {
     });
     return 'resynced';
 }
+/**
+ * Mirror the pool's freshly-refreshed `login` account token back into the
+ * legacy `~/.dario/credentials.json` store. dario#808.
+ *
+ * The divergence #805 fixed runs one way (credentials.json stale, login.json
+ * fresh) but left the two files diverged: the pool's refresh loop advances
+ * accounts/login.json while nothing ever writes credentials.json, so the
+ * legacy file stays frozen at the last `dario login`. Consequences:
+ *   - `dario doctor` reads credentials.json for its OAuth row and prints
+ *     'expired'/'expiring' in pool-of-1 mode even when the live pool token is
+ *     fresh and the fleet is 200-healthy — an alarm-inducing false positive.
+ *   - any other reader of credentials.json (a co-resident Claude Code, an ops
+ *     script) sees a stale token indefinitely.
+ *
+ * Fix: whenever the pool refreshes the `login` account, mirror the new token
+ * into credentials.json so the legacy file tracks the pool store. Only the
+ * `login` alias is mirrored — it's the one back-filled FROM credentials.json
+ * (ensureLoginCredentialsInPool), so it's the only account whose canonical
+ * home is that file; `work`/`personal` accounts have no legacy counterpart.
+ *
+ * Freshness-guarded, symmetric with #805: mirror only when the refreshed login
+ * token is strictly NEWER than the current credentials.json (by `expiresAt`).
+ * A newer-or-equal credentials.json means another process (e.g. a concurrent
+ * `dario login --force-reauth`) just wrote a fresher family — never clobber it;
+ * resyncLoginFromCredentialsIfStale pulls that direction on next startup.
+ *
+ * Best-effort: a mirror failure must never fail the refresh that produced the
+ * live token. Returns one of:
+ *   - 'skip-not-login' : alias isn't the reserved `login` — nothing to mirror
+ *   - 'mirrored'       : credentials.json updated to the pool token
+ *   - 'creds-newer'    : credentials.json is newer-or-equal — left untouched
+ */
+export async function mirrorLoginToCredentials(refreshed) {
+    if (refreshed.alias !== MIGRATED_LOGIN_ALIAS)
+        return 'skip-not-login';
+    const creds = await loadCredentials();
+    const currentExpiry = creds?.claudeAiOauth?.expiresAt ?? 0;
+    // Only mirror a strictly-newer pool token. Equal expiry means the files
+    // already agree (or a same-second write elsewhere); newer credentials.json
+    // is another process's fresher family we must not overwrite (#805 direction).
+    if (currentExpiry >= refreshed.expiresAt)
+        return 'creds-newer';
+    await saveCredentialsTokens({
+        accessToken: refreshed.accessToken,
+        refreshToken: refreshed.refreshToken,
+        expiresAt: refreshed.expiresAt,
+        scopes: refreshed.scopes ?? creds?.claudeAiOauth?.scopes ?? [],
+    });
+    return 'mirrored';
+}

package/dist/cc-template-data.json

@@ -1,6 +1,6 @@
 {
   "_version": "2.1.214",
-  "_captured": "2026-07-14T06:32:01.705Z",
+  "_captured": "2026-07-18T14:14:16.825Z",
   "_source": "bundled",
   "_schemaVersion": 3,
   "agent_identity": "You are a Claude agent, built on Anthropic's Claude Agent SDK.",
@@ -8,7 +8,7 @@
   "tools": [
     {
       "name": "Agent",
-      "description": "Launch a new agent to handle complex, multi-step tasks. Each agent type has specific capabilities and tools available to it.\n\nAvailable agent types are listed in <system-reminder> messages in the conversation.\n\nWhen using the Agent tool, specify a subagent_type parameter to select which agent type to use. If omitted, the general-purpose agent is used.\n\n## When to use\n\nReach for this when the task matches an available agent type, when you have independent work to run in parallel, or when answering would mean reading across several files — delegate it and you keep the conclusion, not the file dumps. For a single-fact lookup where you already know the file, symbol, or value, search directly. Once you've delegated a search, don't also run it yourself — wait for the result.\n\n- The agent's final message is returned to you as the tool result; it is not shown to the user — relay what matters.\n- Use SendMessage with the agent's ID or name to continue a previously spawned agent with its context intact; a new Agent call starts fresh.\n- Each agent type's model, reasoning effort, and tools come from its definition (`.claude/agents/*.md` frontmatter or SDK `agents`).\n- `isolation: \"worktree\"` gives the agent its own git worktree (auto-cleaned if unchanged).\n- Subagents run in the background by default; you'll be notified when one completes. Pass `run_in_background: false` for a synchronous run when you need the result before continuing.",
+      "description": "Launch a new agent to handle complex, multi-step tasks. Each agent type has specific capabilities and tools available to it.\n\nAvailable agent types are listed in <system-reminder> messages in the conversation.\n\nWhen using the Agent tool, specify a subagent_type parameter to select which agent type to use. If omitted, the general-purpose agent is used.\n\n## When to use\n\nReach for this when the task matches an available agent type, when you have independent work to run in parallel, or when answering would mean reading across several files — delegate it and you keep the conclusion, not the file dumps. For a single-fact lookup where you already know the file, symbol, or value, search directly. Once you've delegated a search, don't also run it yourself — wait for the result.\n\n- The agent's final report is not shown to the user — relay what matters.\n- Use SendMessage with the agent's ID or name to continue a previously spawned agent with its context intact; a new Agent call starts fresh.\n- Each agent type's model, reasoning effort, and tools come from its definition (`.claude/agents/*.md` frontmatter or SDK `agents`).\n- `isolation: \"worktree\"` gives the agent its own git worktree (auto-cleaned if unchanged).\n- Subagents run in the background by default; you'll be notified when one completes. Pass `run_in_background: false` for a synchronous run when you need the result before continuing. Never fabricate or predict a pending agent's results — the notification is never something you write yourself; if the user asks before it arrives, say it's still running.",
       "input_schema": {
         "$schema": "https://json-schema.org/draft/2020-12/schema",
         "type": "object",
@@ -939,6 +939,11 @@
                   "description": "One-sentence statement of the defect",
                   "type": "string"
                 },
+                "short_summary": {
+                  "description": "Compressed label for compact UI (≤60 chars): the claim alone, no rationale or consequence clause",
+                  "type": "string",
+                  "maxLength": 60
+                },
                 "failure_scenario": {
                   "description": "Concrete inputs/state → wrong output/crash",
                   "type": "string"
@@ -1038,7 +1043,7 @@
     },
     {
       "name": "Skill",
-      "description": "Execute a skill within the main conversation\n\nWhen users ask you to perform tasks, check if any of the available skills match. Skills provide specialized capabilities and domain knowledge.\n\nWhen users reference a \"slash command\" or \"/<something>\", they are referring to a skill. Use this tool to invoke it.\n\nHow to invoke:\n- Set `skill` to the exact name of an available skill (no leading slash). For plugin-namespaced skills use the fully qualified `plugin:skill` form.\n- Set `args` to pass optional arguments.\n- Some skills are scoped to a directory: their name is prefixed with the directory (e.g. `apps/web:deploy`) and their description says which directory they apply to. When a skill name has both a scoped and an unscoped variant, pick by the files you are working on: if the files are under a variant's directory, invoke that variant (most specific directory wins); otherwise invoke the unscoped one.\n\nImportant:\n- Available skills are listed in system-reminder messages in the conversation\n- Only invoke a skill that appears in that list, or one the user explicitly typed as `/<name>` in their message. Never guess or invent a skill name from training data; otherwise do not call this tool\n- When a skill matches the user's request, this is a BLOCKING REQUIREMENT: invoke the relevant Skill tool BEFORE generating any other response about the task\n- NEVER mention a skill without actually calling this tool\n- Do not invoke a skill that is already running\n- Do not use this tool for built-in CLI commands (like /help, /clear, etc.)\n- If you see a <command-name> tag in the current conversation turn, the skill has ALREADY been loaded - follow the instructions directly instead of calling this tool again\n",
+      "description": "Invoke a skill.\n\nA skill is a packaged set of instructions the user or project has set up for a particular kind of task (deploy steps, a review checklist, a repo-specific workflow). Available skills appear in a system-reminder listing with one-line descriptions. When the task at hand is one a listed skill covers, call this tool first — the skill's instructions load into the turn for you to follow in place of your default approach; some skills instead run in a subagent and return the finished result. Users may also ask for one by name (`/<name>`, or \"slash command\"); that's a request to invoke it.\n\n- `skill`: exact name from the listing, no leading slash. Plugin skills use `plugin:skill`. Directory-scoped skills are listed with a path prefix (`apps/web:deploy`); when both scoped and unscoped variants of a name exist, pick the one whose directory contains the files you're working on (most specific wins; unscoped otherwise).\n- `args`: optional arguments to pass through.\n\nOnly names from the listing (or that the user typed explicitly) are valid. Built-in CLI commands (`/help`, `/clear`, …) aren't skills. If a `<command-name>` block is already present this turn, the skill is loaded — follow it directly rather than calling again.\n",
       "input_schema": {
         "$schema": "https://json-schema.org/draft/2020-12/schema",
         "type": "object",

package/dist/cli.js

@@ -1287,13 +1287,15 @@ async function help() {
                              intact even when a text-tool client is
                              detected; use --preserve-tools per session
                              when edits are needed. (dario#40)
-    --strict-tls             Refuse to start proxy mode if this process
-                             isn't running under Bun. Bun is what Claude
-                             Code uses; matching its TLS stack keeps the
+    --strict-tls             Refuse to start proxy mode unless this process
+                             runs under Bun at a version whose JA3 is verified
+                             to match Claude Code (≥ v1.3.14). Bun is what
+                             Claude Code uses; matching its TLS stack keeps the
                              proxy's JA3/JA4 ClientHello indistinguishable
-                             from a stock CC request. Install Bun
-                             (https://bun.sh) so dario auto-relaunches
-                             under it. (v3.23)
+                             from a stock CC request — but an older Bun ships an
+                             older BoringSSL whose ClientHello diverges (#813).
+                             Install/upgrade Bun (https://bun.sh) so dario
+                             auto-relaunches under it. (v3.23)
     --stealth                Single-flag behavioral-stealth preset.
                              Flips pace-jitter, think-time, and
                              session-start defaults from 0 to non-zero

package/dist/live-fingerprint.d.ts

@@ -282,7 +282,7 @@ export declare function _resetInstalledVersionProbeForTest(): void;
  */
 export declare const SUPPORTED_CC_RANGE: {
     readonly min: "1.0.0";
-    readonly maxTested: "2.1.214";
+    readonly maxTested: "2.1.215";
 };
 /**
  * Compare two dotted-numeric version strings. Returns negative if `a<b`,

package/dist/live-fingerprint.js

@@ -806,7 +806,7 @@ export function _resetInstalledVersionProbeForTest() {
  */
 export const SUPPORTED_CC_RANGE = {
     min: '1.0.0',
-    maxTested: '2.1.214',
+    maxTested: '2.1.215',
 };
 /**
  * Compare two dotted-numeric version strings. Returns negative if `a<b`,

package/dist/oauth.d.ts

@@ -73,6 +73,15 @@ export declare function loadCredentials(): Promise<CredentialsFile | null>;
  * tiebreaker preference. Exported for direct testing.
  */
 export declare function pickFreshestCredentials(candidates: CredentialsFile[]): CredentialsFile | null;
+/**
+ * Mirror a set of OAuth tokens into the legacy `~/.dario/credentials.json`
+ * store. Thin durable-write wrapper over `saveCredentials` for callers outside
+ * this module — specifically the pool's login-account mirror (dario#808), which
+ * keeps credentials.json tracking the pool store after a background/startup
+ * refresh advanced `accounts/login.json`. Shares saveCredentials' durability
+ * (fsync temp + dir, #790), cache invalidation, and refresh-dead-flag clear.
+ */
+export declare function saveCredentialsTokens(tokens: OAuthTokens): Promise<void>;
 /**
  * Automatic OAuth flow using a local callback server (same as Claude Code).
  * Opens browser, captures the authorization code automatically.

package/dist/oauth.js

@@ -424,6 +424,17 @@ async function saveCredentials(creds) {
     credentialsCache = creds;
     credentialsCacheTime = Date.now();
 }
+/**
+ * Mirror a set of OAuth tokens into the legacy `~/.dario/credentials.json`
+ * store. Thin durable-write wrapper over `saveCredentials` for callers outside
+ * this module — specifically the pool's login-account mirror (dario#808), which
+ * keeps credentials.json tracking the pool store after a background/startup
+ * refresh advanced `accounts/login.json`. Shares saveCredentials' durability
+ * (fsync temp + dir, #790), cache invalidation, and refresh-dead-flag clear.
+ */
+export async function saveCredentialsTokens(tokens) {
+    await saveCredentials({ claudeAiOauth: tokens });
+}
 /**
  * Automatic OAuth flow using a local callback server (same as Claude Code).
  * Opens browser, captures the authorization code automatically.

package/dist/proxy.js

@@ -16,7 +16,7 @@ import { AccountPool, computeStickyKey, parseRateLimits, modelFamily, isInAuthCo
 import { Analytics, billingBucketFromClaim, formatUsageLogLine, SUBSCRIPTION_CLAIMS } from './analytics.js';
 import { OverageGuard, buildHaltErrorBody } from './overage-guard.js';
 import { notify as osNotify } from './notify.js';
-import { loadAllAccounts, loadAccount, saveAccount, refreshAccountToken, resyncLoginFromCredentialsIfStale, ensureLoginCredentialsInPool } from './accounts.js';
+import { loadAllAccounts, loadAccount, saveAccount, refreshAccountToken, resyncLoginFromCredentialsIfStale, ensureLoginCredentialsInPool, mirrorLoginToCredentials } from './accounts.js';
 import { handleAdminRequest } from './admin-api.js';
 import { createTokenBucket } from './rate-limit.js';
 import { getOpenAIBackend, isOpenAIModel, forwardToOpenAI } from './openai-backend.js';
@@ -1233,6 +1233,11 @@ export async function startProxy(opts = {}) {
                         return;
                     const refreshed = await refreshAccountToken(saved);
                     pool.updateTokens(acc.alias, refreshed.accessToken, refreshed.refreshToken, refreshed.expiresAt);
+                    // Mirror a refreshed `login` token back to credentials.json so the
+                    // legacy file (and `dario doctor`) tracks the pool store (#808).
+                    await mirrorLoginToCredentials(refreshed).catch((err) => {
+                        console.error(`[dario] login→credentials.json mirror failed (startup) for ${acc.alias}: ${err instanceof Error ? err.message : err}`);
+                    });
                     console.error(`[dario] Startup refresh recovered account ${acc.alias} (was expired/expiring).`);
                 }
                 catch (err) {
@@ -1253,6 +1258,11 @@ export async function startProxy(opts = {}) {
                         continue;
                     const refreshed = await refreshAccountToken(saved);
                     pool.updateTokens(acc.alias, refreshed.accessToken, refreshed.refreshToken, refreshed.expiresAt);
+                    // Mirror a refreshed `login` token back to credentials.json so the
+                    // legacy file (and `dario doctor`) tracks the pool store (#808).
+                    await mirrorLoginToCredentials(refreshed).catch((err) => {
+                        console.error(`[dario] login→credentials.json mirror failed (background) for ${acc.alias}: ${err instanceof Error ? err.message : err}`);
+                    });
                 }
                 catch (err) {
                     console.error(`[dario] Background refresh failed for ${acc.alias}: ${err instanceof Error ? err.message : err}`);
@@ -1628,6 +1638,19 @@ export async function startProxy(opts = {}) {
         }
         // Strip query parameters for endpoint matching
         const urlPath = req.url?.split('?')[0] ?? '';
+        // Liveness probe — always 200 while the HTTP server is accepting requests,
+        // deliberately decoupled from OAuth state. Docker's healthcheck (and the
+        // autoheal watchdog that keys on it) points HERE, not /health: a broken or
+        // expired refresh token makes /health return 503, but a container restart
+        // cannot mint a new token, so restarting on that is a pointless loop (one
+        // shared-refresh-family outage thrashed dario for 4h+ this way). Readiness —
+        // the 503-on-broken-OAuth verdict that uptime monitors and
+        // `depends_on: service_healthy` need — stays on /health.
+        if (urlPath === '/livez') {
+            res.writeHead(200, JSON_HEADERS);
+            res.end(JSON.stringify({ status: 'ok' }));
+            return;
+        }
         // Health check
         //
         // Returns HTTP 503 when OAuth is in a state that will cause every upstream

package/dist/runtime-fingerprint.d.ts

@@ -25,8 +25,16 @@
  */
 /** Canonical buckets the caller pivots on. */
 export type RuntimeFingerprintStatus = 
-/** Running under Bun — TLS stack matches CC. */
+/** Running under Bun ≥ the JA3-verified floor — TLS ClientHello matches CC. */
 'bun-match'
+/**
+ * Running under Bun, but at a version below the JA3-verified floor: being on
+ * Bun is necessary but not sufficient. Older Bun ships an older BoringSSL
+ * whose ClientHello is not confirmed to match CC's (measured divergent on
+ * Bun 1.0.9 — see #813). Treated as a warn so an old Bun on PATH can't
+ * report a false-green match while emitting a divergent JA3.
+ */
+ | 'bun-ja3-unverified'
 /** Running under Node, Bun available on PATH but auto-relaunch was bypassed. */
  | 'bun-bypassed'
 /** Running under Node, Bun not installed. */
@@ -54,6 +62,24 @@ export interface RuntimeFingerprint {
  * the (~sub-100ms) cost when Bun is installed.
  */
 export declare function probeBunVersion(): string | undefined;
+/**
+ * Lowest public Bun version whose TLS ClientHello (JA3) is *measured* to match
+ * the Bun/BoringSSL fingerprint Claude Code presents on the wire. Empirical
+ * basis (#813, macOS arm64): CC 2.1.214 embeds the Bun canary line and hashes
+ * to JA3 `e97f5146a7009cc2918b50e903b6ff8d`; bare public Bun 1.3.14 and canary
+ * reproduce it byte-for-byte, while Bun 1.0.9 diverges (adds 3DES, ECH,
+ * padding → `2ae7eb4b…`). The window between 1.0.9 and 1.3.14 is unmeasured,
+ * so anything below this floor is reported unverified rather than a green match.
+ */
+export declare const JA3_VERIFIED_BUN_FLOOR = "1.3.14";
+/**
+ * True when Bun `version` is at or above `floor`. Parses the leading
+ * `major.minor.patch` and ignores any pre-release/`-canary…` suffix, so Bun's
+ * canary tags (e.g. `1.4.0-canary.x`) compare as their base triple. Returns
+ * `undefined` when either string can't be parsed — the caller decides how to
+ * treat "can't tell" (we keep those as a best-effort match rather than warn).
+ */
+export declare function bunVersionMeetsJa3Floor(version: string, floor?: string): boolean | undefined;
 /**
  * Synthesize the TLS-fingerprint status from three inputs. All three are
  * passed explicitly so tests can cover every combination without touching

package/dist/runtime-fingerprint.js

@@ -51,6 +51,38 @@ export function probeBunVersion() {
         return undefined;
     }
 }
+/**
+ * Lowest public Bun version whose TLS ClientHello (JA3) is *measured* to match
+ * the Bun/BoringSSL fingerprint Claude Code presents on the wire. Empirical
+ * basis (#813, macOS arm64): CC 2.1.214 embeds the Bun canary line and hashes
+ * to JA3 `e97f5146a7009cc2918b50e903b6ff8d`; bare public Bun 1.3.14 and canary
+ * reproduce it byte-for-byte, while Bun 1.0.9 diverges (adds 3DES, ECH,
+ * padding → `2ae7eb4b…`). The window between 1.0.9 and 1.3.14 is unmeasured,
+ * so anything below this floor is reported unverified rather than a green match.
+ */
+export const JA3_VERIFIED_BUN_FLOOR = '1.3.14';
+/**
+ * True when Bun `version` is at or above `floor`. Parses the leading
+ * `major.minor.patch` and ignores any pre-release/`-canary…` suffix, so Bun's
+ * canary tags (e.g. `1.4.0-canary.x`) compare as their base triple. Returns
+ * `undefined` when either string can't be parsed — the caller decides how to
+ * treat "can't tell" (we keep those as a best-effort match rather than warn).
+ */
+export function bunVersionMeetsJa3Floor(version, floor = JA3_VERIFIED_BUN_FLOOR) {
+    const parse = (v) => {
+        const m = /^(\d+)\.(\d+)\.(\d+)/.exec(v.trim());
+        return m ? [Number(m[1]), Number(m[2]), Number(m[3])] : undefined;
+    };
+    const a = parse(version);
+    const b = parse(floor);
+    if (!a || !b)
+        return undefined;
+    for (let i = 0; i < 3; i++) {
+        if (a[i] !== b[i])
+            return a[i] > b[i];
+    }
+    return true; // equal versions meet the floor
+}
 /**
  * Synthesize the TLS-fingerprint status from three inputs. All three are
  * passed explicitly so tests can cover every combination without touching
@@ -65,6 +97,21 @@ export function classifyRuntimeFingerprint(runningUnderBun, availableBunVersion,
         // is readable; we don't require a separate probe. The caller passes the
         // resolved version string as `availableBunVersion` in the bun case.
         const bunVer = availableBunVersion ?? 'unknown';
+        // Being on Bun is necessary but NOT sufficient: only Bun ≥ the JA3-verified
+        // floor is measured to reproduce CC's ClientHello (#813). A readable version
+        // below the floor is the false-green case — dario auto-relaunches into an
+        // old Bun on PATH and would otherwise report a match while emitting a
+        // divergent JA3. An unreadable version (rare; Bun almost always exposes
+        // .version) has nothing to check, so we leave it as a best-effort match.
+        if (bunVer !== 'unknown' && bunVersionMeetsJa3Floor(bunVer) === false) {
+            return {
+                status: 'bun-ja3-unverified',
+                runtime: 'bun',
+                runtimeVersion: bunVer,
+                detail: `Bun v${bunVer} — under Bun, but its TLS ClientHello (JA3) is not verified to match Claude Code (known-good ≥ v${JA3_VERIFIED_BUN_FLOOR})`,
+                hint: `Upgrade Bun to ≥ v${JA3_VERIFIED_BUN_FLOOR} (https://bun.sh); older Bun ships an older BoringSSL whose ClientHello diverges from Claude Code's.`,
+            };
+        }
         return {
             status: 'bun-match',
             runtime: 'bun',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@askalf/dario",
-  "version": "5.2.10",
+  "version": "5.2.12",
   "description": "Use your Claude Pro/Max subscription in any tool — Cursor, Cline, Aider, the Agent SDK, your scripts — at subscription pricing, not per-token API bills. One local Anthropic + OpenAI-compatible endpoint.",
   "type": "module",
   "bin": {