feat: guided onboarding flow — charter init as first-class experience

[stackbilt-admin]

Problem

charter init currently does minimal scaffolding. New users have to read docs to understand which ADF modules to create, how to configure hooks, and what governance policies to enable. The gap between install and first value is too wide.

Proposal

Make charter init a comprehensive guided onboarding flow:

1. Auto-detect repo type — scan for package.json, Cargo.toml, go.mod, etc. Suggest relevant ADF modules based on stack
2. Interactive module selection — present available governance modules with descriptions, let user pick
3. Hook installation — offer to install pre-commit hooks (charter tidy, charter validate) with one confirmation
4. First scan — run charter doctor + charter drift scan immediately after setup so the user sees value in <60 seconds
5. Config generation — produce .charter/config.json with sensible defaults based on selections

Flags

• --interactive (default): guided walkthrough
• --minimal: current behavior (just scaffold)
• --preset <name>: skip questions, apply a known config (e.g. --preset typescript-monorepo)

Why this matters

• Reduces time-to-first-value from "read docs + manual setup" to "answer 3 questions"
• Presets enable org-wide standardization ("all new repos use charter init --preset acme-standard")
• Running doctor + scan immediately builds trust that the tool works

References

• OpenClaw onboard --install-daemon pattern
• npm init / pnpm create interactive flows
• Rust's cargo init auto-detection

🤖 Generated with Claude Code

[stackbilt-admin]

Fixed by cc_task eeb9f4ad. charter init now prints a guided welcome message with next steps and file explanations. Existing directories get a different message pointing to charter doctor.