devlyn-cli 3.2.0 → 3.3.0

package/AGENTS.md

@@ -38,11 +38,11 @@ Each skill's `SKILL.md` is the source of truth for flags and workflow. Do not du
 
 Engine roles: orchestrator = whichever CLI the user opened (this contract is symmetric with CLAUDE.md. If you are Codex orchestrating `/devlyn:resolve`, the phase machinery is mandatory regardless of task size; if you will not run it, say so explicitly and stop — do not silently degrade to ad-hoc execution); legacy executor (with optional separate worker/primary/pair profiles) uses the canonical skill's orchestrator-supported default, overridable per run with `--engine <name>` or durably via machine-local `.devlyn/engines.json` `{"executor": "<name>", "pair_judge_priority": ["<name>", ...]}`; PLAN is orchestrator-fixed and never inherits `--engine` or the executor pin; pair judge = first available OTHER engine, default for VERIFY whenever available; risk probes remain conditional and --no-pair opts out. Pins fail closed (`BLOCKED:<engine>-unavailable` / `BLOCKED:invalid-engine-config`); new engines plug in by shipping `_shared/adapters/<name>.md`. `/devlyn:engines` (no args) shows the role table + detected engines; `executor <name>` / `pair <name>,...` / `clear` manage the pins. The executor pin binds the orchestrator in plain conversation too, not only inside a skill run: when you would implement directly and executor is pinned to a non-default engine, route that work through the pin — via `/devlyn:resolve` (reads it at PHASE 0) or by delegating to that engine; no pin / no file → use the canonical skill's orchestrator-supported default. The pair-judge pin stays pipeline-scoped. `/devlyn:engines role` configures explicit engine/model/effort for supported worker and judge routes; `/devlyn:resolve --role-config <path>` overrides roles for one run. Canonical skills define precedence, evidence and unsupported-route errors; absent profiles preserve existing defaults.
 
-Conversational entry: Before loading a workflow or writing files, inspect the requested change and relevant callers/tests. Quoted phase names, past logs and skill-file paths are context, not an instruction to invoke that workflow; follow the current user request. Default to direct execution when inspection makes the requested behavior, affected boundaries and verification tractable in the current context, including bounded multi-file work. Preserve requested behavior, scope, explicit constraints and the executor pin; make scoped edits, run required checks, review the final diff, and report changes with evidence. One concise route/check explanation suffices; ordinary direct work needs no spec, pipeline state, phase workers or extra approval. For direct/full/queue work, the outer owner reads `references/task-completion.md` relative to the installed `devlyn:resolve` skill's directory: prospective task-branch ownership (linked worktree optional), scoped commit acceptance, then PR/merge and recoverable owned-resource cleanup after required archive/queue commits. Local-only/no-push wins; delivery pending/failure stays separate from product verification.
+Conversational entry: Before loading a workflow or writing files, inspect the requested change and relevant callers/tests. Quoted phase names, past logs and skill-file paths are context, not an instruction to invoke that workflow; follow the current user request. Default to direct execution when inspection makes the requested behavior, affected boundaries and verification tractable in the current context, including bounded multi-file work. Preserve requested behavior, scope, explicit constraints and the executor pin; make scoped edits, run required checks, review the final diff, and report changes with evidence. One concise route/check explanation suffices; ordinary direct work needs no spec, pipeline state, phase workers or extra approval. For direct/full/queue work, the outer owner reads `references/task-completion.md` relative to the installed `devlyn:resolve` skill's directory: prospective task-branch ownership (own linked worktree), scoped commit acceptance, then push + PR after required archive/queue commits. Local-only/no-push wins; delivery pending/failure stays separate from product verification.
 
 Use full `/devlyn:resolve` automatically only when inspection identifies interacting requirements or verification work too complex to manage reliably in the current context, such as coupled durable state, concurrent ownership and failure recovery across boundaries. Name the concrete interaction or verification gap. Domain labels (security/auth/payment/persistence/concurrency/API), file count and a spec document alone do not trigger it. Investigate or clarify missing intent/access first; a pipeline cannot supply them. Direct work still requires risk-proportionate checks and independent review for consequential changes. Explicit resolve (even small), explicit spec-mode workflows and queue drains retain all canonical phases, independent verification, pins and failure handling. If the full-route condition emerges mid-edit, carry the existing delta into its scope/evidence; do not reset the baseline or reconfirm existing authorization.
 
