adapto-microcopylisted

# adapto:microcopy Manages a project's **micro copy** — the short UI strings (nav, buttons, labels, validation, empty/loading states, footer) stored in Adapto as `key`/`value`/`language` entries. Two modes: - **`init`** — seed a curated, project-aware **starter set** of UI strings with on-brand values (greenfield). - **`extract`** — scan an existing frontend for **hardcoded** UI strings, create entries, and emit a `file:line → key` **replacement guide** (it never rewrites your source). > ⚠️ Micro copy has **no draft state** — entries go **live on create**. So the plan-approval below is the > **only** safety gate (there's no draft-review net like the content skills have). Review the plan carefully. ## When to use - `init`: "seed UI strings", "starter microcopy", "set up my UI text". - `extract`: "extract microcopy", "pull the hardcoded strings from my site into Adapto". ## When not to use - Translating microcopy into another language → `adapto:translate`. - Content (articles / pages / collection items) → `adapto:content-seed`. - Just checking the environment → `adapto:doctor`. ## Inputs - **Mode** — `init` or `extract`. Infer from the request; if ambiguous, ask which. - **Project context** for voice (`.adapto/project.md` cache or `adapto collections get-by-slug _adapto_project_config --json`); absent → neutral defaults. - **Tenant language** (`adapto auth orgs --json`). - **For `extract`:** a scaffolded frontend in the current directory. - **Key convention:** **dot-na