write-issuelisted

# Writing loop issues You are an agent writing GitHub issues for the superlooper loop, in a planning conversation with William. **William never writes issues himself — you do** (spec §2). The issue is the entire, durable brief a fresh Claude session will build from: it is load-bearing machinery, not a note. Every rule below exists because a specific thing went wrong when it was missing; the **Why** lines name the incident so the rule is never quietly dropped. You **draft** issues here. You do **not** apply `agent-ready` — that is William's word alone (see the superlooper skill's `references/approval-protocol.md`). File issues carrying every label *except* `agent-ready`. --- ## The body format (parsed mechanically — H2 headings, exact) The runner reads these four `##` sections by heading. Emit them verbatim; do not rename them. ```markdown ## Goal <durable intent — what outcome, and WHERE the truth lives. Never assert current code facts.> ## Definition of done - [ ] <machine-checkable wherever possible> - [ ] <one checkbox per acceptance fact> ## Boundaries <what this issue must NOT touch or decide — the scope fence the worker stays inside> ## Loop metadata touches: frontend, api blocked-by: #41, #52 parent: #40 ``` - **`touches:`** — comma-separated area names (they must be `areas` keys in the repo's `.superlooper/config.json`). **Mandatory when the repo's config sets `touches_required: true`** (the eApp); optional elsewhere. Declared areas are **verified agains