v5.2.0

What's Changed

• fix: the detectors and the server's error log fail closed when a pattern cannot finish by @c-1k in #425
• ci(release): the bump the CHANGELOG requires, a byte-identical rebuild, and npm trusted publishing's floor by @c-1k in #426
• feat(server): health and budget report ledger reachability by @c-1k in #428
• fix(server): the first health probe's deadline counts from its send, not from the child's spawn by @c-1k in #430
• test: linearity rows bound the ratio of two reads, not a time in milliseconds by @c-1k in #429
• fix(core): reclaim an audit writer lock left in another PID namespace once its lease expires by @c-1k in #431
• feat(ui): the usertrust logo and gold in the dashboard header, and a gold/orange/red budget bar by @c-1k in #434
• fix(server): a credential runs on past the caller's key only where the key holds what ended it by @c-1k in #435
• fix(core,ui): publish the enforced budget at startup so an upgraded vault never reads BUDGET UNKNOWN by @c-1k in #432
• release: cut the 5.2.0 CHANGELOG by @c-1k in #439
• test: give three load-sensitive rows an explicit budget sized from measurement by @c-1k in #441
• test: the detectors' linearity rows bound the ratio of two reads, in a CI job of their own by @c-1k in #443
• fix(audit): a writer released and then appended to gives the lock back by @c-1k in #446
• fix: a symlinked node_modules is ignored like a directory by @c-1k in #445
• feat(core,server,claude-code-plugin): a hold can be asked to outlive a long tool call by @c-1k in #448
• fix(claude-code-plugin): a hold past its life is never settled by @c-1k in #444
• fix(pii): redact rewrites only model content; control fields are sent as written by @c-1k in #447
• docs: an integrity claims register, and the documentation no longer says more than verification checks by @c-1k in #452
• test(scan-linear): compare at eight times the input with a bound of 32, so a V8 per-character step cannot fail a linear scan by @c-1k in #453
• test(claims): the integrity vocabulary catches the synonyms an overclaim takes by @c-1k in #455
• test(plugin): a slow answer the hook gave up on never fires into the next row by @c-1k in #457
• fix(claude-code): a hold names the session's own model, never a configured or built-in default by @c-1k in #437
• test(plugin): no test runs as the host's configured session, whatever the host exports by @c-1k in #456
• fix(plugin): a fresh hold too short for its own settle is given back, never settled by @c-1k in #459
• test: a new wall-clock threshold in a test states its headroom, with a ratchet on the ones already there by @c-1k in #454
• test(plugin): state the headroom of the isolate-env suite-run timeout by @c-1k in #464
• test(server): rows that assert how a child's exit is classified wait for the exit, not a 600 ms deadline that races it by @c-1k in #460
• ci: test what will land: candidate/** merge commits, a tested-tree stamp, and no cancelled master runs by @c-1k in #462
• ci(release): prove the npm token before anything is pushed by @c-1k in #466
• release: re-cut the 5.2.0 CHANGELOG with the entries merged since the first cut by @c-1k in #450
• deps(dev): vitest and @vitest/coverage-v8 to 4.1.12 (clears three medium advisories) by @c-1k in #458

Full Changelog: v5.1.0...v5.2.0