waymark-initlisted

# Waymark init Walk the user through setting up Waymark in this repo **one decision at a time** — do not do it all silently. Ask, wait for the answer, confirm, then act. Once `lang` is known, speak to the user in that language. ## Step 0 — git repo? Run `git rev-parse --show-toplevel`. If it fails, offer to `git init` first (Waymark's enforcement lives in git hooks). ## Step 1 — Ask the MODE first (wait for the answer, then branch) Present the choice and ask which one: - **satellite** (recommended) — Waymark lives in its **own repo** and *references* the code repos it manages (via `repos:`). The code repos are never touched. Best for solo, multi-repo, or when the team hasn't adopted Waymark. - **embedded** — Waymark lives **inside this code repo** (docs-with-code). No `repos:` needed. Best for a single repo that wants code + docs in the same PR. Wait for their choice before continuing. Everything below branches on it. ## Step 2 — Scaffold the status folders Create `waymark/draft/`, `waymark/approved/`, `waymark/in-progress/`, `waymark/done/`, each with a `.gitkeep`. (Both modes use a root `waymark/` folder → `waymark/<status>/`.) ## Step 3 — Build `.waymark.yml` (ask one field at a time, confirm) - `lang` — the team's primary language for generated docs (e.g. `ko`, `en`). Default from the user's locale; confirm. - **satellite only** — for each code repo to manage, ask an `alias` and its `remote`, building `repos: { <alias>: { remote: <host/org/repo> } }`.