triad-loop-bootstraplisted

# Triad Bootstrap Create the project-control workspace outside product repositories. It is the human/agent record of planning and evidence; it is not an executable workflow engine. Collect only missing essentials: project ID/title, readable PRD source, target repositories with base/project branches and worktrees, measurable success conditions, runnable quality gates, practical-test need, and integration need. 1. Create `<control-repository>/projects/<project-id>/`. 2. Copy `assets/project.yaml` to `project.yaml`; register only declared product repositories, branches, and worktrees. 3. Copy the approved PRD to `artifacts/prd.md`; record source, collection time, snapshot, revision when available, and SHA-256. 4. Copy `assets/loop-template/` to `.loop/`, then create bounded feature cards under `features/` and a complete `feature-plan.md`. 5. Replace every gate placeholder. Gate executors in v1 are only `control-plane`; remove a non-applicable gate with a recorded reason instead of declaring manual or MCP execution. 6. Create `.loop/runtime/assignments/` and record the active adapter metadata in `.loop/runtime/capabilities.json` by running `.triad-runtime/triad-runtime-capabilities.mjs --adapter .triad-runtime/adapter.json --requested-mode <project.control_plane.dispatch_mode>`. Use `auto` when the project does not declare a mode. For Codex, `auto` is explicit dispatch; `async_hook` is an experimental opt-in only. 7. Show the full card division be