patch-cc 0.5.0__tar.gz → 0.5.2__tar.gz

{patch_cc-0.5.0 → patch_cc-0.5.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: patch-cc
-Version: 0.5.0
+Version: 0.5.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.5.0 → patch_cc-0.5.2}/docs/CONDUCT.md

@@ -59,8 +59,20 @@ shape that already absorbs every case, found rather than bolted on.
   not guesswork: declare it (`Outcome.declare`) so a green tick cannot cover a dead
   feature. A step nobody declared is a step that cannot report its own death:
   `branding` carried none, so a name badge that stopped being a bold render was
-  a green run, an unchanged banner, and a manifest asserting the new name. See
-  [PLAYBOOK.md](PLAYBOOK.md).
+  a green run, an unchanged banner, and a manifest asserting the new name. And a
+  step answers for its own identity alone, never for a name another step
+  discovered: `live-thinking`'s reducer once skipped itself for want of a helper
+  the memo step had found, and eight required steps read *found nothing* over
+  one memo that had merely moved (2.1.257). See [PLAYBOOK.md](PLAYBOOK.md).
+
+- **Ride what upstream ships working.** When the binary already does for one
+  kind of thing what a patch wants for another — live tool uses, for live
+  thinking — put the patch's data on that path instead of building a twin of
+  it. Every step of a parallel implementation is a claim only the patch needs,
+  and upstream owes it nothing; the path upstream ships is one it cannot break
+  without paying for it. `live-thinking`'s render half broke five times on
+  React idioms before it was cut to three insertions on the tool-use list
+  ([PLAYBOOK.md](PLAYBOOK.md#live-thinking--streamingpy)).
 
 - **Port faithfully.** When you change a patch, verify its output against a real
   bundle — byte-identical where behaviour must not change. `doctor` over the