arkgate 4.6.0 → 4.6.1

package/templates/agent-skills/ark-contract/SKILL.md

@@ -1,40 +1,24 @@
 ---
 name: ark-contract
-description: Safely edit ark.config.json layers/rules and arkrules/* (structure + invariants); land business rules under the dual plane. Validated with strict ark-check. Deep source evidence required.
+description: Shortcut to /ark-adopt (session 0) or /ark-autopilot (later config tighten). Deprecated as a first-class door.
 ---
 
-# /ark-contract — Change the architecture contract (safely)
+# /ark-contract — Shortcut to adopt / autopilot
 
-## Improvement compass (process preflight)
+**Deprecated as a first-class door.** Writing `ark.config.json` / `arkrules/*` is
+**`/ark-adopt`** at session 0 and **`/ark-autopilot`** afterward. Do that job now.
 
-When doctor is available, read `doctor.improvementCompass` (or the human **Improvement compass** section).
-Name 1–3 **residual** lenses in plain language before skill-shopping. Always `notAScore` — never invent
-0–10 scores or Excellent/Good ranks.
+## Autonomy contract
 
-**What the user should feel next:** fewer blocked AI writes, clearer folders, safer domain — then jargon.
-
-**Anti false-done:** empty plan A + residual lenses / design-weak → **Incomplete? yes**. Green edges alone
-are not “architecture finished.”
-
-**AI-easy architecture:** ports over concrete I/O in domain; one concern per module; golden pattern for
-new files; place before write (`/ark-place` / prepare-write).
-
-**Out of scope (honest):** scalability/performance, full app-security tooling (SAST), and full resilience
-patterns are **out-of-scope** lenses — say so; do not invent Ark enforcement for them.
-
-**Contract edits are last resort.** Policy-delta honesty; do not weaken rules to clear compass residual.
+Invoking this leftover name **is** the approval to write an honest config. Do not
+preview-only. Never weaken the architecture config.
 
 ## When / not when
 
-| Use `/ark-contract` when… | Do **not** use it when… |
-|---------------------------|-------------------------|
-| Edit layers/rules/includes/intents with source evidence | Move product code without config change → `/ark-fix` / `/ark-loop` |
-| Concentrated-edge / false-green STOP from other skills | Full map without config edit → `/ark-explore` |
-
-The **one sanctioned way** to change layers/rules/`intentPrefixes`/includes.
-Also used to **land mined business rules** into the executable manifest (`ark.config.json` +
-intent naming that the project-bound `ark_manifest` tool exposes authoritatively).
-
+| Use this leftover name when… | Prefer instead |
+|------------------------------|----------------|
+| Layers / include / ArkRules need an edit | **`/ark-adopt`** (path) or **`/ark-autopilot`** (tighten) |
+| False-green / concentrated edge | **`/ark-adopt`** — write the honest config |
 
 ## Dual engine (mandatory)
 
@@ -45,8 +29,6 @@ intent naming that the project-bound `ark_manifest` tool exposes authoritatively
 
 The CLI is a **sensor**, never the whole job. Claiming done without the exploratory bar for this skill is **incomplete**.
 
-
-
 ## MCP workspace binding (mandatory)
 
 Before any `ark_*` MCP tool, call `ark_identity` with `project.expectedRoot` set to the exact
@@ -58,90 +40,27 @@ restart/retargeting is required. `ark://manifest` never satisfies this preflight
 
 ## Dual plane — layers + ArkRules (mandatory, except /ark-runtime)
 
-ArkGate has **two opt-in planes**. The user chooses which to use; you **always label** findings so they never blur.
-
-| Plane | What it protects | Where it lives | Sensors / tools |
-|-------|------------------|----------------|-----------------|
-| **Layers** (inter-layer) | Who may import whom, capabilities, pure/forbiddenGlobals, peerIsolation | `ark.config.json` → `layers[]`, `rules[]` | graph check, baseline edges, doctor coverage % |
-| **ArkRules** (intra-layer) | Structure inside a layer + domain invariants as data | `arkRules` map + `arkrules/<ExactLayerName>.json` | structure sensors, invariant coverage, `--rules-inventory`, doctor `rulesUnderContract` |
-
-**Rules for every report / answer:**
-1. Prefix each finding or next step with **`[Layer]`** or **`[ArkRules]`** (or a two-column table with those headers).
-2. Never call an import-edge violation an “invariant” or an aggregate sensor a “layer deny.”
-3. Absence of `arkRules` is **valid** — do not force ArkRules unless the user wants them or residual inventory clearly wants a pilot.
-4. Editing `arkrules/*` or promoting modes is **`/ark-contract`**; fixing code under a structure sensor is **`/ark-fix`** / **`/ark-loop`** (judgment, never invent mechanical-safe).
-5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` with `evidence.arkruleId`.
-
-
-### Contract + ArkRules
-- You own **both** `layers/rules` and `arkRules`/`arkrules/*.json`.
-- Report diffs in two blocks: **[Layer] config** and **[ArkRules] files**.
-- Promotion ladder: advisory→enforced only with coverage; demote = hash-ack weakening.
+Label findings **`[Layer]`** vs **`[ArkRules]`**. Absence of `arkRules` is valid.
 
 ## Subagent fan-out (optional, host-dependent)
 
-If the host supports **parallel subagents** and the task splits cleanly (e.g. multiple
-dirs to sample), fan out read-only scouts; otherwise **fall back to sequential**.
-Parent merges and still emits the **### Completion** contract. Never parallel-write
-the same files or weaken the gate.
+If the host supports **parallel subagents**, fan out read-only scouts; otherwise
+**fall back to sequential**. Never weaken the gate.
 
 ## Related onboarding
 
-- **Greenfield:** `/ark-architect` or `ark-check --recommend` / `ark start`.
-- **Brownfield:** `/ark-adopt` — match contract to reality; do not force a starter preset.
-- **Default path:** `ark start` → `/ark-autopilot` → `ark-check --doctor`.
-
-## Anti-wrapper rule (mandatory)
-
-**Forbidden:** editing globs from vibes without reading the directories those globs claim to cover.
-
-**Required:**
-1. Snapshot before using CLI as **sensor**: coverage + check JSON.
-2. **Read source** in dirs you reclassify (sample files).
-3. **“Así te lo re-soluciono”** — exact JSON fields + which files become governed/ungoverned.
-4. After write: `ark-check --strict-config` must be the validation gate (dead pattern noise is advisory; unclassified + real violations still matter).
-
-## What you may edit
-
-- `include` / `exclude`
-- `layers[]` (`name`, `patterns`, `optional`, `forbiddenGlobals`, `intentPrefixes`, layer `exclude`)
-- `rules[]` (from/to/allowed)
-- **`arkRules` map + `arkrules/<Layer>.json`** (ADR 0012/0014) — structure sensors + invariant catalog;
-  promote advisory→enforced only with coverage evidence; demote/delete requires hash-bound policy ack
-- Never: disable the check, delete CI gates, or add blanket `allowed: true` for a bad edge without a facade design
+- **Greenfield:** `/ark-adopt` or `ark-check --recommend` / `ark start`.
+- **Brownfield:** `/ark-adopt` — match config to reality.
 
 ## Steps
 
-1. **Snapshot** — coverage governed%, unclassified samples, current violations.
-2. **Smallest edit** for the user intent:
-   - New layer + neighbor rules
-   - Expand patterns for ungoverned dirs (`suggestions` from coverage)
-   - Facade: public surface patterns more specific than internals
-   - **Business rules → manifiesto:**
-     - Add/adjust `intentPrefixes` (`Domain.`, `Application.`, …)
-     - Point Domain patterns at real pure folders (`**/domain/**`, not bare `**/types.ts`)
-     - Document proposed intent names for the app to register (kernel) or for agents to use
-3. **Impact** — re-run coverage/check; report before/after governed% and violation delta.
-4. **Rollback** if strict fails for reasons other than pre-existing debt the user accepted.
-
-## Operating modes
-
-Contract edits are most common in **Align (Adapt)**. In **Guard (Enforce)**, treat edits as high-risk product decisions.
-
-## Critical handoffs
-
-- After contract is honest but residual violations remain: **STOP — do not continue this skill as complete.** **STOP — bulk residual debt: invoke /ark-loop or /ark-autopilot** instead of ad-hoc multi-file grinding without a plan.
-- New artifact home after reclassify: **STOP — do not continue this skill as complete.** **STOP — new file placement: invoke /ark-place** when the user needs a new artifact home.
-
-## Done
-
-- Diff of `ark.config.json` explained in plain language.
-- **Así te lo re-soluciono en el manifiesto** when intents/Domain were part of the request.
-- Strict check result captured.
+1. If the path is missing or lying → execute **`/ark-adopt`**.
+2. If the path is honest and you are tightening rules → execute **`/ark-autopilot`**.
+3. `ark-check --strict-config`.
 
 ## Completion contract (skill incomplete if missing)
 
-End with **exactly** these headings (markdown `###`):
+Skill incomplete if missing any field below.
 
 ### Completion
 - **Sensor:** commands/tools run
