lazycodex-ai 5.1.7 → 5.1.8

package/packages/shared-skills/skills/browser/runtime/omowright/manifest.json

@@ -5,5 +5,5 @@
     "index.js": "b6b064fab277031c6c51f5a58b84b31040f9960bf767bf646adc0540c1d25c1b",
     "page-bundle.js": "bfd51e8383cf47200d57387bbbed258bce5a3a3d00c38fc108034d2888e23f0c"
   },
-  "stagedAtUtc": "2026-09-30T23:56:44.170Z"
+  "stagedAtUtc": "2026-10-01T14:48:25.418Z"
 }

package/packages/shared-skills/skills/debugging/SKILL.md

@@ -73,7 +73,7 @@ Each phase has exactly one reference. Read it as you enter the phase — not in
 | 4 | **Oracle Triple** — after 2 consecutive failed rounds, spawn three Oracles with orthogonal framings and synthesize | [references/methodology/04-oracle-triple.md](references/methodology/04-oracle-triple.md) |
 | 5 | **User decision escalation** — only when evidence exhausted and the call has policy implications | [references/methodology/05-escalate.md](references/methodology/05-escalate.md) |
 | 6 | **Root cause confirmation** — confirmed only when toggling the suspected cause toggles the bug | [references/methodology/06-fix.md](references/methodology/06-fix.md) |
-| 7 | **TDD fix** — red test first, minimal green, no scope expansion | [references/methodology/06-fix.md](references/methodology/06-fix.md) |
+| 7 | **Fix locked by a failing proof** — reuse the owner test that already fails or add one regression that fails on the pre-fix code, minimal green, no scope expansion | [references/methodology/06-fix.md](references/methodology/06-fix.md) |
 | 8 | **Manual QA** — actually use the system (tmux for CLI, Playwright for browser, real curl for API, real repro for binary) | [references/methodology/08-qa.md](references/methodology/08-qa.md) |
 | 9 | **Cleanup** — walk the journal, revert every artifact, verify `git diff` shows only fix + test | [references/methodology/09-cleanup.md](references/methodology/09-cleanup.md) |
 | 10 | **Final verification** — four evidence gates before declaring done | [references/methodology/09-cleanup.md](references/methodology/09-cleanup.md) |

package/packages/shared-skills/skills/debugging/references/methodology/06-fix.md

@@ -51,6 +51,14 @@ The "mechanism" field is the acid test. If you can't write the causal chain from
 
 Red, green, refactor. No shortcuts.
 
+### 0. Look for the owner test first
+
+Before writing a reproduction test, find the test that already owns this contract at the strongest boundary. Run it on the pre-fix code:
+
+- **It already fails for this bug.** It is the red proof. Record its failure and skip step 1.
+- **It passes but covers the path.** Extend it with the failing case (a table row, a fixture case) instead of adding a parallel test.
+- **No owner exists.** Write the new reproduction test in step 1, and apply the repository's test-authoring gate if it has one.
+
 ### 1. Red — the reproduction as a test
 
 Write a test that fails *specifically because of this bug*. Requirements: