arkgate 4.5.7 → 4.6.1

package/templates/skills/ark-architect.md

@@ -1,43 +1,24 @@
 ---
 name: ark-architect
-description: Choose the application shape, adopt phase-1 layers, scaffold directories, and verify honestly — for enthusiasts before codegen. Autonomous.
+description: Shortcut to /ark-adopt for greenfield shape. Deprecated as a first-class door. Do adopt’s job.
 ---
 
-# /ark-architect — Choose your application shape and adopt Ark
+# /ark-architect — Shortcut to /ark-adopt
 
-## Improvement compass (process preflight)
+**Deprecated as a first-class door.** Session 0 is **`/ark-adopt`**. Do that job now
+(greenfield scaffold via `ark-check --recommend` / MCP `ark_recommend` after `ark_identity`).
 
-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.
-
-**Greenfield that is AI-easy day one:** golden norm + thin layers so the next agent turn stays ordered.
+Invoking this skill **is** the approval to mark the path. Write `ark.config.json` and
+phase-1 dirs in this turn. Then `ark-check`.
 
 ## When / not when
 
-| Use `/ark-architect` when… | Do **not** use it when… |
-|----------------------------|-------------------------|
-| Greenfield / thin tree; pick shape + phase-1 layers | Existing spaghetti brownfield → `/ark-adopt` (+ `/ark-explore` first if map missing) |
-| Enthusiast before heavy codegen | Enforcement residual on mature tree → `/ark-autopilot` |
-
-The user is building something new or early in Ark adoption. They may not know
-layered architecture jargon. Your job: translate **what they want to build**
-(application shape, not framework name) into an Ark preset, a phase-1 layer plan,
-conventional directories, and a passing honest check — without weakening the gate.
-
-Commands below are written as `ark-check` / `ark`; run each through the project's
-package manager (`pnpm exec`, `yarn`, `npx`) — match the lockfile.
+| Use this leftover name when… | Prefer instead |
+|------------------------------|----------------|
+| Muscle memory / old docs say architect | **`/ark-adopt`** (greenfield + brownfield) |
+| Empty tree needs a shape | Same — adopt writes the recommend result |
 
 ## Dual engine (mandatory)
 
@@ -48,8 +29,6 @@ package manager (`pnpm exec`, `yarn`, `npx`) — match the lockfile.
 
 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
@@ -59,128 +38,31 @@ retain `projectIdentity.projectId`, then pass both `expectedRoot` and `expectedP
 uncertain, do not consume MCP analysis: use the workspace-local CLI and report that MCP
 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`.
+Then call **`ark_recommend`** with the same bound `project` envelope (or `ark-check --recommend`).
 
+## Dual plane — layers + ArkRules (mandatory, except /ark-runtime)
 
-### Architect + ArkRules
-- Preset/init should emit lean `arkRules` + templates for phase-1 layers (exact names).
-- Explain to the user: layers = boundaries; arkrules = habits inside Domain/App/adapters (opt-in, start advisory).
+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.
 
-## Relationship to other skills
+## Related onboarding
 
-| Skill | When |
-|-------|------|
-| **/ark-architect** | **Before** — greenfield or fresh config; pick shape + phase 1 |
-| /ark-adopt | **After** — messy existing repo |
-| /ark-contract | **During** — evolve config safely |
-| /ark-place | **During** — one new file |
-| /ark-explain | **After** — understand what exists |
+- **Greenfield:** this shortcut → **`/ark-adopt`** + `ark-check --recommend` / `ark start`.
+- **Brownfield:** `/ark-adopt` — do not force a starter preset.
 
 ## Steps
 