@@ -149,8 +68,5 @@ End with **exactly** these headings (markdown `###`):
 - **Result:** one-line outcome
 - **Planes:** one-line split of residual **[Layer]** vs **[ArkRules]** (or `n/a` if unused)
 - **Compass:** top residual lenses | `n/a`
-- **Handoff:** `/ark-…` / CLI / `none`
+- **Handoff:** `/ark-adopt` / `/ark-autopilot` / `none`
 - **Incomplete?** `no` | `yes — <what is missing>`
-
-If a **STOP** handoff applies and you continued as if done, set **Incomplete?** to `yes`.
-**Skill incomplete if missing** any of the bullets above.

package/templates/agent-skills/ark-coverage/SKILL.md

@@ -5,6 +5,9 @@ description: Ark adoption fitness audit — governed%, gates, baseline honesty,
 
 # /ark-coverage — Ark adoption fitness (not full recon)
 
+**Shortcut.** Fitness numbers only. Full map / leftover design → **`/ark-explore`**.
+Apply → **`/ark-autopilot`**. Session 0 → **`/ark-adopt`**. This is not `/ark-explore`.
+
 You audit **how this repo uses ArkGate** (coverage, gates, baseline, host write path) and
 what adoption gaps remain. Work autonomously. End with a ranked fitness report.
 

