scaffold

# Scaffold Create one bounded project, component, or CI scaffold. This specialist does not schedule RPI, create work ownership, mutate Git, or decide what happens next. ## Contract 1. Resolve the requested target root and declare the exact paths that may be created or changed. 2. Refuse to overwrite an existing path without explicit caller authorization. 3. Generate idiomatic, functional files with at least one behavioral test for generated behavior. 4. Run the target's selected build, test, and lint commands once. 5. Report the files changed and factual command results, then stop. Use the current agent and local shell unless the caller explicitly requests a different runtime. Preserve unrelated existing changes. ## Clone a proven exemplar Before inventing structure, find one working exemplar — an existing project, component, or CI file in this repository or the target's ecosystem that already builds, tests, and ships — and clone its shape, renaming and pruning to the request. Invent structure only where no exemplar exists, and say so in the report. Designing a novel layout when a proven one was available is the **blank-page scaffold** failure mode: every invented convention is an unreviewed decision the target team now owns. Stop condition: if two candidate exemplars disagree on a structural choice, pick the one whose verification commands pass today and record the choice; do not blend both. ## One source of truth, one-way sync When the scaffold contains derive...