indifferentketchup/boocode
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

0 Releases 92 Tags

RSS Feed
  • v1.13.6-prefix-stability a0c8d212cb
    Compare

    v1.13.8: system-prompt prefix stability verify-and-measure

    indifferentketchup released this 2026-05-22 13:42:18 +00:00 | 98 commits to main since this release

    Recon during planning disproved the original v1.13.7 (DB-cache) premise:
    buildSystemPrompt already runs over inputs mtime-cached at the file layer
    (BOOCHAT.md in system-prompt.ts:25, AGENTS.md global+per-project in
    agents.ts:245), and DB scalars are byte-stable until edited. The output
    is microsecond pure-string concat with no I/O. Skills aren't in the
    prefix; tools live in a separate request body field alpha-sorted by
    v1.13.3.

    This batch closes the verification gap with instrumentation, not
    implementation:

    • system-prompt.ts: buildSystemPromptWithFingerprint canonical impl
      computes SHA-256 over the assembled prefix, runs a per-session
      Map<sessionId, lastHash> observer, emits PrefixFingerprint per call
      and PrefixDrift (with field-level changed_inputs) on hash change.
      buildSystemPrompt is now a thin shim returning .prompt.
    • agents.ts: getAgentsMtimes accessor — cache-read only, no I/O.
    • payload.ts: buildMessagesPayload takes optional log argument; when
      passed, emits prefix-fingerprint (info) + prefix-drift (warn).
    • turn.ts + sentinel-summaries.ts: pass ctx.log at 3 production call
      sites; sentinel summaries log too so any drift across cap-hit /
      doom-loop paths surfaces.
    • system-prompt.test.ts: 4 new tests (byte-identical, no-drift-on-
      stable, drift-fires-with-changed-inputs, cross-session-no-drift).

    194/194 tests pass (was 190).

    Smoke: 5 messages in a fresh session produced 7 prefix-fingerprint
    logs (extras from buildMessagesPayload being called from sentinel
    summary paths), all with identical prefix_hash and prefix_length=2907,
    zero prefix-drift. Prefix is byte-stable in steady-state.

    Decision: original system_prompt_cache DB table from the roadmap is
    permanently dropped. The v1.12.0 mtime caches at the input layer plus
    alpha tool ordering at the request body (v1.13.3) already address the
    load-bearing cache-stability surfaces. Instrumentation stays so the
    claim can be re-verified at any time.

    Downloads