bootstraplisted

Turns the stack-agnostic template into a project that verifies itself. The hooks and skills only start earning their keep once `verify.sh` runs real commands — this skill wires that up and proves it. ## Hold in mind 1. Hooks only help if wired to real commands — placeholder checks are worse than none because they teach false confidence. 2. `verify.sh quick` runs after every single edit: it must finish in well under 10 seconds or it will be resented and disabled. 3. `verify.sh full` is the definition of "healthy": if it passes while the project is broken, every loop built on it is lying. 4. CLAUDE.md's concept budget applies to the facts you write: stack, commands, run instructions — one line each. ## Steps 1. Detect the stack: look for manifests (`package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`, `Gemfile`, `mix.exs`, `pom.xml`, `build.gradle`, `*.csproj`). Use the argument as a hint. If nothing is found (fresh project), interview the user: language, package manager, test framework, formatter/linter. Scaffold the minimal stack files they choose. 2. Wire `scripts/verify.sh`: - Replace the block between `# janus:bootstrap:quick:start` and `:end` with per-file checks keyed on file extension (format check, lint, typecheck of the changed file). Budget: <10s. Keep the template's `*.sh`/`*.json` arms — hook scripts exist in every child and deserve the same loop. - Replace the block between `# janus:bootstrap:full:start` and `:end` with the real suite: lint all, type