patch-cc 0.6.0__tar.gz → 0.6.1__tar.gz

{patch_cc-0.6.0 → patch_cc-0.6.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: patch-cc
-Version: 0.6.0
+Version: 0.6.1
 Summary: Interactive patcher for the Claude Code native binary
 Project-URL: Homepage, https://github.com/anfreire/patch-cc
 Project-URL: Repository, https://github.com/anfreire/patch-cc

{patch_cc-0.6.0 → patch_cc-0.6.1}/docs/PLAYBOOK.md

@@ -123,6 +123,20 @@ The tree removes the *mechanical* fragility. It does not decide these:
   the bundle one identity, the point where that path is fed, where a twin of
   the path owes one per step, each a claim only the patch needs.
   `live-thinking` is the worked case ([below](#live-thinking--streamingpy)).
+- **Anchor on the fact, not on a consumer of it.** When upstream keeps a fact
+  under a name of its own — a setting, a header, a store field — and every
+  site that acts on it sits downstream of one read, default or flip *that
+  read* and leave the sites alone: the sites are where upstream respells
+  things, the name is what it keeps. `display-mode` paid for the lesson on
+  2.1.277. It defaulted the request's thinking display at the site that chose
+  it, reached through the env-var read that shared the value's `let`
+  (comma-fusion, the minifier's) and identified as the consequence of a
+  ternary whose alternative was `void 0` (the branch layout, upstream's); the
+  build flipped the branches and grew a `"highlights"` mode inside the value,
+  and the step found nothing with every anchor standing — while the fact,
+  `showThinkingSummaries`, was one member read in one spelling on every build
+  in the corpus. Where a value *must* be identified at its site, ask what it
+  can *be* (`js.values`), never which branch it sits on.
 - **Match an identity by the weakest claim that still proves it; hold a rewrite
   to the exact node.** The two jobs pull in opposite directions.
   `thinking-inline`'s null-guard neutralises only a `return` that answers
@@ -505,8 +519,9 @@ Most patches are one rewrite. `live-thinking` is five named sub-steps, because
 a single hit count cannot tell "all landed" from "half silently drifted", and
 each records its own `candidates`/`applied`:
 
-- **`display-mode`** — the request asks the API for summarised thinking text;
-  without it the stream carries signatures and no words.
+- **`display-mode`** — the `showThinkingSummaries` setting defaults on, so the
+  request asks the API for summarised thinking text; without it the stream
+  carries signatures and no words.
 - **`reducer`** — the stream reducer is found together with the options bag it
   is handed the live tool-use setter in, and our binding of that setter is
   added to the bag.
@@ -881,15 +896,24 @@ for you. Each entry: what it changes, the stable anchor, and where it lives.
     drew beside the landed block for as long as the answer streamed. A
     tool-use entry at the same index is left exactly as the twin leaves it,
     and a list with nothing to drop is returned as it was.
-  - **`display-mode`** defaults the request's thinking display to
-    `"summarized"`; without it the API only streams summary text when the
-    `showThinkingSummaries` setting is on. Two shapes used to be spelled out —
-    the inline env check and the 2.1.216 form that hoists it behind
-    feature-helper calls. They are one edit: the display value gains a
-    default, and whatever guards reach it are untouched because they are never
-    matched. The env-var *name* is the witness; whatever reads it is never
-    described, so a hoisted `process.env` (the same migration that killed
-    `org-label` on 2.1.228) costs nothing here.
+  - **`display-mode`** defaults the `showThinkingSummaries` setting on. Upstream
+    asks the API for `"summarized"` exactly when that setting is on, and routes
+    every consequence — the request's display, the beta header it withholds
+    while summaries are on, the `updates` display the request otherwise falls
+    back to — off one read of it, so that read
+    gains a default (`(settings().showThinkingSummaries??!0)`) and the request
+    is never touched. Every member read of the name, as `spinner-tips` reads
+    its setting, and a write is skipped for the reason it gives; the read is
+    one on every build in the corpus, spelled `settings().name??!1` on all of
+    them, and none of that is claimed. An explicit `false` in the user's
+    settings still wins. Until 2.1.277 this step defaulted the request's
+    display value instead, reached through the `CLAUDE_CODE_DISABLE_THINKING`
+    read that shared its `let` and identified as the consequence of a ternary
+    whose alternative was `void 0`; that build flipped the branches
+    (`!x?void 0:…`) and grew a `"highlights"` mode inside the chosen value,
+    and the step read *found nothing* with every anchor standing. Both claims
+    were syntax between the anchors ([What still takes
+    judgement](#what-still-takes-judgement)).
 
   **What is deliberately not done.** No state of ours: upstream's store carries
   a `streamingThinking` slot with a setter and a thirty-second linger, written
@@ -936,7 +960,10 @@ for you. Each entry: what it changes, the stable anchor, and where it lives.
   slots (2.1.257 — not the compiler arriving, which had cached the
   conversation render since 2.1.247, but this component joining it). The
   reducer half, anchored on the API's event strings, has not moved since it
-  became an insertion at dispatch points. Prefer claims upstream cannot drop
+  became an insertion at dispatch points. The display default broke once
+  (2.1.277), on the branch layout of the ternary that chose the request's
+  value, and moved off the request onto the setting upstream chooses it from.
+  Prefer claims upstream cannot drop
   without paying for them — a dispatch string, a store's field name, the twin's
   own list — over claims only this patch needs, which is what CONDUCT's *ride
   what upstream ships working* asks. What was cut, and why each piece was a

{patch_cc-0.6.0 → patch_cc-0.6.1}/docs/corpus.md

@@ -90,6 +90,15 @@ never the size:
 | `2.1.267` | 217 MB | `0399c793ff571d5946ef923d80b4f330d05ac4b6842a6b0775468f5d389403c0` |
 | `2.1.268` | 219 MB | `9691a2b7bd796712ca8cffb8e32e54ff7fc45b662540233171a16a94a0425653` |
 | `2.1.269` | 220 MB | `25e44883f54419569a3d739f38cbbdaebe83b09895da0f343e1b003710a4775b` |
+| `2.1.270` | 224 MB | `3a624a5a7cd79bbad4d32bd7db36f1197ecf458bc5bf1e2aed81834a01ad3ef0` |
+| `2.1.271` | 227 MB | `5e7b6fc24d0e124f68e99a0641c47b662945c6d197d768d7ad7a72cbf1897f58` |
+| `2.1.272` | 227 MB | `d81396a668eb76fbddb49a2a5841f1b5d7af96b4c1f6500ced92f2c988f5bcd4` |
+| `2.1.273` | 229 MB | `6c752e2cc7c110c9df15f26d8d134d438c5ae95dbd610efc1a308bf7f9c5f6c1` |
+| `2.1.274` | 231 MB | `15e2d05148f801b5774032faad87e624ecd172e9903288bda448b892eb58fa07` |
+| `2.1.275` | 232 MB | `13586f3150a7ca1655f36e1dba759fb404e0f7cf7021d4a3dcd5e6f604e56156` |
+| `2.1.276` | 232 MB | `8a56c8a14bd3cb246e2bdb7e60aefe0f609bff78c8bbcc5ea6b1817c111c6145` |
+| `2.1.277` | 234 MB | `722210f05ba494d8f6df69423c4d4f2960900f7a007d0532851c7a36e375cab7` |
+| `2.1.278` | 234 MB | `5c4735937844e84f8a93306e841a5b0e12252909b07870f789b190468da147ab` |
 
 This set covers the span the playbook's tree-move measurements were taken over
 (`2.1.210` → `2.1.233`), the 2.1.242 split, the 2.1.246 stream-store

{patch_cc-0.6.0 → patch_cc-0.6.1}/src/patch_cc/__init__.py

@@ -1,3 +1,3 @@
 """patch-cc: an interactive patcher for the Claude Code native binary."""
 
-__version__ = "0.6.0"
+__version__ = "0.6.1"

{patch_cc-0.6.0 → patch_cc-0.6.1}/src/patch_cc/patches/streaming.py

@@ -21,8 +21,10 @@ memoization fashion, and each repair bought exactly one build: every one of
 those was a claim only this patch needed (the builds and the spellings are in
 docs/PLAYBOOK.md). The reducer half, anchored on the API's own event strings,
 has not moved since it became an insertion at dispatch points. Only that half
-is left, plus the one request-side default that makes the API stream summary
-text at all.
+is left, plus the one setting default that makes the API stream summary text
+at all -- which broke once itself (2.1.277), on the spelling of the ternary
+that chose the request's display, and now rests on the setting upstream
+chooses it from.
 
 Two facts about upstream's list are relied on, both measured on the corpus.
 The renderer keys a virtual message off its block's ``id`` when the block has
@@ -43,98 +45,50 @@ from .. import js
 from ..js import Edit, Source
 from .base import GROUP_OUTPUT, Options, Outcome, Patch
 
-# -------------------------------------------------------------- display mode
+# --------------------------------------------------------- summaries setting
 
-#: The env var *name* is the witness; whatever expression reads it is
-#: upstream's to spell, and is never described here. Spelling such a path is
-#: what killed `org-label` on 2.1.228, and this is the same variable one
-#: migration behind.
-_DISABLE_THINKING = "CLAUDE_CODE_DISABLE_THINKING"
-_DISPLAY = "display"
-_SUMMARIZED = '"summarized"'
-
-
-def _defaulting(read: js.Node) -> js.Node:
-    """The value a `display` read stands for -- itself, or the ``??`` around it.
-
-    Two spellings of one value: a bare read, or a read upstream has already
-    given a fallback of its own. The coalesce is a node the grammar names,
-    where splitting the text on ``??`` was a claim about an operator free to
-    appear anywhere else in the expression -- and the same split then rebuilt
-    the replacement, so one stray ``??`` in front would have been silently
-    dropped from what we wrote back.
-    """
-    parent = read.parent
-    if parent is not None and parent.type == "binary_expression":
-        operator = parent.child_by_field_name("operator")
-        if (
-            operator is not None
-            and js.text(operator) == "??"
-            and parent.child_by_field_name("left") == read
-        ):
-            return parent
-    return read
-
-
-def _chooses(node: js.Node) -> bool:
-    """Is this the ``display`` read the request's thinking value is chosen from?
-
-    The read is the identity and :func:`_defaulting` is what the arm is, so the
-    property is a field of a member read rather than the tail of a spelling --
-    ``.display`` at the end of some text says nothing about what precedes it,
-    which is the half upstream regenerates every build.
-    """
-    if not js.reads(node, _DISPLAY):
-        return False
-    value = _defaulting(node)
-    chosen = value.parent
-    return (
-        chosen is not None
-        and chosen.type == "ternary_expression"
-        and chosen.child_by_field_name("consequence") == value
-        and (alternative := chosen.child_by_field_name("alternative")) is not None
-        and js.text(alternative) == "void 0"
-    )
+#: The setting upstream reads to decide whether a request asks the API for
+#: summarised thinking text -- a name upstream wrote and publishes in its
+#: settings schema, and the one fact every consequence is routed off: the
+#: request's `display`, the beta header withheld while it is on, the `updates`
+#: display the request otherwise falls back to. The request site those reach
+#: is where upstream respells things; the name is what it keeps.
+_SHOW_SUMMARIES = "showThinkingSummaries"
 
 
 def _step_display_mode(source: Source, outcome: Outcome) -> Source:
-    """Default the thinking request to `summarized`.
+    """Default the `showThinkingSummaries` setting on.
 
     Without a display mode in the request the API streams signature-only (or
     late) thinking, so the live row starves -- worst on short thinks. Upstream
-    only asks for summaries when the `showThinkingSummaries` setting is on;
-    default it on instead.
-
-    Two shapes used to be spelled out here -- an inline env check, and the
-    2.1.216 form that hoists it into its own variable and gates the display
-    behind extra feature-helper calls. They are one edit: the display value
-    gains a default. Whatever guards reach it, and in whatever order the
-    declaration lists them, is untouched because it is never matched.
+    asks for ``"summarized"`` exactly when this setting is on, so the setting's
+    read gains a default and the request is never touched: what the display
+    value becomes, where it is chosen and how that choice is spelled are
+    upstream's. 2.1.277 respelled all three at once -- the ternary that chose
+    the value flipped its branches and grew a ``"highlights"`` mode inside the
+    chosen side -- and the locator that stood here, reached through the env-var
+    read sharing the value's ``let`` (comma-fusion, the minifier's) and asking
+    for the consequence of a ternary whose alternative was ``void 0`` (the
+    branch layout, upstream's), found nothing with every anchor standing.
+
+    The read is one on every build in the corpus, spelled ``settings().name??!1``
+    on all of them, and none of that is claimed: every member read is defaulted,
+    as `spinner-tips` reads its setting, and a write is left alone for the
+    reason it gives. An explicit ``false`` in the user's settings still wins,
+    which the request-side default this replaced could not honour.
     """
     step = outcome.step("display-mode")
     edits = []
-    seen: set[int] = set()
-
-    for node in source.find(_DISABLE_THINKING):
-        declaration = js.up(node, "lexical_declaration", "variable_declaration")
-        if declaration is None or declaration.id in seen:
-            continue
-        # The value itself, not the ternary that chooses it: what is edited is
-        # what identified it, so there is no second reach for the same child.
-        display = js.first(declaration, _chooses)
-        if display is None:
+    for node in source.find(_SHOW_SUMMARIES):
+        read = node.parent
+        if read is None or not js.reads(read, _SHOW_SUMMARIES) or js.written(read):
             continue
-        seen.add(declaration.id)
-        value = _defaulting(display)
         step.candidates += 1
         step.applied += 1
-        # Built from the read, so the default we write is a default *of that
-        # read* whichever of the two shapes this build ships. An upstream that
-        # already asks for summaries is the goal achieved, not a rewrite owed.
-        summarized = f"{js.text(display)}??{_SUMMARIZED}"
-        if js.text(value) == summarized:
-            continue
-        edits.append(Edit.replace(value, summarized))
+        # Parenthesised, so it is a default *of that read* inside whatever
+        # expression this build spells around it: a bare ``??`` may not stand
+        # beside ``&&`` or ``||``.
+        edits.append(Edit.replace(read, f"({js.text(read)}??!0)"))
     return source.apply(edits)
 
 
@@ -508,7 +462,7 @@ PATCHES = [
             f'case"{_THINKING_DELTA}"',
             f'case"{_THINKING_TYPES[0]}"',
             f'"{_CONTENT_BLOCK_START}"',
-            _DISABLE_THINKING,
+            _SHOW_SUMMARIES,
         ),
     ),
 ]