v0.6.1 — anchor on the fact, not a consumer of it

Claude Code 2.1.277 respelled the site where a request's thinking display is chosen: the ternary flipped its branches (!x?void 0:…) and grew a "highlights" mode inside the chosen value. live-thinking's display-mode step had anchored on that site, so it read required step display-mode found nothing on 2.1.277 and 2.1.278 while every anchor count stood, and apply dropped the patch — live thinking silently gone, every other patch landing. This release fixes those builds, and fixes the class: the step no longer anchors on a site that consumes the fact.

The fix

The step reached the display value through the CLAUDE_CODE_DISABLE_THINKING read that shared its let — comma-fusion, the minifier's — and identified it as the consequence of a ternary whose alternative was void 0 — the branch layout, upstream's. Both are syntax between the anchors, which is the one thing the playbook says never to describe.

What upstream keeps under a name of its own is the showThinkingSummaries setting: one member read, spelled settings().showThinkingSummaries??!1, on every one of the 60 builds from 2.1.210 to 2.1.278 — and the request's display, the beta header withheld while summaries are on, and the updates display the request otherwise falls back to are all routed off that one read. So the read gains a default ((settings().showThinkingSummaries??!0)) and the request is never touched. Every member read, as spinner-tips reads its setting; a write is skipped for the reason it gives; nothing is claimed about the expression around it. The step is 13 lines where it was 80, and the env-var anchor, the ?? climb and the branch test are gone.

One behaviour change falls out, in the user's favour: an explicit "showThinkingSummaries": false in your settings now wins, where the request-side default overrode it.

PLAYBOOK.md records the rule this cost, under What still takes judgement: anchor on the fact, not on a consumer of it — and where a value must be identified at its site, ask what it can be (js.values), never which branch it sits on.

Compatibility

Transparent. If Claude auto-updated you onto 2.1.277 or 2.1.278 and your thinking stopped streaming live, upgrade and re-bake (patch-cc apply --from-cache, or re-run the menu). No other patch, flag, manifest key or stored selection changes.

Validated

patch-cc doctor bakes and boots all 60 corpus builds, 2.1.210 → 2.1.278 (the set grew by nine this release: 2.1.270–2.1.278, each hash verified against upstream's own manifest). Diffed against the previous sweep, exactly two lines move: 2.1.277 and 2.1.278 go from a failing exit to green with live-thinking at cand=5 applied=5. No other build's count, note or runtime line moved. A real 2.1.278 apply lands 10/10 and boots, and an interactive turn on it carries a thinking block with text in the transcript.

uvx patch-cc            # or: uv tool install patch-cc && patch-cc