setuplisted

Prepare this instance of the forge (POS.1050). Run after cloning the engine, before any other work. Two files in the engine — plus, on the user's word, the git identity configuration outside it; the command runs no git operation. The conversation language is not configured yet on a true first run: speak whatever language the user speaks to you. 1. **`CLAUDE.local.md`** at the engine root. - If it already exists: report briefly what it holds and do not touch it. - Otherwise copy `templates/CLAUDE.local.md` to the root and fill it by elicitation interview, one question at a time: - **Principal** — the role, whose thinking is being forged (the template's placeholder); - **Conversation language** — the language the working conversation runs in (chain artefacts follow their project's language, briefs verbatim, everything else English); - **Git identities** — name and e-mail per git host the user will push to (e.g. github.com, a company host), written to `identities.local.md` beside it from `templates/identities.local.md` (POS.0950). This is the roster from which per-repository identities are proposed at every project creation or import. May be left empty and added later; say so. - Keep the templates' format; both files are gitignored and never committed. - Close the git-identities part with an offer (POS.1050, POS.0950): the global guard `user.useConfigOnly = true` under