-1. **Bind and detect the shape** — complete the mandatory `ark_identity` preflight first, then
-   call MCP tool **`ark_recommend`** with the bound `project` envelope (or run the workspace-local
-   `ark-check --recommend --json`). Never use an unverified recommendation. Read `archetype`, `preset`, `confidence`,
-   `adoptInOrder.phase1`, `analogy`, `why`, `evidence`, and `requiresConfirmation`.
-   Ask at most **two** questions only if `requiresConfirmation` is true (or for compatibility
-   with older ArkGate output, `confidence < 0.5`):
-   - "Will this app save data between sessions?"
-   - "Is this one app or several in one repository?"
-
-2. **Present in plain English** — name the application shape (e.g. "product with
-   UI and stored data"), not the framework. One analogy. List **phase-1 layers only**.
-
-3. **Map to Ark** — if `ark.config.json` is missing, run
-   `ark init --archetype <archetype> --yes` (maps playbook id → preset + gates),
-   or `ark-check --apply-policy-pack enthusiast-<preset>` for the enthusiast variant.
-   Optional team record: `ark-check --recommend --write-plan` → `ark-adoption-plan.json`.
-   If a config already exists, use `/ark-contract` to align it — do not regenerate
-   unasked. On a messy brownfield tree: **STOP — do not continue this skill as complete.** Invoke **/ark-adopt** instead of forcing greenfield shape.
-
-4. **Scaffold phase 1** — create conventional directories from the preset/playbook
-   (`src/domain`, `src/application`, …). Add a one-line README per folder explaining
-   what belongs there. Match the nearest sibling file style if code already exists.
-   Flat layouts (`src/` + `lib/` + `api/` at the repo root) are common in Vite and
-   serverless projects — use `/ark-contract` to map them to layers instead of forcing
-   everything under `src/**/domain/**` only.
-
-5. **Install gates** when the user uses AI coding tools and gates are missing:
-   `ark-check --install-agent-gates`.
-
-6. **Verify honestly** — run `ark-check --doctor` and `ark-check --coverage --json`.
-   Report `governed.percent`. Say explicitly what is **not** governed yet
-   (ungoverned directories, empty layers).
-
-7. **Deliver to the user**
-   - ASCII diagram (≤3 boxes for phase 1, inner → outer)
-   - Table: "when you build X, put it in Y"
-   - Three rules the agent must not break (no domain→database imports, no raw
-     `publish()`, no weakening `ark.config.json` to pass)
-   - Optional book refs from `books` in the recommendation JSON under "go deeper"
-   - **Gallery starter** — point the user at the matching clonable example:
-
-     | Archetype | Example directory |
-     |-----------|-------------------|
-     | `crud-product` | `examples/crud-product-starter/` |
-     | `api-backend` | `examples/api-backend-starter/` |
-     | `worker-pipeline` | `examples/worker-pipeline-starter/` |
-     | `multi-app-workspace` | `examples/multi-app-workspace-starter/` |
-     | `vertical-slice-product` | `examples/vertical-slice-starter/` |
-     | `ddd-bounded-contexts` | `examples/ddd-context-starter/` |
-
-     Say they can copy that folder as a baseline (`npm install && npm run check`).
-     For a runnable API with break exercises, mention `examples/hexagonal-order-api/`.
-     Full enthusiast track: `docs/enthusiast/README.md`.
-
-## Operating rules
-
-- Never weaken `ark.config.json`, the baseline, CI, or agent settings to pass.
-- Never invent layers outside the 11-layer profile or named presets
-  (`hexagonal`, `layered`, `feature-sliced`, `monorepo`, `ui-surface`,
-  `vertical-slice`, `ddd-bounded-contexts`).
-- Flag unrecognized dirs (`utils/`, `lib/`) — user must classify via `/ark-contract`.
-- Default to smallest viable phase 1; unlock phase 2 only when the user describes need.
-- All user-facing copy is **English**.
-
-## Merge cards (physical cohesion reshape — judgment only)
-
-When `doctor.physicalCohesion` reports a mirrored concept and the user asks whether files
-should be **merged**, treat it as domain modeling, never deduplication (field fact: zero
-structural clones among 123 same-concept files). Produce a **merge card** per candidate group:
-which files, the domain concept they express, 2–3 shapes the merged module could take, and what
-each shape costs — **no default action, no auto-merge, never a codemod**. Physical **moves**
-belong to `/ark-loop`'s pilot loop; your job here is the judgment about what the concept IS.
-
-## Verify and report
-
-End with `ark-check --root . --config ark.config.json --strict-config` when the
-tree is ready. Report: archetype + preset, directories created, governed %, and
-the next command if anything remains ungoverned.
+1. Bind MCP (`ark_identity` then `ark_recommend`) or run `ark-check --recommend`.
+2. Execute **`/ark-adopt`** autonomy: write the config, dirs, optional advisory ArkRules, gates.
+3. `ark-check --strict-config`. Handoff `/ark-place` for new files.
 
 ## Completion contract (skill incomplete if missing)
 
-End with **exactly** these headings (markdown `###`):
+Skill incomplete if missing any field below.
 
 ### Completion
 - **Sensor:** commands/tools run
@@ -188,8 +70,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-place` / `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/skills/ark-autopilot.md

@@ -1,17 +1,27 @@
 ---
 name: ark-autopilot
-description: Guided end-to-end path for layers and opt-in ArkRules — doctor next action when unsure. Explore first; dual plan A (edges) + B (shape); mechanical-safe only by default; B with user OK, one pilot at a time. Empty plan A is not healthy if design-weak. CLI is a sensor; you read and remediate files.
+description: Apply Ark end-to-end — explore first; dual plan A (edges) + B (shape); write mechanical-safe and judgment in this turn; one Shape refactor. Empty plan A is not healthy if leftover design remains. CLI is a sensor; you edit files.
 ---
 
-# /ark-autopilot — Guided end-to-end architecture path
+# /ark-autopilot — Apply the path
 
-**This is the full guided co-pilot** after the compact router. Prefer it when the user wants
-architecture cleaned end-to-end, not when they only need a map (`/ark-explore`) or a single
-edge fix (`/ark-fix`). Doctor remains the control plane: re-check status after each major step.
+**This is the apply door.** Invoking it **is** the approval. Prefer it when the user wants
+architecture cleaned end-to-end, not when they only need a map (`/ark-explore`). Doctor
+remains the control plane: re-check status after each major step.
 
-Composes **explore → sensors → dual plan → loop**. Safe default: auto-apply only
-`mechanical-safe`; when the user says full apply / apply everything, also execute **judgment**
-fixes you design from reading source (still validate with ark-check, never weaken the gate).
+## Autonomy contract
+
+The CLI is a **sensor and gate**. **CLI budget:** one doctor / `--plan`; open files; **write**;
+re-check. Forbidden as the result: “4 safe / 4 judgment — approve?”, dumping `--plan` JSON,
+or `STOP — invoke /ark-fix` / `/ark-loop` / `/ark-contract`. Do that work **here**.
+
+Apply plan A (`mechanical-safe` **and** judgment). If leftover design work remains, apply
+**one** small refactor this turn, then re-doctor. Never batch every Shape bet.
+
+Composes **explore → sensors → dual plan → write**. Validate with ark-check; never weaken the gate.
+**Team lock:** do not edit `ark.config.json`, `arkrules/*`, or `.ark-baseline.json` in this
+turn unless the user invoked a steward contract session. Feature diffs use
+`ark-check --changed --base <merge-ref>`. Growing the baseline is steward-only.
 
 **Not a plan grinder.** Empty `--plan` does **not** mean “architecture is healthy” without
 the explore pass and dual-plan section B (pattern / Shape bets).
@@ -33,25 +43,25 @@ 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.
 
-**Guided vibe path:** phase 0 = doctor + compass residual. Shape only with user OK. Never script “done” while residual lenses remain.
+**Guided vibe path:** phase 0 = doctor + compass residual. Shape: one refactor this turn (invoke = OK). Never script “done” while residual lenses remain.
 
 ## When / not when
 
 | Use `/ark-autopilot` when… | Do **not** use it when… |
 |----------------------------|-------------------------|
 | “Make architecture sound” end-to-end | Map only, no apply → `/ark-explore` |
-| Brownfield or greenfield with apply | Only fitness numbers → `/ark-coverage` |
-| User wants A + B planned and A executed | Single edge fix → `/ark-fix`; plan A only → `/ark-loop` |
-| **Apply half of post-green Shape path** (after explore map / when user wants full apply) | Skipping explore when doctor primary is Shape map-first |
-| Spaghetti under ENFORCE: Shape work with user ok on B | Contract false-green first → `/ark-adopt` / `/ark-contract` STOP paths |
+| Brownfield or greenfield with apply | Session 0 / config lying → `/ark-adopt` first, then return |
+| User wants A + B planned and **applied** | New file only → `/ark-place` |
+| **Apply** leftover design (one Shape refactor) | User said map only |
+| Spaghetti under ENFORCE: Shape work (invoke = apply one pilot) | — |
 
-**Post-green door:** doctor’s single door is `/ark-explore` shape-focus → dual-plan B, **then** this skill only
-to apply B with OK. Prefer that order when `postGreenPath` / design-weak is the primary residual.
+**Post-green door:** `/ark-explore` shape-focus → dual-plan B, **then this skill applies one
+pilot**. Prefer that order when `postGreenPath` / leftover design work is the primary residual.
 
 ## Related onboarding
 
-- **Greenfield:** `/ark-architect` or `ark-check --recommend` / `ark start`.
-- **Brownfield:** `/ark-adopt` — match contract to reality; do not force a starter preset.
+- **Greenfield:** `/ark-adopt` or `ark-check --recommend` / `ark start`.
+- **Brownfield:** `/ark-adopt` — match config to reality; do not force a starter preset.
 - **Deep map only:** `/ark-explore` — full recon / dual-plan seed without applying.
 - **Adoption fitness only:** `/ark-coverage` — governed% + capability gaps (not pattern dual-plan).
 - **Default path:** `ark start` → `ark-check --doctor` → **`/ark-autopilot`** (this skill) for guided work.
@@ -73,8 +83,8 @@ decision-grade explore pass **and** without opening violating files.
 4. **Open every file** in plan A `steps[]` (and `target` if present) before classifying a fix.
 5. **“Así te lo re-soluciono”** for each A cluster and each B pattern bet.
 6. Apply A → re-run ark-check → rollback on regression. **Never auto-apply B** as mechanical-safe.
-7. **One-pilot loop for B:** when design-weak, take **`pilotLoop.nextPilot`** (one extraction card)
-   → apply **only** that pilot with user OK → **re-doctor**. Never multi-pilot batch B; residual
+7. **One-pilot loop for B:** when leftover design / design-weak, take **`pilotLoop.nextPilot`** (one extraction card)
+   → apply **only** that pilot **in this turn** → **re-doctor**. Never multi-pilot batch B; residual
    outside the pilot may remain and must not be called “healthy finished.”
 8. **Reshape decision memory:** read `doctor.physicalCohesion.reshapeDecisions` before acting on
    mirror facts. Outcome first: a current rejected/deferred verdict means “intentional/deferred
@@ -106,7 +116,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 promoting modes and fixing structure sensors is **this skill** (judgment, never invent `mechanical-safe`).
 5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` with `evidence.arkruleId`.
 
 
@@ -150,7 +160,7 @@ Include explore **§G** when spaghetti / design-weak signals fire.
 5. **Agent/gate reality** — installed hooks vs install templates (e.g. `--hook` vs `--hook-repair`); MCP; CI gate present.
 6. **Coupling** — fan-in / exports / importers for hotspots (LOC alone is a hint).
 7. **False-green soft block** — doctor/coverage: empty Domain/Persistence while Application owns I/O (`airtable`, `supabase`, `prisma`, `drizzle`, `repositories`, …). Doctor gap id: `contract-false-green-io-under-application`. If so:
-   **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`.
+   **STOP — do not continue this skill as complete.** **STOP — false-green:** fix the architecture config **in this turn** (same job as `/ark-adopt`) before claiming ENFORCE. Do not claim goal.met / ENFORCE from type-only cleanup while doctor reports `contract-false-green-io-under-application`.
 8. **Seed dual plan B** — 2–5 pattern / Shape bets ranked (impact × effort × enforceability). Each B row needs pilot + success signal; I/O bets need an **extraction card** (explore §G).
 
 Min bar: **≥12 source files** across **≥4 meaningful directories** (not only files in `steps[]`).  
@@ -160,16 +170,16 @@ Standalone long report: `/ark-explore`. Adoption fitness only: `/ark-coverage`.
 
 | Section | Source | Question | Auto-apply? |
 |---------|--------|----------|-------------|
-| **A. Remediation** | `--plan --json` + opened step files | What must change so the **gate** is honest? | Only `mechanical-safe` by default |
+| **A. Remediation** | `--plan --json` + opened step files | What must change so the **gate** is honest? | Write `mechanical-safe` **and** judgment |
 | **B. Pattern / Shape** | Explore §B/§G (not coverage alone) | What **design** must improve even if A is empty? | **Never** as mechanical-safe |
 
 **Section A** — group by edge; treat `peerIsolation` / cross-slice as **judgment**.  
 **Section B** examples: choose golden pattern + pilot migrate-on-touch, peerIsolation, move rules out of UI, write-path repair, split god modules, Domain placement / intents, facade SQL → port/adapter (extraction card). Cap **3–5** B rows. Each row: evidence path + **así te lo re-soluciono** + next skill/command + **success signal** + **pilot** (+ kill-switch if new layer).
 
-B does **not** count as “architecture healthy finished.” Report B as `proposed | deferred | applied-with-user-ok`.  
+B does **not** count as “architecture healthy finished.” Report B as `proposed | deferred | applied`.  
 When A is empty and B is non-empty: status is **`goal.met on edges · Shape residual open`** — never “done” without listing B.
-Prefer CLI `patternBets[]` / `designSmells[]` when present; apply B only with explicit user ok using
-**extraction cards** (`docs/brownfield-adoption.md` §6) — never mechanical-safe, never silent.
+Prefer CLI `patternBets[]` / `designSmells[]` when present; apply **one** B pilot this turn using
+**extraction cards** (`docs/brownfield-adoption.md` §6) — never mechanical-safe, never silent, never multi-pilot.
 If B will take multiple PRs, offer (do not require) persisting a short Shape plan under the
 repo so the next agent session continues the same pilot — still never auto-apply B.
 
@@ -190,7 +200,7 @@ Status lights from doctor — not settings you choose. Rank residual honestly:
 | **Suggest** | Thin/new tree; contract not control plane | Finish `ark start` → re-doctor; do not skill-shop |
 | **Adapt** | Contract/tree disagree or debt open | Explore + adopt/loop/contract; do not claim guarded |
 | **Enforce** | Honest coverage + clean checked **edges** | Confirm gates + CI; emit dual-plan B only if residual found |
-| **Enforce · design-weak** | Edges clean; design smells remain | **Primary Shape door:** explore shape-focus → dual-plan **B** → apply **one** pilot with user OK. Empty plan A ≠ done. Never mechanical-safe B. False-done forbidden. |
+| **Enforce · leftover design work** | Imports clean; design still messy | **Primary Shape door:** explore shape-focus → dual-plan **B** → apply **one** small refactor. Empty plan A ≠ done. Never mechanical-safe B. False-done forbidden. |
 
 - **Setup (Suggest):** no config → `ark start` (start freezes origin after config, before gates).
 - **Align (Adapt):** open debt, low honesty, or false-green → explore + adopt/loop; do not claim “guarded”.
@@ -206,12 +216,12 @@ Status lights from doctor — not settings you choose. Rank residual honestly:
 3. **Sensors** — `--plan --json`, doctor/coverage as needed.
 4. **Emit dual plan** — A from plan steps (files opened); B from explore (3–5 bets).
 5. **Concentrated edge?** — if one edge dominates A:
-   **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).
+   **STOP — do not continue this skill as complete.** **STOP — concentrated edge:** rewrite `ark.config.json` **in this turn** with source evidence (do not freeze a wrong config or grind N freezes).
 6. **Worktree preferred** — discardable git worktree when possible.
 7. **Mechanical-safe (A only)** — kinds from `/ark-loop` table; one step, validate, rollback.
-8. **Judgment (A)** — default: propose with full “así te lo re-soluciono”. If user authorized full apply: implement, validate, rollback on fail.
-9. **Pattern bets (B)** — propose; apply only with explicit user go + correct skill (`/ark-contract`, refactor, install gates, etc.). Never weaken the gate to clear B.
-10. **Manifiesto** — loose business rules → Domain placement + `intentPrefixes` / intents via `/ark-contract` discipline.
+8. **Judgment (A)** — implement with full “así te lo re-soluciono”; validate; rollback on fail.
+9. **Pattern bets (B)** — apply **one** extraction-card pilot this turn; leave the rest queued. Never weaken the gate to clear B.
+10. **Manifiesto** — loose business rules → Domain placement + `intentPrefixes` / intents; write config here if the path is still dishonest.
 11. **Final report** — re-`--report`; evolution vs origin; A applied vs open; B proposed/deferred; gates on.
 12. **Strict check** — `ark-check --strict-config` (dead preset globs are advisory; real violations still fail).
 13. **Core ratchet (when green)** — if plan `goal.met` and doctor still **ADAPT** only because

package/templates/skills/ark-contract.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/skills/ark-coverage.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/skills/ark-explain.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