patch-cc 0.2.1__tar.gz → 0.2.2__tar.gz

{patch_cc-0.2.1 → patch_cc-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: patch-cc
-Version: 0.2.1
+Version: 0.2.2
 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.2.1 → patch_cc-0.2.2}/docs/PLAYBOOK.md

@@ -17,10 +17,35 @@ constantly. These rules are what keep matchers alive:
   literals, `case` labels, prop names, or control-flow shape.
 - Match the *semantic shape* of a function body, not its symbol names.
 - When upstream ships more than one shape for the same feature, add a second
-  narrow branch — don't widen one regex until it over-matches.
+  narrow branch — don't widen one regex until it over-matches. A different
+  *spelling* of one shape is not a second shape, and does not earn a branch; see
+  "applied to, not reached through" below for where that line falls.
 - Accept statement variants a minifier flips between. The thinking gate broke
   on 2.1.216 solely because `if(x)return null;` became `if(x){return null}` —
   matchers should allow both from day one.
+- **Applied to, not reached through.** Match what a helper is applied to; say
+  nothing about how it is reached. The callee of a zod schema is pure minifier
+  noise — the persisted `effortLevel` reads `E.enum(` on 2.1.216, `A.enum(`,
+  `b.enum(`, `v.enum(`, `w.enum(` through 2.1.223, then `Ir(` on 2.1.224 — and
+  every matcher that named any of it dated itself to one build. 2.1.224 is the
+  proof: `.enum([` dropped from 241 sites to 23 in a single release, because the
+  spelling tracks which *module* a schema lives in (bundled namespace alias vs
+  bare standalone factory), never what the schema is. So the callee is
+  `base.ARRAY_CALL` — whatever sits between the prop name and the array literal,
+  bounded only by statement and block edges — and no spelling is enumerated.
+  Enumerating the spellings seen so far only defers the same break to the next
+  one; that is the boundary of the narrow-branch rule above.
+- **Dissolving the callee raises what the surviving anchors must carry**, and
+  that debt is per-site, never general. `effortLevel:` plus its level array is
+  unique on every build. `model:` plus an array is *not* — 6 sites on
+  2.1.216–220, 12 on 2.1.221–224 — so `MODEL_ENUM`'s
+  ``.optional().describe(`Optional model override`` tail is its sole
+  discriminator, not belt-and-braces. Trimmed, the matcher finds three sites, two
+  of them the settings-scope enum `["user","project","local"]`, and
+  `codex-models` splices Codex ids into it. Measure an anchor's match count on
+  every backup before removing any part of it: under the older, tighter callee
+  that same probe read 1 on all 8 builds, so a measurement taken before the
+  callee was dissolved does not survive it.
 - Match an optional brace **pair** conditionally (`(\{)?…(?(1)\})`), never as
   two independent `\{?` / `\}?`. A lone optional closing brace eats the
   *enclosing* block's `}` on the unbraced shape, and a rewrite that emits its
@@ -41,8 +66,8 @@ Anything the binary can enumerate for us, it does:
   `agentType:"<name>",whenToUse:` carrying `source:"built-in"` in the same
   object (`agents.discover_agents`). Definitions whose `whenToUse` begins with
   `"Internal` are plumbing and are not offered.
-- **Model aliases** come from the Task tool's own input schema: the
-  `model:<zod>.enum([...])` whose describe-string starts
+- **Model aliases** come from the Task tool's own input schema: the `model`
+  enum whose describe-string starts
   `Optional model override` — `agents.MODEL_ENUM`, one compiled anchor because
   `codex-models` splices the chosen Codex ids into the very group
   `discover_models` reads back out.