package/templates/agent-skills/ark-explain/SKILL.md

@@ -5,6 +5,9 @@ description: Explain this project's architecture in plain language and generate
 
 # /ark-explain — Understand this project's architecture
 
+**Shortcut.** Teach / HTML tour only. Map → **`/ark-explore`**. Apply → **`/ark-autopilot`**.
+Session 0 → **`/ark-adopt`**.
+
 The user wants to understand the architecture, a specific rule, or why the gate blocked them.
 
 ## Improvement compass (process preflight)
@@ -31,7 +34,7 @@ patterns are **out-of-scope** lenses — say so; do not invent Ark enforcement f
 | Use `/ark-explain` when… | Do **not** use it when… |
 |--------------------------|-------------------------|
 | Plain-language tour of layers/rules/report | Decision-grade recon / dual-plan → `/ark-explore` |
-| “Why did the gate block me?” pedagogy | Apply fixes → `/ark-fix` / `/ark-autopilot` |
+| “Why did the gate block me?” pedagogy | Apply fixes → `/ark-autopilot` |
 | Generate / walk HTML showcase report | Fitness numbers only → `/ark-coverage`; brownfield action → `/ark-adopt` |
 Your job is to **teach with this repo's real data** and leave a shareable visual artifact.
 
@@ -68,7 +71,7 @@ ArkGate has **two opt-in planes**. The user chooses which to use; you **always l
 1. Prefix each finding or next step with **`[Layer]`** or **`[ArkRules]`** (or a two-column table with those headers).
 2. Never call an import-edge violation an “invariant” or an aggregate sensor a “layer deny.”
 3. Absence of `arkRules` is **valid** — do not force ArkRules unless the user wants them or residual inventory clearly wants a pilot.
