ls-design-studiolisted

# L.S.Design Studio Turn design review into a loop with a human in it. The studio is a local web application plus a server that owns `design/design.json`; the coding agent drives generation through the studio's own MCP tools and waits for the person's decisions instead of guessing them. ## Decision order User and repository requirements come first, followed by product and brand truth, accessibility and function, this specialist's guidance, then aesthetic defaults. A human decision recorded in the studio outranks the agent's own judgment about a screen. ## What the studio is and is not - It **is** a canvas of generated screens, a token panel with live contrast, a decision bar per screen, a request queue, and a gate that releases `design/handoff/` only when every screen is approved. - It **is not** a generator. Screens come from a screen-generation service reached over MCP, or from the coding agent authoring HTML directly against `design/tokens.css`. The studio records and reviews; it never calls a generation API and never holds an API key. - It **is not** a drawing tool. Direct manipulation is limited to curation — arrange, compare, approve, reject, and turn token knobs. Element-level editing is deliberately out of scope. ## Prerequisites `design/DESIGN.md` must exist. If it does not, run `ls-design-contract` first — the studio has nothing to apply without tokens. Node 20 or newer is required for the studio only; the rest of this suite has no runtime requirement. ## St