ark-autopilotlisted

# /ark-autopilot — Apply the path **Contener · Guiar · Ordenar.** In plain words: contain the write, guide the next step, order leftover mess. This door is **Guiar**: apply leftover design and illegal imports, one small change at a time. Skills never enforce — CLI / hooks / CI do. **When:** the user wants architecture cleaned end-to-end, or leftover design after a map. **Not when:** map only (`/ark-explore`), session 0 / config lying (`/ark-adopt`), or one new file (`/ark-place`). ## Steps 1. Read `arkgate-check --doctor` (do #1). 2. Fix import-rule debt; if leftover design remains, apply **one** small refactor. When doctor JSON has `noDomainFrontend`, that refactor is one pure rule into Domain — not another UI helper. Soft. Silent when Domain already has files. When doctor JSON has `prototypeShortcuts`, that refactor is one file-store move into Persistence, or one admin literal behind Domain / an auth tag. Soft. Silent when those houses are absent or the shortcut is already home. 3. Re-run doctor. Never weaken `ark.config.json`. **This is the apply door.** Invoking it **is** the approval. Run `arkgate-check --doctor` for the next step. ## 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-saf