-4. Editing `arkrules/*` or promoting modes is **`/ark-contract`**; fixing code under a structure sensor is **`/ark-fix`** / **`/ark-loop`** (judgment, never invent mechanical-safe).
+4. Editing `arkrules/*` or applying structure fixes is **`/ark-adopt`** / **`/ark-autopilot`** (never invent `mechanical-safe`).
 5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` with `evidence.arkruleId`.
 
 
@@ -186,7 +189,7 @@ when residual signals remain.
    - If a DI/kernel framework border exists, explain public surface vs internals.
 3. **If asked about a specific rule or block**, answer with: the rule, the consequence it
    prevents, and the sanctioned fix (usually a port). If they want it fixed now:
-   **STOP — do not continue this skill as complete.** **STOP — fix requested: invoke /ark-fix.**
+   **STOP — do not continue this skill as complete.** **STOP — fix requested:** invoke `/ark-autopilot`.
    This skill stays read-only.
 4. **If asked "what's a port/adapter/saga…"**, two sentences + this-repo example or conventional path.
 
@@ -206,7 +209,7 @@ when residual signals remain.
 
 ## Related
 
-- Onboarding: `/ark-architect`, `ark-check --recommend`, `docs/enthusiast/README.md`
+- Onboarding: `/ark-adopt` (or leftover `/ark-architect`), `ark-check --recommend`, `docs/enthusiast/README.md`
 - Brownfield: `/ark-adopt`, `docs/brownfield-adoption.md`
 - Autopilot: `/ark-autopilot` after the user understands the contract
 

package/templates/agent-skills/ark-explore/SKILL.md

@@ -1,13 +1,21 @@
 ---
 name: ark-explore
-description: Specialized map skill — decision-grade recon of layers + ArkRules opportunities + dual-plan seed (no apply). Primary post-green door when leftover design work remains. Not the default day-to-day path (use doctor + place/gate; guided apply is /ark-autopilot). CLI is a sensor; you read the tree. No gate bypass.
+description: Map skill — decision-grade recon of layers + ArkRules opportunities + dual-plan seed (no apply). Primary post-green door when leftover design work remains. CLI is a sensor; you read the tree. No gate bypass.
 ---
 
 # /ark-explore — Recon the real project (map only)
 
-**Specialized escape**, not the default curriculum. Use when you need a decision-grade map
-or the post-green Shape door; hand off to `/ark-autopilot` to apply. Day-to-day place + gate
-work does not require this skill.
+## Autonomy contract
+
+Invoking this skill **is** the approval to **map**. Open the real tree. CLI JSON alone is
+incomplete. **Do not write** config or product code (that is `/ark-adopt` / `/ark-autopilot`).
+**CLI budget:** one doctor / coverage; then open ≥12 files across ≥4 dirs; then the map.
+
+**Still never:** weaken the config; invent `mechanical-safe` kinds; claim healthy because
+plan A is empty while leftover design work remains.
+
+Use when you need a decision-grade map or the **Primary post-green door**; hand off to
+`/ark-autopilot` to apply. Day-to-day place + gate work does not require this skill.
 
 You are a **staff engineer doing architecture reconnaissance** on *this* repository.
 Ark’s CLI is a **sensor** (coverage, doctor, plan). **You** open source, entry points,
@@ -58,15 +66,15 @@ If the consumer tree has a **domain glossary**, prefer its terms for layer/slice
 
 | Use `/ark-explore` when… | Do **not** use it when… |
 |--------------------------|-------------------------|
-| Map / “what next?” / residual after ENFORCE | User wants edits applied → `/ark-autopilot` or `/ark-fix` |
+| Map / “what next?” / residual after ENFORCE | User wants edits applied → `/ark-autopilot` |
 | **Primary post-green door:** messy / leftover design work / “clarify for AI” | Skill-shopping coverage or think for the same leftover work |
 | Spaghetti brownfield: patterns concurrent, design-weak under green check | Only “governed% + gates installed?” numbers → `/ark-coverage` |
 | Dual-plan **seed** (A remediation + B pattern bets) without applying | One design trade-off between 2–3 options already mapped → `/ark-think` |
 | Path-correct vs design-correct honesty | Plain-language tour / HTML report → `/ark-explain` |
 
 **Post-green single path:** when doctor `postGreenPath` / ENFORCE · leftover design work is active, **this skill
-(shape-focus / dual-plan seed) is the map half of the one door** — then `/ark-autopilot` only
-to apply B with user OK. Do not send the user to coverage or think as equal first choices.
+(shape-focus / dual-plan seed) is the map half of the one door** — then `/ark-autopilot`
+applies one B pilot. Do not send the user to coverage or think as equal first choices.
 
 ### Status lights (rank residual; not settings)
 
@@ -82,8 +90,8 @@ to apply B with user OK. Do not send the user to coverage or think as equal firs
 
 ## Related onboarding
 
-- **Greenfield / thin tree:** `/ark-architect` or `ark-check --recommend` / `ark start`.
-- **Brownfield action (write contract/baseline):** `/ark-adopt` after the map.
+- **Greenfield / thin tree:** `/ark-adopt` or `ark-check --recommend` / `ark start`.
+- **Brownfield action (write config/baseline):** `/ark-adopt` after the map.
 - **Execute dual plan:** `/ark-autopilot` (explore seeds; autopilot applies A, proposes B).
 - **Default path:** `ark start` → `ark-check --doctor` → `/ark-autopilot` for guided apply; use this skill for map-only or post-green Shape residual.
 
@@ -129,7 +137,7 @@ ArkGate has **two opt-in planes**. The user chooses which to use; you **always l
 1. Prefix each finding or next step with **`[Layer]`** or **`[ArkRules]`** (or a two-column table with those headers).
 2. Never call an import-edge violation an “invariant” or an aggregate sensor a “layer deny.”
 3. Absence of `arkRules` is **valid** — do not force ArkRules unless the user wants them or residual inventory clearly wants a pilot.
-4. Editing `arkrules/*` or promoting modes is **`/ark-contract`**; fixing code under a structure sensor is **`/ark-fix`** / **`/ark-loop`** (judgment, never invent mechanical-safe).
+4. Editing `arkrules/*` or applying structure fixes is **`/ark-adopt`** / **`/ark-autopilot`** — explore does not write (never invent `mechanical-safe`).
 5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` with `evidence.arkruleId`.
 
 
@@ -333,8 +341,8 @@ Empty plan A + design-weak is **not** architecture finished. Plan B is judgment
 | 1. Confirm residual | `designFitness.designWeak` **or** non-empty `patternBets` / `designSmells` | You would claim healthy finished because plan A is empty |
 | 2. Pick **one** pilot | `pilotLoop.nextPilot` (preferred) **or** one ranked B bet with a path scope | Multi-pilot batch / “fix all smells this PR” |
 | 3. Write extraction card | Pilot · Smell · Move · Do not · Success · **Kill-switch** · Next | Missing kill-switch or success signal |
-| 4. User OK | Explicit approval before edit (or stay map-only) | Silent auto-apply of plan B |
-| 5. Apply **only** that pilot | Via `/ark-autopilot` (apply B) or `/ark-fix` (one cluster) | Opening a second pilot before re-doctor |
+| 4. Stay map-only here | Explore does not edit | Silent auto-apply of plan B |
+| 5. Apply **only** that pilot | Via `/ark-autopilot` (one cluster) | Opening a second pilot before re-doctor |
 | 6. Re-doctor | Success = reduced evidence on pilot paths; residual outside pilot may remain | Declaring whole-tree done from one pilot |
 
 **Hard lines (never break):**
@@ -356,7 +364,7 @@ Do not:
   - open a second pilot before re-doctor
 Success: <observable / falsifiable — re-doctor>
 Kill-switch: <stop condition — e.g. if pilot does not clear smell evidence in 1 PR → stop / re-map>
-Next: /ark-autopilot (apply with user ok) | /ark-fix (one cluster) | re-doctor
+Next: /ark-autopilot (apply one pilot) | re-doctor
 ```
 
 When doctor JSON is available, prefer smell `id`s from `designSmells` / `patternBets[].smellId`
@@ -380,10 +388,10 @@ Kinds: `risk` | `false-green` | `debt` | `opportunity` | `shape` | `manifiesto`
 
 5. **Field path summary**.
 6. **Top 3 bets** — first bet = highest leverage residual, even when plan A is empty (design-correct / agent-dx / field honesty — **not** “run loop on zero steps”).
-   On false-green dominant: **STOP — do not continue this skill as complete.** **STOP — false-green: invoke /ark-adopt or /ark-contract before claiming ENFORCE.** Do not claim goal.met / ENFORCE from type-only cleanup while doctor reports `contract-false-green-io-under-application`.
-   On concentrated edge dominant: **STOP — do not continue this skill as complete.** **STOP — concentrated edge: invoke /ark-contract with source evidence** (do not freeze a wrong contract or grind N freezes).
+   On false-green dominant: **STOP — do not continue this skill as complete.** **STOP — false-green:** name the honesty gap; next door is `/ark-adopt` (write). Do not claim goal.met / ENFORCE from type-only cleanup while doctor reports `contract-false-green-io-under-application`.
+   On concentrated edge dominant: **STOP — do not continue this skill as complete.** **STOP — concentrated edge:** name the config smell with source evidence; next door is `/ark-adopt` (do not freeze a wrong config or grind N freezes).
 7. **Dual-plan seed** — required in dual-plan seed / shape-focus (and when §G auto-upgrades); A + B cap 3–5; extraction cards for I/O bets.
-8. **Deterministic residue** — plan completeness, steps, violations, doctor top action. Point to `/ark-loop` / `/ark-fix` **only when A steps exist**; never call a `partial`/`unavailable` plan met, and never pretend loop is the architecture story when a complete goal is already met.
+8. **Deterministic residue** — plan completeness, steps, violations, doctor top action. Point to `/ark-autopilot` **when A steps exist**; never call a `partial`/`unavailable` plan met, and never pretend an empty plan is the architecture story when leftover design remains.
 
 Optional: **Diff vs naive sensor-only read** (what reading the tree changed).
 
@@ -397,7 +405,7 @@ Optional: **Diff vs naive sensor-only read** (what reading the tree changed).
 - When §G fires: phase named, design smells listed with paths, dual-plan B or shape-focus B present.
 - Every Top-3 / B bet has a **success signal**; new-layer bets have a **kill-switch** + pilot.
 - Mode respected: no multi-week roadmap in recon mode; dual-plan seed capped at 3–5 B bets.
-- Clear handoff: `/ark-adopt` | `/ark-contract` | `/ark-autopilot` | `/ark-loop` | `/ark-fix` | CLI | `stop`.
+- Clear handoff: `/ark-adopt` | `/ark-autopilot` | `/ark-place` | CLI | `stop`.
 - No gate weakening; no false ENFORCE claim; no README echo as primary content.
 
 ## Completion contract (skill incomplete if missing)

package/templates/agent-skills/ark-fix/SKILL.md

@@ -1,81 +1,41 @@
 ---
 name: ark-fix
-description: Resolve Ark architecture violations at the root cause — read importers and product context, design ports/adapters/moves/intent alignment. Never weaken the contract. CLI only validates.
+description: Shortcut to /ark-autopilot for a small violation cluster. Deprecated as a first-class door.
 ---
 
-# /ark-fix — Fix architecture violations at the root
+# /ark-fix — Shortcut to /ark-autopilot
 
-You fix violations Ark reports. Prefer structural fixes over silencing the gate.
-**Read the surrounding product code** (callers, package role, feature ownership) — not only
-the two files on the violation edge.
+**Deprecated as a first-class door.** Gate violations and judgment remediations are
+**`/ark-autopilot`**. Do that job now. CLI only validates.
 
-## Improvement compass (process preflight)
+## Autonomy contract
 
-When doctor is available, read `doctor.improvementCompass` (or the human **Improvement compass** section).
-Name 1–3 **residual** lenses in plain language before skill-shopping. Always `notAScore` — never invent
-0–10 scores or Excellent/Good ranks.
+Invoking this leftover name **is** the approval to write the fix. Open importers,
+design the port/move, apply, `ark-check`. Never weaken the config. Never invent
+`mechanical-safe` kinds.
 
-**What the user should feel next:** fewer blocked AI writes, clearer folders, safer domain — then jargon.
-
-**Anti false-done:** empty plan A + residual lenses / design-weak → **Incomplete? yes**. Green edges alone
-are not “architecture finished.”
-
-**AI-easy architecture:** ports over concrete I/O in domain; one concern per module; golden pattern for
-new files; place before write (`/ark-place` / prepare-write).
-
-**Out of scope (honest):** scalability/performance, full app-security tooling (SAST), and full resilience
-patterns are **out-of-scope** lenses — say so; do not invent Ark enforcement for them.
-
-**Name residual lenses** on each cluster (SoC, DIP, coupling, …). Still no weaken-gate to clear a lens.
-
-## Deep modules (process)
+## When / not when
 
-- Prefer fixes that leave a **deep module** at a named **seam** (port in the owning layer; adapter outside).
-- Apply the **deletion test** before extracting a layer “just so tests can mock it.”
-- After a port/inject fix, **test at the public interface** of the seam (match remediation `nextAction` language), not only private internals.
+| Use this leftover name when… | Prefer instead |
+|------------------------------|----------------|
+| One change / small cluster just failed the gate | **`/ark-autopilot`** |
+| Judgment design for a known violation | Session 0 / false-green → **`/ark-adopt`** |
 
-## When / not when
+## Plan B one-pilot checklist (when leftover design, not a single edge)
 
-| Use `/ark-fix` when… | Do **not** use it when… |
-|----------------------|-------------------------|
-| One change / small cluster just failed the gate | Bulk residual / many edges → `/ark-loop` or `/ark-autopilot` |
-| Need a structural fix (port, move, intent rename) | Map residual / pattern Shape plan → `/ark-explore` |
-| Judgment design for a known violation | Contract wrong / false-green → STOP to `/ark-contract` / `/ark-adopt` |
-
-When the fix is really a **Shape** extraction (I/O out of routes, god module split), write an
-**extraction card** before editing — same template as `docs/brownfield-adoption.md`
-§6 and explore §G. Fixed fields (never mechanical-safe, never silent B apply).
-
-### Plan B one-pilot checklist (when Shape residual, not a single edge fix)
-
-Empty plan A + `designWeak` is **not** architecture finished. One pilot only:
-
-1. **Confirm** doctor `designFitness.designWeak` / non-empty `patternBets` (or agent-detected smell).
-2. **One pilot** — prefer `pilotLoop.nextPilot`; never multi-batch concurrent Shape extractions.
-3. **Extraction card** with **Kill-switch** + falsifiable Success (required).
-4. **User OK** before apply — `autoApplyPlanBForbidden` / never mechanical-safe.
-5. **Edit only that pilot scope** — then `ark-check` / re-doctor; residual outside pilot may remain.
-6. **Stop** if kill-switch fires; do not open pilot #2 in the same batch.
-
-```text
-### Extraction card
-Pilot: <one directory or feature path — or pilotLoop.nextPilot.pilotTarget>
-Smell: <doctor designSmells id if present>
-Move: <verbatim relocate / split>
-Do not: rewrite queries; weaken ark.config; invent mechanical-safe kinds; big-bang; multi-pilot batch
-Success: <falsifiable — re-doctor on pilot paths>
-Kill-switch: <stop condition — required>
-Next: re-run ark-check; shrink baseline if applicable
-```
+Empty plan A + leftover design work is **not** architecture finished. One pilot only.
+Write an **extraction card** (`docs/brownfield-adoption.md` §6) — never mechanical-safe,
+never silent B apply. **Kill-switch** required. `multiPilotBatchForbidden` — never
+multi-pilot batch.
 
 ## Dual engine (mandatory)
 
 | Engine | Role |
 |--------|------|
-| **Deterministic** | Violation list, plan kinds, post-edit `ark-check` |
-| **Exploratory** | Why this edge exists in *this* product; better home; manifiesto if the rule is business |
-
+| **Deterministic** | CLI / MCP / contract sensors — exit codes, plan kinds, coverage numbers, install status |
+| **Exploratory** | You open **this** repo's real files and product surface before concluding |
 
+The CLI is a **sensor**, never the whole job. Claiming done without the exploratory bar for this skill is **incomplete**.
 
 ## MCP workspace binding (mandatory)
 
@@ -88,89 +48,25 @@ restart/retargeting is required. `ark://manifest` never satisfies this preflight
 
 ## Dual plane — layers + ArkRules (mandatory, except /ark-runtime)
 
-ArkGate has **two opt-in planes**. The user chooses which to use; you **always label** findings so they never blur.
-
-| Plane | What it protects | Where it lives | Sensors / tools |
-|-------|------------------|----------------|-----------------|
-| **Layers** (inter-layer) | Who may import whom, capabilities, pure/forbiddenGlobals, peerIsolation | `ark.config.json` → `layers[]`, `rules[]` | graph check, baseline edges, doctor coverage % |
-| **ArkRules** (intra-layer) | Structure inside a layer + domain invariants as data | `arkRules` map + `arkrules/<ExactLayerName>.json` | structure sensors, invariant coverage, `--rules-inventory`, doctor `rulesUnderContract` |
-
-**Rules for every report / answer:**
-1. Prefix each finding or next step with **`[Layer]`** or **`[ArkRules]`** (or a two-column table with those headers).
-2. Never call an import-edge violation an “invariant” or an aggregate sensor a “layer deny.”
-3. Absence of `arkRules` is **valid** — do not force ArkRules unless the user wants them or residual inventory clearly wants a pilot.
-4. Editing `arkrules/*` or promoting modes is **`/ark-contract`**; fixing code under a structure sensor is **`/ark-fix`** / **`/ark-loop`** (judgment, never invent mechanical-safe).
-5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` with `evidence.arkruleId`.
-
-
-### Fix + ArkRules
-- Classify each violation: `LAYER_*` / capability → **[Layer]**; `ARKRULE_*` / `INVARIANT_*` → **[ArkRules]**.
-- Structure sensor fixes are judgment (ports, factories, private state) — not mechanical-safe.
+Label findings **`[Layer]`** vs **`[ArkRules]`**. Structure sensor fixes are judgment.
 
 ## Subagent fan-out (optional, host-dependent)
 
-When the user asks to go faster **or** the work naturally splits (multiple packages,
-feature dirs, plan clusters), you **may** dispatch **subagents**:
-
-| Host capability | Behavior |
-|-----------------|----------|
-| **Parallel subagents supported** (e.g. multi-agent / `spawn_subagent` / concurrent Agent tools) | Launch **2–N** agents in **one wave** with **disjoint path scopes**. Prefer **read-only** explore agents for mapping; at most **one writer** unless the host gives isolated worktrees. Parent merges findings, then runs `ark-check` once. |
-| **Not supported** (single agent only) | **Fall back to sequential** — same checklist, one cluster/step at a time. Never claim parallel work you did not run. |
-
-**Rules:**
-1. Give each subagent a **tight brief**: paths in scope, sensor commands allowed, deliverable shape (paths opened + findings JSON or bullets).
-2. **No shared mutable files** across parallel writers.
-3. STOP handoffs and dual-engine rules still apply in every agent.
-4. Parent owns the **### Completion** block (union of **Opened**, single **Handoff**).
-5. Do **not** use subagents to weaken the gate or invent `mechanical-safe` kinds.
+If the host supports **parallel subagents**, fan out read-only scouts; otherwise
+**fall back to sequential**. Never weaken the gate.
 
 ## Related onboarding
 
-- **Greenfield:** `/ark-architect` or `ark-check --recommend` / `ark start`.
-- **Brownfield:** `/ark-adopt` — match contract to reality; do not force a starter preset.
-- **Map first:** `/ark-explore` when the violation is one of many structural smells.
-- **peerIsolation / cross-slice:** always **judgment** — extract to shared, events/ports, or redesign ownership. Never auto-apply cross-feature or cross-context moves.
-- **`vertical-slice` ownership:** feature code stays under `src/features/<slice>/…` (no sibling-slice imports); shared primitives in `src/shared/`; infra in `src/lib/`; shell in `src/app/`. Cross-feature edges are peerIsolation — extract shared or use events/ports.
-- **`ddd-bounded-contexts` ownership:** code under `src/contexts/<context>/{domain,application,infrastructure,presentation}/`; shared kernel only under `src/shared/kernel/`. Cross-context imports (same or cross technical layer) are peerIsolation — integrate via application APIs/events, not peer technical layers.
-- **Default path:** `ark start` → `/ark-autopilot` → `ark-check --doctor`.
+- **Greenfield:** `/ark-adopt` or `ark-check --recommend` / `ark start`.
+- **Brownfield:** `/ark-adopt`.
 
-## Anti-wrapper rule (mandatory)
+## Steps
 
-**Forbidden:** only listing violations from JSON without reading importers/targets.
-
-**Required:**
-1. Run `ark-check` as **sensor** (and `--plan --json` if multi-step) — CLI validates; you remediate.
-2. **Read** each violated file and its import target (plus callers that explain product role).
-   If the wall is a concentrated contract smell: **STOP — do not continue this skill as complete.** **STOP — concentrated edge: invoke /ark-contract with source evidence** (do not freeze a wrong contract or grind N freezes).
-   If false-green cores: **STOP — do not continue this skill as complete.** **STOP — false-green: invoke /ark-adopt or /ark-contract before claiming ENFORCE.** Do not claim goal.met / ENFORCE from type-only cleanup while doctor reports `contract-false-green-io-under-application`.
-   If many residuals: **STOP — do not continue this skill as complete.** **STOP — bulk residual debt: invoke /ark-loop or /ark-autopilot** instead of ad-hoc multi-file grinding without a plan.
-3. **“Así te lo re-soluciono”** — concrete change before editing.
-4. After edits: `ark-check --strict-config` (and baseline if configured).
-
-## Common fix patterns
-
-| Symptom | Fix |
-|---------|-----|
-| App → Presentation type-only | Extract type to application/core; re-export from UI |
-| App → Presentation value (UI in core) | Move component wrappers to presentation |
-| Domain → outer layer | Port/interface in Domain; adapter outside; or relocate false Domain file (`**/types.ts` trap) |
-| Intent prefix mismatch | Rename intent to layer’s `intentPrefixes` or fix prefix in config via `/ark-contract` |
-| Forbidden global in Domain | Inject a port (Clock, Id, Http) — don’t allow `Date.now` in Domain |
-| Concentrated edge wall | Stop grinding; `/ark-contract` facade/surface split |
-
-## Manifiesto
-
-If the “fix” is really a missing business intent or Domain home for a rule:
-
-- Propose intent name + layer placement.
-- Register / place code so `ark_manifest` / config can enforce it.
-- Do not only delete the import.
-
-## Rules
-
-- No `ark-*-disable`, no allowing a bad edge “to finish”, no baselining a **new** violation you introduced.
-- Prefer mechanical-safe kinds when the plan tags them; otherwise design judgment carefully.
-- Code only — no DB migrations unless user asked.
+1. Sensor: `ark-check` / `--plan --json`.
+2. If false-green or concentrated edge: **STOP — do not continue this skill as complete.**
+   **STOP — false-green:** / **STOP — concentrated edge:** execute **`/ark-adopt`** in this turn.
+3. Otherwise execute **`/ark-autopilot`** for the cluster (extraction card if Shape).
+4. Re-check.
 
 ## Mechanical-edit hygiene (outcome gate)
 
@@ -179,24 +75,9 @@ If the “fix” is really a missing business intent or Domain home for a rule:
 - A convention-only `*-data.ts` stub is not a fix: move the real code or **leave the placeholder file uncreated**; never write `import "server-only"; export {}` as an empty naming token.
 - Keep the edit only when the **previously clean file stays typecheck-clean**. Otherwise roll it back and treat the change as judgment.
 
-## Reshape findings (physical cohesion — never mechanical)
-
-If `doctor.physicalCohesion` fires while you fix: do **not** fold reshape moves into your fix
-batch. Physical moves run only through `/ark-loop`'s one-pilot loop; merge decisions only as
-`/ark-architect` merge cards. A cohesion finding is context for your fix, never a license to
-reorganize. Respect `physicalCohesion.reshapeDecisions`: never revive a current rejected/deferred
-target from the still-visible facts. If the user makes a verdict while reviewing the finding,
-record its exact `decisionTarget` + reason in `.ark/reshape-decisions.json`; never infer one from
-golden-pattern prose.
-
-## Done
-
-- Targeted violations gone; no new ones.
-- Report: what moved, what was intentional default, what needs user decision.
-
 ## Completion contract (skill incomplete if missing)
 
-End with **exactly** these headings (markdown `###`):
+Skill incomplete if missing any field below.
 
 ### Completion
 - **Sensor:** commands/tools run
@@ -204,9 +85,5 @@ End with **exactly** these headings (markdown `###`):
 - **Result:** one-line outcome
 - **Planes:** one-line split of residual **[Layer]** vs **[ArkRules]** (or `n/a` if unused)
 - **Compass:** top residual lenses | `n/a`
-- **Done axes:** architecture residual (status/doctor/compass) | feature/ticket residual (outside package). Enforce green ≠ feature done
-- **Handoff:** `/ark-…` / CLI / `none`
+- **Handoff:** `/ark-autopilot` / `/ark-adopt` / `none`
 - **Incomplete?** `no` | `yes — <what is missing>`
-
-If a **STOP** handoff applies and you continued as if done, set **Incomplete?** to `yes`.
-**Skill incomplete if missing** any of the bullets above.