{patch_cc-0.2.1 → patch_cc-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "patch-cc"
-version = "0.2.1"
+version = "0.2.2"
 description = "Interactive patcher for the Claude Code native binary"
 readme = "README.md"
 requires-python = ">=3.11"

{patch_cc-0.2.1 → patch_cc-0.2.2}/src/patch_cc/__init__.py

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

{patch_cc-0.2.1 → patch_cc-0.2.2}/src/patch_cc/patches/agents.py

@@ -17,6 +17,7 @@ import re
 from dataclasses import dataclass
 
 from .base import (
+    ARRAY_CALL,
     GROUP_MODELS,
     GROUP_OUTPUT,
     IDENT,
@@ -156,7 +157,7 @@ _DEF_WINDOW = 3000
 #: why that ordering is load-bearing). Matched separately, the two would drift
 #: apart on the next upstream reshape, and only one of them would be repaired.
 MODEL_ENUM = compile_js(
-    rf'model:{IDENT}\.enum\(\[((?:"{_MODEL_CHARS}+",?)+)\]\)\.optional\(\)'
+    rf'model:{ARRAY_CALL}((?:"{_MODEL_CHARS}+",?)+)\]\)\.optional\(\)'
     rf'\.describe\([`"]Optional model override'
 )
 #: Used only if the Task-tool schema anchor ever disappears.

{patch_cc-0.2.1 → patch_cc-0.2.2}/src/patch_cc/patches/base.py

@@ -277,6 +277,19 @@ def compile_js(pattern: str, flags: int = 0) -> re.Pattern[str]:
 # Matches a minified identifier, the JS `[A-Za-z_$][\w$]*` idiom.
 IDENT = r"[A-Za-z_$][\w$]*"
 
+#: From a schema's property name to the *opening* of the array literal it is
+#: built from -- the ``([`` included, so a site composes this as
+#: ``prop:{ARRAY_CALL}`` and never spells the call open itself.
+#:
+#: Whatever expression the build reaches the factory through is skipped
+#: unmodelled, because the callee is minifier noise that churns every few
+#: releases (``E.enum(`` ... ``w.enum(`` ... ``Ir(`` for one unchanged schema).
+#: Lazy but not unbounded: ``[^;{}]`` cannot cross a statement or block edge,
+#: and the spans it actually spends are 47-51 and 88-92 characters on every
+#: build we hold. What the surviving anchors must carry instead -- which is a
+#: debt this raises, per site: docs/PLAYBOOK.md.
+ARRAY_CALL = r"[^;{}]*?\(\["
+
 
 def switch_case_end(content: str, start: int) -> int:
     """End offset of a ``switch`` arm beginning at ``start``.

{patch_cc-0.2.1 → patch_cc-0.2.2}/src/patch_cc/patches/thinking.py

@@ -32,6 +32,7 @@ from __future__ import annotations
 import re
 
 from .base import (
+    ARRAY_CALL,
     GROUP_MODELS,
     GROUP_OUTPUT,
     IDENT,
@@ -219,7 +220,7 @@ _EFFORT_GATE = compile_js(
 # then reverted by a Claude update) treats it as unset rather than failing the
 # whole settings parse -- the property that makes this patch safe to lose.
 _EFFORT_SCHEMA = compile_js(
-    rf'effortLevel:({IDENT})\.enum\(\["low","medium","high","xhigh"(,"max")?\]\)'
+    rf'(effortLevel:{ARRAY_CALL})"low","medium","high","xhigh"(?:,"max")?(\]\))'
 )
 
 
@@ -242,14 +243,14 @@ def _max_effort(content: str, _options: Options, outcome: Outcome) -> str:
 
     output = _EFFORT_GATE.sub(widen_gate, content)
 
+    # No already-applied branch, unlike the gate above: the levels are spliced
+    # into the array the match found, so a bundle that already carries `max` is
+    # rewritten to itself. `widen_gate` needs one because its unconditional path
+    # also normalises the brace form, and would churn a bundle that was fine.
     def widen_schema(match: re.Match[str]) -> str:
         schema.candidates += 1
         schema.applied += 1
-        if match.group(2):
-            return match.group(0)
-        return (
-            f'effortLevel:{match.group(1)}.enum(["low","medium","high","xhigh","max"])'
-        )
+        return f'{match.group(1)}"low","medium","high","xhigh","max"{match.group(2)}'
 
     return _EFFORT_SCHEMA.sub(widen_schema, output)