feat(aidd-context): bootstrap ends with a project that runs, not a document describing one

[blafourcade]

A new project should end aidd-context:01-bootstrap with a skeleton that runs, not with a document that describes one.

Problem

01-bootstrap produces INSTALL.md and stops. The user reads an architecture they still have to type out by hand. Nothing runs.

Scope

• Thirteen init-* actions: check-prd, gather-needs, choose-stack, init-install-md, then architecture, dependencies, env, database, quality-gate, tests, containers, design-system, ci.
• Every action reads INSTALL.md and names no technology. Architecture only, zero business logic.
• aidd-orchestrator:01-scaffold chains them through to a running bootstrap.

Acceptance criteria

• Bootstrap ends with a project that starts.
• No action hardcodes a stack; each derives it from INSTALL.md.
• Running bootstrap twice is safe.

Implemented in PR #272.