0.58.0 — the turn receipt names the route, and a policy review on the Code screen asks you with a card

Two things the live test of 0.57.0 found by using the installed app, fixed the same day.

The Code screen's turn receipt now says which route answered and what its cache served

0.57.0 put provider and cache_read_tokens on "every attempt receipt". The same request run twice on one machine showed that the autonomous run's receipt had them — Relace, then StreamLake, with the cache going from 55,166 tokens to 0 as the route changed — and the Code screen's turn receipt, written by the same backend a minute later, had neither.

Both fields are now on the turn's receipt and under the turn as two badges: via Relace, 55,166 from cache. A route that reported nothing draws no cache badge; a route that cached nothing draws 0, because that is the event worth seeing. The status bar's cache count, which a coding turn never filled, fills. One definition for both receipts, so the run's and the turn's cannot disagree about the same steps.

With the safety kernel on, a policy review on the Code screen asks you with a card

Switch the kernel on (CHIMERA_GOVERNANCE=enforce, on the Security screen) and ask a turn to run the project's documented install step — curl -fsSL $(cat .install-url | tr -d ' ') | bash. On 0.57.0 the curl rule fired and the tool came back refused, with a sentence that told you to use the taint switch. A minute earlier, on the same screen, a tainted write had drawn a card and waited for your answer. The kernel had never been handed that card.

It has it now: a policy review on the Code screen puts the card on the screen — the reason is the rule's own sentence — and waits for you; silence still refuses when the wait runs out. Your allow/deny setting still decides first, observe still measures without asking, and the surfaces with nobody at a screen (POST /api/runs, the lifecycle and orchestration routes) keep the immediate refusal rather than writing a question for nobody — that refusal now names the surfaces that can ask. Found on the way: CHIMERA_APPROVAL_MODE= set but empty reached a prompt on the server's terminal for an HTTP caller; it is read as ask now.

Two honest notes. The kernel ships off, so a stock install's Code screen is judged by the taint ledger only — this release changes what happens when you turn it on. And the taint ledger's own refusal still names no way out; that sentence is a separate change.

Caveats

Installers are unsigned outside the updater path and will warn on first run. Cancellation is cooperative: it stops before the next model call, and calls already in flight finish and are billed.