work-initlisted

# Work / 1. Init Create the smallest useful project foundation through a short guided flow. Read [../QUALITY.md](../QUALITY.md) first. Keep the scaffold focused, reliable at real boundaries, and free of compatibility scaffolding. Define proof before adding surface area. ## Ask first Ask no more than three setup questions at a time, progressively: 1. Project name, destination, type, language/runtime, target platform, and minimum version. 2. Required packages, services, storage, authentication, and integrations. 3. Preferred test, lint, format, build, and run commands. Use sensible defaults when the answer is discoverable from the workspace. Do not add speculative packages or infrastructure. Before writing, state the exact foundation goal, source of truth, what “ready” means, and what does not count (for example, an empty scaffold that has never built or run). Keep the first setup intentionally narrow; defer product features until the foundation proves itself. Grow in working layers: start with the smallest end-to-end version and add each capability only after the product already works. Never trade a working foundation for unfinished complexity. If setup includes tests, inspect the implementation, existing tests, public APIs, and actual user flows before writing them. State the four-line meaningful test plan from [QUALITY.md](../QUALITY.md#meaningful-testing), use the native framework and conventions, and add only tests that protect observed behavior. ## Build and veri