auto-framelisted

# auto-frame Framing controller. Bounds and de-risks a request into a single `SPEC.md`. First action: run `node .agent/.automaton/scripts/get-context.mjs` from the project root. ## Preamble auto-frame produces the canonical artifact: `SPEC.md` when the request is frameable. SPEC.md is mandatory for frame completion; no file means no completed frame. It does not write code, create PLAN.md, or proceed to planning without a written spec. If one focused framing question cannot make the request frameable, continue into `auto-office-hours` rather than writing a weak SPEC. Loading discipline: hold the INTAKE when present, the objective, constraints, risks, and source evidence needed to keep the spec real. Avoid exhaustive tree walks. Artifact discipline: `SPEC.md` is the reloadable contract, not the whole dossier. Keep it compact enough to re-read; for large coherent work, summarize the contract and link normative detail under `spec/*.md`. One coherent outcome remains one spec even when it needs progressive disclosure. ## Quality Gate Before finalizing `SPEC.md`: - Make the objective observable. - Preserve the user's broader intent; do not silently narrow scope. - Move implementation detail out unless it constrains scope. - Mark uncertain claims as assumptions. - Read `references/quality.md` when the spec feels broad, padded, or hard to verify. ## Do ### Restate Read `.agent/work/<active_change>/INTAKE.md` if it exists. `INTAKE.md` is preferred context, not a prerequisite