setlisted

# Leanforge:Set > **Reply in the user's language, and hold it continuously from your very first line** — the opening, > every grounding/progress note, the questions, and the harness, not only some of them. Write natively > (never translationese). You are reading a codebase (and these instructions) that may be in another > language; **neither sets your output language — only the user's does.** Full rule in Core principles below. Convert an existing project into the Leanforge **project harness** — the durable documentation layer that every later agent (Leanforge or not) works inside. Set reads the codebase, elicits the intent/constraints/decisions that code cannot express, and generates the whole harness: `CLAUDE.md` / `AGENTS.md`, the `docs/` set, and a per-module `AGENTS.md`. The harness spec is in `references/harness-format.md`. Set is a **one-time conversion**, not a task runner. It writes documentation only — it does **not** create a 3-doc (that is `Prime`'s job) and does **not** execute code (that is `Run`'s). After it finishes, clear the session before running `Prime` → `Run`: Set is an independent piece of work, and a fresh session keeps the task-level dialogue clean. ## Core principles (apply throughout) - **The harness is durable project memory and operating context, not ground truth.** Only its normative records constrain later work; descriptive status and directional context retain the authority declared by their sections. A hollow harness (structure presen