-Full-route handoff + loop engineering: the orchestrating model — not the user — invokes the skills. `/devlyn:queue` fronts the intent queue (`docs/specs/queue.md`): no args = status, `add <intent>`, `drain` = serial unattended drain per the contract below. Work selected for full resolve is written to `docs/specs/<id>/spec.md` (always a spec file — the user's reviewed contract; free-form large assumes-and-logs instead of halting, zero-scope-signal goals still halt to ideate), summarized once for user review, then run hands-free via `--spec`. Outer loop per task: before the first full run, commit the scoped queue-item delta (when applicable) and linked spec bundle; findings-backed verdicts (NEEDS_WORK, verify/build-gate exhaustion) get a committed spec amendment before re-run, max 3 iterations; infrastructure / invalid-input / engine-availability / implement-empty BLOCKED verdicts surface immediately. Unattended queue drain (`docs/specs/queue.md`, strictly serial): assumptions may only take scope-narrowing, reversible, non-user-visible defaults — material ambiguity marks the item `[F] needs-review`; commit every terminal `[x]` / `[F]` transition before advancing. The canonical commit order is `config/skills/devlyn:resolve/references/outer-loop.md`.
+Full-route handoff + loop engineering: the orchestrating model — not the user — invokes the skills. `/devlyn:queue` fronts the intent queue (`docs/specs/queue.md`): no args = status, `add <intent>`, `drain` = serial unattended drain per the contract below. Work selected for full resolve is written to `docs/specs/<id>/spec.md` (always a spec file — the user's reviewed contract; free-form large assumes-and-logs instead of halting, zero-scope-signal goals still halt to ideate), summarized once for user review, then run hands-free via `--spec`. Outer loop per task: before the first full run, commit the scoped queue-item delta (when applicable) and linked spec bundle; findings-backed verdicts (NEEDS_WORK, BLOCKED:repair-budget-exhausted) get a committed spec amendment before re-run, max 3 iterations; infrastructure / invalid-input / engine-availability / implement-empty BLOCKED verdicts surface immediately. Unattended queue drain (`docs/specs/queue.md`, strictly serial): assumptions may only take scope-narrowing, reversible, non-user-visible defaults — material ambiguity marks the item `[F] needs-review`; commit every terminal `[x]` / `[F]` transition before advancing. The canonical commit order is `config/skills/devlyn:resolve/references/outer-loop.md`.
 
 ## Subtractive-First Editing
 

package/CLAUDE.md

@@ -51,7 +51,7 @@ Each skill's `SKILL.md` is the source of truth for its flags and workflow — do
 
 ### Conversational entry + full-route handoff
 
-Before loading a workflow or writing files, inspect the requested change and relevant callers/tests. Quoted phase names, past logs and skill-file paths are context, not an instruction to invoke that workflow; follow the current user request. Default to direct execution when inspection makes the requested behavior, affected boundaries and verification tractable in the current context, including bounded multi-file work. Preserve requested behavior, scope, explicit constraints and the executor pin; make scoped edits, run required checks, review the final diff, and report changes with evidence. One concise route/check explanation suffices; ordinary direct work needs no spec, pipeline state, phase workers or extra approval. For direct/full/queue work, the outer owner reads `references/task-completion.md` relative to the installed `devlyn:resolve` skill's directory: prospective task-branch ownership (linked worktree optional), scoped commit acceptance, then PR/merge and recoverable owned-resource cleanup after required archive/queue commits. Local-only/no-push wins; delivery pending/failure stays separate from product verification.
+Before loading a workflow or writing files, inspect the requested change and relevant callers/tests. Quoted phase names, past logs and skill-file paths are context, not an instruction to invoke that workflow; follow the current user request. Default to direct execution when inspection makes the requested behavior, affected boundaries and verification tractable in the current context, including bounded multi-file work. Preserve requested behavior, scope, explicit constraints and the executor pin; make scoped edits, run required checks, review the final diff, and report changes with evidence. One concise route/check explanation suffices; ordinary direct work needs no spec, pipeline state, phase workers or extra approval. For direct/full/queue work, the outer owner reads `references/task-completion.md` relative to the installed `devlyn:resolve` skill's directory: prospective task-branch ownership (own linked worktree), scoped commit acceptance, then push + PR after required archive/queue commits. Local-only/no-push wins; delivery pending/failure stays separate from product verification.
 
 Use full `/devlyn:resolve` automatically only when inspection identifies interacting requirements or verification work too complex to manage reliably in the current context, such as coupled durable state, concurrent ownership and failure recovery across boundaries. Name the concrete interaction or verification gap. Domain labels (security/auth/payment/persistence/concurrency/API), file count and a spec document alone do not trigger it. Investigate or clarify missing intent/access first; a pipeline cannot supply them. Direct work still requires risk-proportionate checks and independent review for consequential changes. Explicit resolve (even small), explicit spec-mode workflows and queue drains retain all canonical phases, independent verification, pins and failure handling. If the full-route condition emerges mid-edit, carry the existing delta into its scope/evidence; do not reset the baseline or reconfirm existing authorization.
 
@@ -60,7 +60,7 @@ The user does not invoke skills manually; the orchestrating model does. For work
 1. Write the agreed contract to `docs/specs/<id>/spec.md` (+ `spec.expected.json` when mechanical verifications exist). Use a spec file for the selected work — a written spec is the user's reviewed contract; free-form large now assumes-and-logs instead of halting (zero-scope-signal goals still halt to ideate).
 2. Present a one-screen plan-contract summary — the user's single review checkpoint, BEFORE the pipeline starts.
 3. On go-ahead, commit the scoped queue-item delta (when applicable) and linked spec bundle, then invoke `/devlyn:resolve --spec <path>` hands-free to completion.
-4. **Per-task outer loop**: read the terminal verdict. Successful normal-run archive → outer-owner completion per the canonical task-completion reference, after any terminal queue commit. Verdicts backed by spec/verification findings (NEEDS_WORK, verify/build-gate exhaustion) → adjudicate the findings, amend the spec (recorded in the spec file; spec stays read-only inside a run), commit that scoped amendment, then re-invoke — at most 3 outer iterations, then surface with the findings trail. Infrastructure, invalid-input, engine-availability, and implement-empty BLOCKED verdicts are not spec-amendable: surface immediately. Every iteration re-enters through committed durable artifacts (spec, findings, run archive), never conversation memory.
+4. **Per-task outer loop**: read the terminal verdict. Successful normal-run archive → outer-owner completion per the canonical task-completion reference, after any terminal queue commit. Verdicts backed by spec/verification findings (NEEDS_WORK, BLOCKED:repair-budget-exhausted) → adjudicate the findings, amend the spec (recorded in the spec file; spec stays read-only inside a run), commit that scoped amendment, then re-invoke — at most 3 outer iterations, then surface with the findings trail. Infrastructure, invalid-input, engine-availability, and implement-empty BLOCKED verdicts are not spec-amendable: surface immediately. Every iteration re-enters through committed durable artifacts (spec, findings, run archive), never conversation memory.
 
 **Intent queue (unattended drain)**: the user stacks intents in `docs/specs/queue.md` (ordered checklist; `/devlyn:queue` is the front-end — no args shows status, `add <intent>` appends, `drain` starts the serial drain). Drain strictly serially — per item: spec it, commit the scoped owner baseline, run the outer loop, mark `[x]` done or `[F]` blocked with reason, commit that terminal transition, then complete eligible delivery once. Retain PR/pending workspaces; unavailable separate safe placement stops the drain with remaining items pending. A product-blocked item otherwise never halts the queue. The queue entry is the user's go-ahead, so assume-and-log replaces the interactive checkpoint — but unattended assumptions may only take scope-narrowing, reversible, non-user-visible defaults. Material ambiguity (user-visible behavior, data/state semantics, new files/scripts/flags, implementation surface) → mark `[F] needs-review`, commit it, and move on. End the drain with a per-item product verdict, separate delivery status/URL/resume and assumptions report. The canonical commit order is `config/skills/devlyn:resolve/references/outer-loop.md`.
 

package/README.md

@@ -84,27 +84,14 @@ PLAN  →  IMPLEMENT  →  BUILD_GATE  →  CLEANUP  →  VERIFY (fresh subagent
 Common flags: `--engine claude|codex|omp` (default: the orchestrator-supported default), `--role-config <path>` (one-run worker/judge profiles, see below), `--bypass build-gate,cleanup`, `--pair-verify` (force pair-mode JUDGE in VERIFY), `--no-pair` (intentional solo VERIFY), `--risk-probes` / `--no-risk-probes`, `--perf` (per-phase timing).
 `--pair-verify` and `--no-pair` are mutually exclusive; using both stops with `BLOCKED:invalid-flags`.
 
-Free-form goals that ask for benchmark evidence, pair-evidence, risk-probe
-measurement, `solo<pair` proof, or solo-headroom work must include an
-actionable `solo-headroom hypothesis` naming the visible behavior `solo_claude`
-is expected to miss plus a backticked observable command; the backticked line
-itself must contain `miss` and be framed as the command/observable that exposes it. Without that,
-`/devlyn:resolve` stops with `BLOCKED:solo-headroom-hypothesis-required` and
-points you to `/devlyn:ideate` instead of inventing a weak hypothesis.
-Free-form goals that add or run a new unmeasured benchmark, shadow fixture,
-golden fixture, risk-probe, or pair-evidence candidate must also include
-`solo ceiling avoidance`, mention `solo_claude`, and name the concrete
-difference from rejected or solo-saturated controls such as `S2`-`S6`; without
-that, `/devlyn:resolve` stops with `BLOCKED:solo-ceiling-avoidance-required`.
-
-Accepted tasks default to owner completion: scoped commit → push → PR → normal
-protected merge → recoverable cleanup of prospectively owned resources. Set
-`git config --local devlyn.completionMode pr` to stop at a PR, or `auto` to restore
-the default; `task-complete.py complete --mode auto|pr` overrides one task.
-Local-only/no-push instructions take precedence. Linked worktrees are optional;
-existing branches cannot be adopted. Full runs require successful archive before
-delivery; direct tasks use their actual checks and root acceptance. Verify-only
-never publishes. Pending checks or unsupported merge policy retain resources and
+Each task gets its own linked worktree; accepted tasks default to scoped commit → push → PR.
+After the PR merges, either mode cleans the worktree and branch its session
+released; anything in use is kept. Set `git config --local devlyn.completionMode auto` to
+also request a normal protected merge; `task-complete.py complete --mode auto|pr`
+overrides one task. Local-only/no-push instructions take precedence; existing
+branches cannot be adopted. Full runs require successful archive before delivery;
+direct tasks use their actual checks and root acceptance. Verify-only never
+publishes. Pending checks or unsupported merge policy retain resources and
 report a receipt-based resume command separately from product verification.
 See [task completion](config/skills/devlyn:resolve/references/task-completion.md)
 for allocation, acceptance, writer cessation and recovery.
@@ -157,74 +144,6 @@ Pin roles durably with `/devlyn:engines` (no args shows the role table + detecte
 
 If an engine is absent when explicitly selected by flag, pin, or role profile, or OTHER engine is absent under `--pair-verify`, the harness stops with `BLOCKED:<engine>-unavailable` and prints setup guidance. Automatic VERIFY absence is a reported solo route. Use `--no-pair` only when intentionally accepting solo VERIFY; use `--no-risk-probes` only when intentionally disabling automatic high-risk probes.
 
-### Benchmark score runs
-
-Use the benchmark CLI when a change claims `solo_claude < pair`. The score-focused runners print the run id, startup gate lines, blind-judge score tables, fixture pair margins, average pair margin, wall-time ratio, and failure reasons:
-
-```bash
-npx devlyn-cli benchmark headroom --min-fixtures 3 F16-cli-quote-tax-rules F23-cli-fulfillment-wave F25-cli-cart-promotion-rules
-npx devlyn-cli benchmark recent
-npx devlyn-cli benchmark recent --out-md /tmp/devlyn-recent-benchmark.md
-npx devlyn-cli benchmark frontier --out-md /tmp/devlyn-pair-frontier.md
-npx devlyn-cli benchmark audit --out-dir /tmp/devlyn-benchmark-audit
-npx devlyn-cli benchmark audit-headroom --out-json /tmp/devlyn-headroom-audit.json
-npx devlyn-cli benchmark pair --min-fixtures 3 --max-pair-solo-wall-ratio 3 F16-cli-quote-tax-rules F23-cli-fulfillment-wave F25-cli-cart-promotion-rules
-```
-
-`benchmark recent` prints a compact, wrap-safe snapshot of the current local
-pair evidence: status counts, pair-lift aggregates, and one card per passing
-pair-evidence fixture. It intentionally avoids wide Markdown tables, so the
-same output stays readable in narrow terminals, PR comments, and release notes.
-`benchmark frontier` also prints a stdout score summary for existing complete pair
-evidence rows, including pair arm, trigger reasons, average/minimum pair margin,
-and wall ratio, plus row-level verdicts even when `--out-json` or `--out-md`
-writes an artifact. Markdown frontier artifacts include a `Triggers` column.
-Full-pipeline pair gate artifacts record `require_hypothesis_trigger` in JSON
-and include a Markdown `Hypothesis trigger` column, so strict regenerated
-evidence shows whether each row carried `spec.solo_headroom_hypothesis`.
-`benchmark audit` is the provider-free release/handoff guard: it writes
-`audit.json` with the frontier summary, artifact map, and compact trigger-backed verdict-bearing `pair_evidence_rows`
-(each row carries `pair_trigger_eligible: true`, non-empty `pair_trigger_reasons`, `pair_trigger_has_canonical_reason: true`, and `pair_trigger_has_hypothesis_reason`; the audit fails rows missing trigger reasons or missing actionable solo-headroom hypotheses in fixture `spec.md` whose observable command matches `expected.json`), runs the frontier with
-`--fail-on-unmeasured`, requires at least four fixtures with passing pair evidence,
-revalidates frontier `verdict: PASS`, zero unmeasured candidates, and revalidates `pair_mode: true`,
-the default 5-point pair margin, and 3x pair/solo wall ratio, then
-audits failed headroom results. The audit stdout also prints
-`headroom_rejections=...`, `pair_evidence_quality=...`,
-`pair_trigger_reasons=...`, `pair_evidence_hypotheses=...`, and
-`pair_evidence_hypothesis_triggers=...` handoff rows, plus
-`pair_trigger_historical_aliases=...` when archived evidence includes legacy
-trigger aliases and `pair_evidence_hypothesis_trigger_gaps=...` when documented
-hypotheses have not yet propagated into trigger reasons, with the rejected-fixture
-coverage counts plus actual minimum pair margin, maximum pair/solo wall ratio,
-and canonical trigger reason coverage plus row-match status.
-The compact evidence row count must match the frontier evidence count,
-`checks.frontier_stdout` records summary, aggregate, final-verdict, expected, printed score-row, trigger-visible row, and hypothesis-trigger-visible row counts,
-`checks.headroom_rejections` records child verdict plus unrecorded/unsupported counts,
-`checks.pair_evidence_quality` records the same quality thresholds from the compact rows,
-`checks.pair_trigger_reasons` records canonical/historical-alias/exposed/total trigger-reason row counts, fixture-level historical alias details, summary count, and row-match status,
-`checks.pair_evidence_hypotheses` records documented/total pair-evidence hypothesis row counts,
-and `checks.pair_evidence_hypothesis_triggers` records whether documented hypotheses also appear as `spec.solo_headroom_hypothesis` trigger reasons plus fixture-level gap details
-so incomplete or low-quality local score artifacts cannot inflate the claim.
-Add `--require-hypothesis-trigger` to turn those hypothesis-trigger gaps from
-archived-evidence WARN rows into release-blocking FAIL rows for newly
-regenerated pair evidence.
-
-```bash
-npx devlyn-cli benchmark audit --require-hypothesis-trigger --out-dir /tmp/devlyn-benchmark-audit-strict
-```
-
-Historical trigger aliases are only reported for archived artifact review; new
-current pair-evidence gates fail historical-only or unknown trigger reasons and
-require at least one canonical `pair_trigger.reasons` entry.
-`benchmark audit-headroom` fails if an active failed headroom fixture is missing
-from both rejected registry and passing pair evidence.
-Headroom runs use the current claim gate: `bare <= 60`, `solo_claude <= 80`,
-and the default 5-point `bare`/`solo_claude` headroom margins before spending a pair arm.
-Add `--dry-run` to either score runner to validate args, fixture ids, minimum
-fixture count, and the replay command without running arms or judges. Dry-runs
-and lint prove wiring only; real score claims must cite the run id and fixture
-ids.
-
 ### Migration from earlier versions
 
 Reinstall with the new version to refresh instructions and skills for the selected
@@ -235,17 +154,16 @@ its defaults. Exact pre-update backups are saved in `.devlyn/instructions/`.
 When recovery is needed, pre-existing symlinks or non-directory entries at `.devlyn/` or
 `.devlyn/instructions/` stop installation without replacing the instruction file.
 
-Templates from versions 3.0.0–3.1.2 migrate automatically, including custom
-text before or after the template. Replaced or extended introductions under the
-original project heading also migrate when the entire body from `## North Star`
-onward matches a known template hash. Replacement project rules are preserved
-outside the managed block; only an exact original introduction is removed.
-Recognizable leftover Devlyn text, changed bodies and ambiguous templates stop
-with a concise recovery message and leave the original unchanged. The message
-links an exact `.backup`, new defaults in `.incoming`, and a `.merge.md` guide.
-Compare the two files, preserve all project rules outside one new managed block,
-and rerun the same install command. Earlier selected agents may already be updated.
-Plain custom instruction files retain their contents and gain a managed block.
+Older and mixed-version templates migrate automatically. Within recognizable
+Devlyn sections, exact historical paragraphs and list items are replaced;
+modified or unknown text and its headings are preserved outside the new block.
+Edits inside an existing managed block are preserved outside it too. Plain custom
+files and rules outside managed blocks retain their contents. Unknown old text
+is kept conservatively, even when it may contain obsolete defaults.
+Malformed or duplicate managed markers still stop with an exact `.backup`, new
+defaults in `.incoming`, and a `.merge.md` guide; the original remains unchanged.
+Release packaging refreshes the offline fingerprints from Git history using
+`node scripts/update-instruction-templates.js`; installation needs no Git or network.
 Use 3.1.3 or newer consistently: older installers still overwrite `CLAUDE.md`.
 
 <!-- legacy-surface-map:begin — retired command names below are documented as OLD, not current; lint Check 10c skips this block -->
@@ -261,19 +179,6 @@ Earlier versions of devlyn-cli shipped 16+ slash commands. The iter-0034 Phase 4
 
 ---
 
-## Auto-Activated Skills
-
-These activate automatically — no commands needed. They shape how Claude thinks during relevant tasks.
-
-| Skill | Activates During |
-|---|---|
-| `root-cause-analysis` | Debugging — enforces 5 Whys, evidence standards |
-| `code-review-standards` | Reviews — severity framework, approval criteria |
-| `ui-implementation-standards` | UI work — design fidelity, accessibility, responsiveness |
-| `code-health-standards` | Maintenance — dead code prevention, complexity thresholds |
-
----
-
 ## Optional Add-ons
 
 Selected during install. Run `npx devlyn-cli` again to add more.
@@ -293,6 +198,10 @@ Selected during install. Run `npx devlyn-cli` again to add more.
 | `devlyn:pencil-pull` | Pull Pencil designs into code |
 | `devlyn:pencil-push` | Push codebase UI to Pencil canvas |
 | `devlyn:reap` | Safely reap orphaned MCP / codex / Superset child processes |
+| `code-health-standards` | Maintainability standards — dead code, dependencies, complexity, naming |
+| `code-review-standards` | Severity framework and approval criteria for reviews |
+| `root-cause-analysis` | Evidence-first why-chain debugging |
+| `ui-implementation-standards` | UI quality bar — design tokens, accessibility, state coverage, responsive layout |
 
 </details>
 

package/bin/devlyn.js

@@ -13,8 +13,7 @@ const { updateInstructions, InstructionError } = require('./instructions');
 
 // The devlyn skill bundle installed into every skill-capable agent's loader
 // directory. Single source of truth so codex/omp/pi stay in lockstep — adding a
-// skill here installs it everywhere. Standards skills (code-*, root-cause-*,
-// ui-*) stay Claude-core-only, matching the pre-existing Codex bundle.
+// skill here installs it everywhere.
 const DEVLYN_CORE_SKILLS = ['devlyn:resolve', 'devlyn:ideate', 'devlyn:design-ui', 'devlyn:engines', 'devlyn:queue', '_shared'];
 const DEVLYN_SKILL_DIR_STAMP = '__DEVLYN_SKILL_DIR__';
 const DEVLYN_INSTALL_MARKER = '.devlyn-install.json';
@@ -169,6 +168,11 @@ const DEPRECATED_DIRS = [
   // upgrade so users only have them if they opt in via the interactive
   // installer (matches the pencil-pull / pencil-push pattern).
   'skills/devlyn:reap',
+  // 0221 Session 1: standards skills moved to optional-skills/ (opt-in).
+  'skills/code-health-standards',
+  'skills/code-review-standards',
+  'skills/root-cause-analysis',
+  'skills/ui-implementation-standards',
   // Deleted entirely on 2026-05-14 (devlyn:team-design-ui merged into
   // devlyn:design-ui; devlyn:design-system removed outright). Entries kept
   // so users who previously opted in get their stale copies purged on upgrade.
@@ -237,6 +241,10 @@ const OPTIONAL_ADDONS = [
   { name: 'devlyn:pencil-pull', desc: 'Pull Pencil designs into code with exact visual fidelity', type: 'local' },
   { name: 'devlyn:pencil-push', desc: 'Push codebase UI to Pencil canvas for design sync', type: 'local' },
   { name: 'devlyn:reap', desc: 'Safely reap orphaned MCP / codex / Superset child processes left behind by long Claude sessions', type: 'local' },
+  { name: 'code-health-standards', desc: 'Maintainability standards — dead code, dependencies, complexity, naming, hygiene', type: 'local' },
+  { name: 'code-review-standards', desc: 'Severity framework and approval criteria for reviewing a change', type: 'local' },
+  { name: 'root-cause-analysis', desc: 'Evidence-first why-chain debugging to the actionable root cause', type: 'local' },
+  { name: 'ui-implementation-standards', desc: 'UI quality bar — design tokens, WCAG 2.1 AA, state coverage, responsive layout', type: 'local' },
   // External skill packs (installed via npx skills add)
   { name: 'vercel-labs/agent-skills', desc: 'React, Next.js, React Native best practices', type: 'external' },
   { name: 'supabase/agent-skills', desc: 'Supabase integration patterns', type: 'external' },
@@ -660,7 +668,7 @@ function detectOtherCLIs() {
   return detected;
 }
 
-// Install devlyn:resolve + devlyn:ideate + devlyn:design-ui + _shared skills into a CLI's
+// Install DEVLYN_CORE_SKILLS into a CLI's
 // global skills directory (e.g. ~/.codex/skills/). Returns count of skills
 // copied. Skipped silently for CLIs without a skillsDir (e.g. cursor, copilot
 // at the time of writing — they don't have an analogous skill-loader).
@@ -722,7 +730,7 @@ function installAgentsForCLI(cliKey) {
   const instr = installInstructionsForCLI(cliKey);
   const skillsCopied = installSkillsForCLI(cliKey);
   if (skillsCopied > 0) {
-    log(`  → ${skillsCopied} skill${skillsCopied > 1 ? 's' : ''} installed (devlyn:resolve / devlyn:ideate / devlyn:design-ui / _shared)`, 'dim');
+    log(`  → ${skillsCopied} skill${skillsCopied > 1 ? 's' : ''} installed (${DEVLYN_CORE_SKILLS.join(' / ')})`, 'dim');
   }
   return instr || skillsCopied > 0;
 }
@@ -928,19 +936,11 @@ function installClaudeCore() {
   // Configure global Claude Code settings (~/.claude/settings.json)
   // Project settings may refer to this same file; merge the latest bytes.
   const globalSettings = readGlobalSettings();
-  let globalSettingsChanged = false;
-  if (!globalSettings.env.CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING) {
-    globalSettings.env.CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING = '1';
-    globalSettingsChanged = true;
-  }
   if (!globalSettings.env.ENABLE_PROMPT_CACHING_1H) {
     globalSettings.env.ENABLE_PROMPT_CACHING_1H = 'true';
-    globalSettingsChanged = true;
-  }
-  if (globalSettingsChanged) {
     if (!fs.existsSync(globalClaudeDir)) fs.mkdirSync(globalClaudeDir, { recursive: true });
     fs.writeFileSync(globalSettingsPath, JSON.stringify(globalSettings, null, 2) + '\n');
-    log('  → ~/.claude/settings.json (disabled adaptive thinking, enabled 1h prompt caching)', 'dim');
+    log('  → ~/.claude/settings.json (enabled 1h prompt caching)', 'dim');
   }
 
   log('\n✅ Claude Code config installed!', 'green');
@@ -1022,15 +1022,6 @@ function showHelp() {
   log('  npx devlyn-cli -y           Install Claude core without prompts');
   log('  npx devlyn-cli agents       Install agents for detected CLIs');
   log('  npx devlyn-cli agents all   Install agents for all supported CLIs');
-  log('  npx devlyn-cli benchmark    Run the resolve benchmark suite');
-  log('  npx devlyn-cli benchmark recent              Show compact recent benchmark results');
-  log('  npx devlyn-cli benchmark frontier            Show pair candidate frontier scores/triggers without providers');
-  log('  npx devlyn-cli benchmark audit               Audit pair evidence readiness');
-  log('  npx devlyn-cli benchmark audit-headroom      Audit failed headroom results');
-  log('  npx devlyn-cli benchmark headroom <fixtures...>  Score bare vs solo_claude headroom');
-  log('  npx devlyn-cli benchmark pair <fixtures...>      Score solo_claude vs pair path');
-  log('  npx devlyn-cli benchmark --bless         If ship-gate passes, promote baseline');
-  log('  npx devlyn-cli benchmark --dry-run       Validate suite setup without model invocation');
   log('  npx devlyn-cli --help       Show this help\n');
   log('Optional skills (select during install):', 'green');
   OPTIONAL_ADDONS.filter((a) => a.type === 'local').forEach((skill) => {
@@ -1051,170 +1042,6 @@ function showHelp() {
   log('');
 }
 
-function showBenchmarkHelp() {
-  log('Usage:', 'green');
-  log('  npx devlyn-cli benchmark [suite] [options] [fixtures...]');
-  log('  npx devlyn-cli benchmark recent [options]');
-  log('  npx devlyn-cli benchmark frontier [options]');
-  log('  npx devlyn-cli benchmark audit [options]');
-  log('  npx devlyn-cli benchmark audit-headroom [options]');
-  log('  npx devlyn-cli benchmark headroom [options] <fixtures...>');
-  log('  npx devlyn-cli benchmark pair [options] <fixtures...>');
-  log('');
-  log('Score-focused runs:', 'green');
-  log('  recent   Show compact, wrap-safe recent benchmark results');
-  log('  frontier Show active rejected/evidence/unmeasured pair candidates, scores, and triggers without providers');
-  log('  audit     Fail on unmeasured pair candidates and invalid headroom rejections');
-  log('            Prints frontier score rows plus headroom and pair quality handoff rows');
-  log('  audit-headroom  Fail on active failed or unsupported headroom rejections');
-  log('  headroom  Score bare vs solo_claude before spending the pair arm');
-  log('  pair      Score solo_claude vs the selected pair path and print gate tables');
-  log('');
-  log('Shadow suite:', 'green');
-  log('  npx devlyn-cli benchmark suite --suite shadow --dry-run');
-  log('            Lists shadow tasks only; use headroom/pair with explicit S* ids for real measurement');
-  log('');
-  log('Examples:', 'green');
-  log('  npx devlyn-cli benchmark --dry-run F1-cli-trivial-flag');
-  log('  npx devlyn-cli benchmark recent');
-  log('  npx devlyn-cli benchmark recent --out-md /tmp/devlyn-recent-benchmark.md');
-  log('  npx devlyn-cli benchmark frontier --out-md /tmp/devlyn-pair-frontier.md');
-  log('  npx devlyn-cli benchmark audit --out-dir /tmp/devlyn-benchmark-audit');
-  log('  npx devlyn-cli benchmark audit-headroom --out-json /tmp/devlyn-headroom-audit.json');
-  log('  npx devlyn-cli benchmark headroom --min-fixtures 3 F16-cli-quote-tax-rules F23-cli-fulfillment-wave F25-cli-cart-promotion-rules');
-  log('  npx devlyn-cli benchmark pair --min-fixtures 3 --max-pair-solo-wall-ratio 3 F16-cli-quote-tax-rules F23-cli-fulfillment-wave F25-cli-cart-promotion-rules');
-  log('');
-}
-
-function showBenchmarkModeHelp(mode) {
-  if (mode === 'recent') {
-    log('Usage:', 'green');
-    log('  npx devlyn-cli benchmark recent [options]');
-    log('');
-    log('Options:', 'green');
-    log('  --out-json PATH');
-    log('  --out-md PATH');
-    log('  --fixtures-root PATH');
-    log('  --registry PATH');
-    log('  --results-root PATH');
-    log('  --max-width N  default: 92');
-    log('  --min-pair-margin N  default: 5');
-    log('  --max-pair-solo-wall-ratio N  default: 3');
-    log('');
-    log('Output:', 'green');
-    log('  Prints compact, wrap-safe benchmark status and pair-evidence cards without wide tables');
-    log('');
-    log('Example:', 'green');
-    log('  npx devlyn-cli benchmark recent');
-    log('  npx devlyn-cli benchmark recent --out-md /tmp/devlyn-recent-benchmark.md');
-    log('');
-    return;
-  }
-  if (mode === 'frontier') {
-    log('Usage:', 'green');
-    log('  npx devlyn-cli benchmark frontier [options]');
-    log('');
-    log('Options:', 'green');
-    log('  --out-json PATH');
-    log('  --out-md PATH');
-    log('  --fixtures-root PATH');
-    log('  --registry PATH');
-    log('  --results-root PATH');
-    log('  --min-pair-margin N  default: 5');
-    log('  --max-pair-solo-wall-ratio N  default: 3');
-    log('  --fail-on-unmeasured');
-    log('');
-    log('Output:', 'green');
-    log('  Prints pair evidence score rows with trigger reasons; --out-md includes a Triggers column');
-    log('');
-    log('Example:', 'green');
-    log('  npx devlyn-cli benchmark frontier --out-md /tmp/devlyn-pair-frontier.md');
-    log('');
-    return;
-  }
-  if (mode === 'audit-headroom') {
-    log('Usage:', 'green');
-    log('  npx devlyn-cli benchmark audit-headroom [options]');
-    log('');
-    log('Options:', 'green');
-    log('  --out-json PATH');
-    log('  --fixtures-root PATH');
-    log('  --registry PATH');
-    log('  --results-root PATH');
-    log('');
-    log('Example:', 'green');
-    log('  npx devlyn-cli benchmark audit-headroom --out-json /tmp/devlyn-headroom-audit.json');
-    log('');
-    return;
-  }
-  if (mode === 'audit') {
-    log('Usage:', 'green');
-    log('  npx devlyn-cli benchmark audit [options]');
-    log('');
-    log('Options:', 'green');
-    log('  --out-dir PATH');
-    log('  --fixtures-root PATH');
-    log('  --registry PATH');
-    log('  --results-root PATH');
-    log('  --min-pair-evidence N  default: 4');
-    log('  --min-pair-margin N  default: 5');
-    log('  --max-pair-solo-wall-ratio N  default: 3');
-    log('  --require-hypothesis-trigger');
-    log('');
-    log('Output:', 'green');
-    log('  Prints frontier score rows plus headroom_rejections=PASS/FAIL, pair_evidence_quality=PASS/FAIL, pair_trigger_reasons=PASS/FAIL, pair_evidence_hypotheses=PASS/FAIL, pair_evidence_hypothesis_triggers=PASS/WARN/FAIL, historical-alias, and hypothesis-trigger gap handoff rows');
-    log('');
-    log('Example:', 'green');
-    log('  npx devlyn-cli benchmark audit --out-dir /tmp/devlyn-benchmark-audit');
-    log('  npx devlyn-cli benchmark audit --require-hypothesis-trigger --out-dir /tmp/devlyn-benchmark-audit-strict');
-    log('');
-    return;
-  }
-  if (mode === 'headroom') {
-    log('Usage:', 'green');
-    log('  npx devlyn-cli benchmark headroom [options] <fixtures...>');
-    log('');
-    log('Options:', 'green');
-    log('  --run-id ID');
-    log('  --bare-max N       default: 60');
-    log('  --solo-max N       default: 80');
-    log('  --min-bare-headroom N  default: 5');
-    log('  --min-solo-headroom N  default: 5');
-    log('  --min-fixtures N   default: 2; use 3 for F16/F23/F25 proof reruns; audit requires 4 passing evidence rows');
-    log('  --allow-rejected-fixtures  active-fixture diagnostics only');
-    log('  --dry-run          validate args/fixtures and print replay command only');
-    log('');
-    log('Example:', 'green');
-    log('  npx devlyn-cli benchmark headroom --min-fixtures 3 F16-cli-quote-tax-rules F23-cli-fulfillment-wave F25-cli-cart-promotion-rules');
-    log('');
-    return;
-  }
-  if (mode === 'pair') {
-    log('Usage:', 'green');
-    log('  npx devlyn-cli benchmark pair [options] <fixtures...>');
-    log('');
-    log('Options:', 'green');
-    log('  --run-id ID');
-    log('  --bare-max N');
-    log('  --solo-max N');
-    log('  --min-bare-headroom N  default: 5');
-    log('  --min-solo-headroom N  default: 5');
-    log('  --min-fixtures N   default: 2; use 3 for F16/F23/F25 proof reruns; audit requires 4 passing evidence rows');
-    log('  --min-pair-margin N  default: 5');
-    log('  --max-pair-solo-wall-ratio N  default: 3');
-    log('  --pair-arm ARM  default: l2_risk_probes; l2_gated is diagnostic');
-    log('  --reuse-calibrated-from RUN_ID');
-    log('  --allow-rejected-fixtures  active-fixture diagnostics only');
-    log('  --dry-run       validate args/fixtures and print replay command only');
-    log('');
-    log('Example:', 'green');
-    log('  npx devlyn-cli benchmark pair --min-fixtures 3 --max-pair-solo-wall-ratio 3 F16-cli-quote-tax-rules F23-cli-fulfillment-wave F25-cli-cart-promotion-rules');
-    log('');
-    return;
-  }
-  showBenchmarkHelp();
-}
-
 // Main
 const args = process.argv.slice(2);
 
@@ -1234,45 +1061,6 @@ switch (command) {
   case 'ls':
     listContents();
     break;
-  case 'benchmark':
-  case 'bench': {
-    const benchmarkScripts = {
-      suite: 'run-suite.sh',
-      recent: 'recent-benchmark-summary.py',
-      frontier: 'pair-candidate-frontier.py',
-      audit: 'audit-pair-evidence.py',
-      'audit-headroom': 'audit-headroom-rejections.py',
-      headroom: 'run-headroom-candidate.sh',
-      pair: 'run-full-pipeline-pair-candidate.sh',
-    };
-    let forwardedArgs = args.slice(1);
-    if (forwardedArgs[0] === '--help' || forwardedArgs[0] === '-h') {
-      showBenchmarkHelp();
-      break;
-    }
-    let benchmarkMode = 'suite';
-    if (forwardedArgs[0] === 'suite' || forwardedArgs[0] === 'recent' || forwardedArgs[0] === 'frontier' || forwardedArgs[0] === 'audit' || forwardedArgs[0] === 'audit-headroom' || forwardedArgs[0] === 'headroom' || forwardedArgs[0] === 'pair') {
-      benchmarkMode = forwardedArgs[0];
-      forwardedArgs = forwardedArgs.slice(1);
-    }
-    if (forwardedArgs[0] === '--help' || forwardedArgs[0] === '-h') {
-      showBenchmarkModeHelp(benchmarkMode);
-      break;
-    }
-    const runnerName = benchmarkScripts[benchmarkMode];
-    const runner = path.join(__dirname, '..', 'benchmark', 'auto-resolve', 'scripts', runnerName);
-    if (!fs.existsSync(runner)) {
-      log('❌ Benchmark suite runner missing — is this a clean devlyn-cli checkout?', 'yellow');
-      log(`   Expected: ${runner}`, 'dim');
-      process.exit(1);
-    }
-    const { spawnSync } = require('child_process');
-    const env = { ...process.env, DEVLYN_BENCHMARK_CLI_SUBCOMMAND: benchmarkMode };
-    const executable = (benchmarkMode === 'recent' || benchmarkMode === 'frontier' || benchmarkMode === 'audit' || benchmarkMode === 'audit-headroom') ? 'python3' : 'bash';
-    const res = spawnSync(executable, [runner, ...forwardedArgs], { stdio: 'inherit', env });
-    process.exit(res.status ?? 1);
-    break;
-  }
   case 'agents': {
     showLogo();
     log('─'.repeat(44), 'dim');