devlyn-cli 2.6.1 → 2.8.0

package/config/skills/_shared/pair-plan-schema.md

@@ -125,14 +125,14 @@ Top-level wrapper:
       "status":              "sign | block",
       "blocked_ids":         [],
       "signed_plan_sha256":  "...",                  // canonical pre-stamp sha (see below)
-      "model":               "claude-opus-4-7",
+      "model":               "<exact claude model id>",
       "timestamp":           "2026-04-29T..."
     },
     "codex": {
       "status":              "sign | block",
       "blocked_ids":         [],
       "signed_plan_sha256":  "...",
-      "model":               "gpt-5.5",
+      "model":               "<exact codex model id>",
       "timestamp":           "..."
     }
   }

package/config/skills/_shared/runtime-principles.md

@@ -51,7 +51,7 @@ This rule exists because LLMs (including you) are trained to be helpful, compreh
 **The five drift patterns you must refuse to execute on:**
 
 1. **Unrequested work.** "While I'm here, I noticed X is broken/ugly/inefficient" → **stop**. The user did not ask for X. If X is a real defect, surface it as a finding, a follow-up suggestion, or an entry in a TODO list — do NOT fix it inside the current change. Mixing unrequested work with requested work is what makes diffs unreviewable and PRs eternal. **Pre-existing dead code → mention only, do NOT delete; orphans YOUR change created (now-unused imports, variables, functions) → clean them up.**
-2. **Tangential cleanup.** "This file looks messy, let me also tidy..." → **stop**. The current task is the only task. Unrelated cleanup is a separate change requiring its own justification, scope, and pre-flight 0 check. **Match existing style even if you'd write it differently; do NOT touch comments, formatting, or code orthogonal to your real change** — silent side-effects on neighboring lines are the most common Karpathy-observed regression class.
+2. **Tangential cleanup.** "This file looks messy, let me also tidy..." → **stop**. The current task is the only task. Unrelated cleanup is a separate change requiring its own justification, scope, and pre-flight 0 check. **Match existing style even if you'd write it differently; on touched lines, replace only the bytes the task requires and preserve all other bytes, comments, formatting, and orthogonal code.**
 3. **Speculative robustness.** "Just adding a check / fallback / handler for the case where..." → **stop**. If the case has not been observed (in production, in tests, in a finding), it does not belong in this change. Defensive code added for unobserved cases is the most common form of accretion debt — it never gets removed because nobody can prove the case never happens.
 4. **Re-scoping mid-flight.** "Actually, the better way to do this is to also restructure / rename / migrate..." → **stop**. If you discover the requested approach is wrong, surface that to the user with evidence and let them adjudicate. Do NOT silently expand scope. The user's explicit redirect is the only authorization to enlarge a task.
 5. **Curiosity detours.** "Let me also explore how Y works to understand this better..." → **stop**, unless Y is provably on the goal's critical path. Curiosity-driven exploration is creative-mode; default is execution-mode.