locklisted

# X2 Lock Copy the approved design artifact down into the repo, verify it is complete, stamp its provenance, and request the lock. The lock is the acceptance contract for the slice; everything the builder ships is held to it. The pilot ran without this step and paid twice: the design system was never imported so the client's tokens were scraped from what happened to be readable inline (MET-04), and the prototype was treated as locked for days before anyone asked for the approval (turn 25). ## The import Pull the complete artifact set from the design project into `design/prototype/` (the canonical home, INV-01): - the prototype source (`<name>.dc.html`), - the **complete** design-system export under `_ds/` (the token css, component css, fonts), - the supporting scripts. Never derive tokens from values readable inline in the prototype source. The pilot did, and silently produced a partial, light-only, placeholder token set with the coverage floor skipped. The client's token source derives from the export on disk, nothing else. ## Done-checks (all must pass before requesting the lock) - The token file on disk defines the full variable set: the more-than-fifty floor is met, not skipped. - Both themes are present: the dark root and the light override. - Fonts resolve by a named path: binaries checked in, or a self-hosted font package pinned under the dependency ledger (the pilot's answer; the design MCP cannot carry binaries through context). - `design/prototype/README.