bootstraplisted

# Bootstrap The top-level skill owns every user-facing question. The retained scaffolder is a bounded, non-interactive worker invoked only after the answer it needs is durable in the target knowledge base. {% include_shared "parent-owned-interview.md" %} ## Invariants - Keep `metadata.is_workflow: false`; bootstrap may start outside an initialized project. - Known `_TBD_` sections in `charter.md` and `preferences.md` are the only resume state. - Workflow events are telemetry only. Never use them to decide which question or action comes next. - Do not create scratch pads, bootstrap markers, checkpoint comments, context sidecars, relay envelopes, continuation payloads, or generalized scaffold probes. - Use the same parent-owned topology on every platform. Do not use platform-specific interaction tags. - MUST NOT dispatch inside either interview loop. Across one invocation, dispatch at most one PLAN action, one optional REVISE action, and one APPLY action. ## Procedure ### 1. Validate Every Project Name Before Effects Begin from a non-mutating directory inventory. Inspect only the current directory and safe-named direct children when looking for resumable work; do not recurse through arbitrary directories. Validate every supplied, inferred, or recovered project name against `^[a-z0-9][a-z0-9-]*$` before using it as a path segment. Do not trim, sanitize, lowercase, or otherwise rewrite a candidate. Reject separators, `..`, whitespace, globs, punctuation other than `-`, an