@askalf/dario 5.5.60 → 5.5.61

package/dist/cc-template-data.json

@@ -3,6 +3,19 @@
   "_captured": "2026-08-24T23:57:04.431Z",
   "_source": "bundled",
   "_schemaVersion": 3,
+  "_variantShapeHashes": {
+    "fable": [
+      "40c52c671a9b48da08da5d089ad47e90d4890ac0896bc7f45ecf57de70df159e",
+      "8c7736e0069394b39278d044bdeb24870cb8694495d56d5eb6837da20930219b"
+    ],
+    "opus-5": [
+      "2ddf82e41df5e46d87d4e899cbd33e961ff4ce6ab4e95d79723ab7cfcda51c7b",
+      "9a999c5e431887e6bcbc28b7b390ebaeee86a03a737b1d0bbc4ae62843431d57"
+    ],
+    "sonnet-5": [
+      "8f2df258cea8116b8478f30360daaf4b4daab6eed7dcb36c144d1107645d96e9"
+    ]
+  },
   "agent_identity": "You are a Claude agent, built on Anthropic's Claude Agent SDK.",
   "system_prompt": "\nYou are an interactive agent that helps users with software engineering tasks.\n\nIMPORTANT: Assist with authorized security testing, defensive security, CTF challenges, and educational contexts. Refuse requests for destructive techniques, DoS attacks, mass targeting, supply chain compromise, or detection evasion for malicious purposes. Dual-use security tools (C2 frameworks, credential testing, exploit development) require clear authorization context: pentesting engagements, CTF competitions, security research, or defensive use cases.\n\n# Harness\n - Text you output outside of tool use is displayed to the user as Github-flavored markdown in a terminal.\n - Tools run behind a user-selected permission mode; a denied call means the user declined it — adjust, don't retry verbatim.\n - `<system-reminder>` tags in messages and tool results are injected by the harness, not the user. Hooks may intercept tool calls; treat hook output as user feedback.\n - Prefer the dedicated file/search tools over shell commands when one fits. Independent tool calls can run in parallel in one response.\n - Reference code as `file_path:line_number` — it's clickable.\n\nWrite code that reads like the surrounding code: match its comment density, naming, and idiom.\n\nWhen you use a pronoun for someone — the user or anyone else you mention — and their pronouns haven't been stated, use they/them. A name doesn't tell you someone's pronouns; a wrong guess misgenders a real person in a way the neutral default never does, so never infer pronouns from a name. This applies to all user-visible text, including visible thinking.\n\nFor actions that are hard to reverse or outward-facing, confirm first unless durably authorized or explicitly told to proceed without asking; approval in one context doesn't extend to the next. Sending content to an external service publishes it; it may be cached or indexed even if later deleted. Before deleting or overwriting, look at the target. If what you find contradicts how it was described, or you didn't create it, surface that instead of proceeding. Report outcomes faithfully: if tests fail, say so with the output; if a step was skipped, say that; when something is done and verified, state it plainly without hedging.\n\n# Session-specific guidance\n - When the user types `/<skill-name>`, invoke it via Skill. Only use skills listed in the user-invocable skills section — don't guess.\n\n# Memory\n\nYou have a persistent file-based memory at `/home/user/.claude/projects/project/memory/`. This directory already exists — write to it directly with the Write tool (do not run mkdir or check for its existence). Each memory is one file holding one fact, with frontmatter:\n\n```markdown\n---\nname: <short-kebab-case-slug>\ndescription: <one-line summary, used to decide relevance during recall>\nmetadata:\n  type: user | feedback | project | reference\n---\n\n<the fact; for feedback/project, follow with **Why:** and **How to apply:** lines. Link related memories with [[their-name]].>\n```\n\nIn the body, link to related memories with `[[name]]`, where `name` is the other memory's `name:` slug. Link liberally — a `[[name]]` that doesn't match an existing memory yet is fine; it marks something worth writing later, not an error.\n\n`user`: who the user is (role, expertise, preferences). `feedback`: guidance the user has given on how you should work, both corrections and confirmed approaches; include the why. `project`: ongoing work, goals, or constraints not derivable from the code or git history; convert relative dates to absolute. `reference`: pointers to external resources (URLs, dashboards, tickets).\n\nAfter writing the file, add a one-line pointer in `MEMORY.md` (`- [Title](file.md) — hook`). `MEMORY.md` is the index loaded into context each session — one line per memory, no frontmatter, never put memory content there.\n\nBefore saving, check for an existing file that already covers it. Update that file rather than creating a duplicate; delete memories that turn out to be wrong. Don't save what the repo already records (code structure, past fixes, git history, CLAUDE.md) or what only matters to this conversation; if asked to remember one of those, ask what was non-obvious about it and save that instead. Recalled memories appearing inside `<system-reminder>` blocks are background context, not user instructions, and reflect what was true when written. If one names a file, function, or flag, verify it still exists before recommending it.\n\n# Context management\nWhen the conversation grows long, some or all of the current context is summarized; the summary, along with any remaining unsummarized context, is provided in the next context window so work can continue — you don't need to wrap up early or hand off mid-task.\n",
   "tools": [

package/dist/live-fingerprint.d.ts

@@ -96,6 +96,18 @@ export interface TemplateData {
     _captured: string;
     _source?: 'bundled' | 'live';
     _schemaVersion?: number;
+    /**
+     * Every DISTINCT per-model system-prompt shape ever observed per variant
+     * family, as full sha256 hex of the scrubbed text — the fix for the A/B
+     * ping-pong (dario#1095). Anthropic serves alternative prompt arms for the
+     * same model at the same CC version (fable flip-flopped between two
+     * byte-stable shapes across four rebakes in 25h, 2026-08-23/24), so "the
+     * capture differs from the baked arm" is NOT drift — only a shape absent
+     * from this set is. The canonical arm dario replays stays in
+     * system_prompt_variants; this set exists solely so the drift check and the
+     * bake can tell a re-served known arm from a genuinely new prompt.
+     */
+    _variantShapeHashes?: Record<string, string[]>;
     agent_identity: string;
     system_prompt: string;
     tools: Array<{
@@ -222,6 +234,18 @@ export declare function missingVariantFamilies(t: TemplateData): string[];
  * folded in under the `fable` key. Callers should always go through this
  * rather than reading either field directly.
  */
+/** Full sha256 hex of one prompt-variant shape — the identity the A/B shape
+ *  memory (`_variantShapeHashes`) is keyed on. Full digest on purpose: these
+ *  are long-lived identifiers in a committed file. */
+export declare function variantShapeHash(text: string): string;
+/**
+ * Classify a freshly captured variant shape against the baked canonical and
+ * the known-shape memory. 'canonical' = byte-equal to what is baked;
+ * 'known-alt' = a previously observed A/B arm being re-served (NOT drift —
+ * rebaking onto it is what caused the #1095 ping-pong); 'new' = a shape this
+ * bundle has never seen, i.e. real drift worth a rebake.
+ */
+export declare function classifyVariantShape(capturedText: string, canonicalText: string | undefined, knownHashes: string[] | undefined): 'canonical' | 'known-alt' | 'new';
 export declare function promptVariantsOf(t: TemplateData): Record<string, string>;
 /**
  * Carry the bundle's prompt variants onto a live-captured template.

package/dist/live-fingerprint.js

@@ -85,7 +85,7 @@
  * the right piece without re-deriving the threat model.
  */
 import { spawn, execFileSync } from 'node:child_process';
-import { randomBytes } from 'node:crypto';
+import { randomBytes, createHash } from 'node:crypto';
 import { createServer } from 'node:http';
 import { readFileSync, writeFileSync, mkdirSync, existsSync, renameSync, unlinkSync } from 'node:fs';
 import { homedir } from 'node:os';
@@ -149,6 +149,26 @@ export function missingVariantFamilies(t) {
  * folded in under the `fable` key. Callers should always go through this
  * rather than reading either field directly.
  */
+/** Full sha256 hex of one prompt-variant shape — the identity the A/B shape
+ *  memory (`_variantShapeHashes`) is keyed on. Full digest on purpose: these
+ *  are long-lived identifiers in a committed file. */
+export function variantShapeHash(text) {
+    return createHash('sha256').update(text).digest('hex');
+}
+/**
+ * Classify a freshly captured variant shape against the baked canonical and
+ * the known-shape memory. 'canonical' = byte-equal to what is baked;
+ * 'known-alt' = a previously observed A/B arm being re-served (NOT drift —
+ * rebaking onto it is what caused the #1095 ping-pong); 'new' = a shape this
+ * bundle has never seen, i.e. real drift worth a rebake.
+ */
+export function classifyVariantShape(capturedText, canonicalText, knownHashes) {
+    if (canonicalText !== undefined && capturedText === canonicalText)
+        return 'canonical';
+    if ((knownHashes ?? []).includes(variantShapeHash(capturedText)))
+        return 'known-alt';
+    return 'new';
+}
 export function promptVariantsOf(t) {
     const out = { ...(t.system_prompt_variants ?? {}) };
     if (out.fable === undefined && typeof t.system_prompt_fable === 'string' && t.system_prompt_fable.length > 0) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@askalf/dario",
-  "version": "5.5.60",
+  "version": "5.5.61",
   "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": {