Add /new-project bootstrap command (guide + wrapper)

The inverse of /retrofit: workshops a captured (new) inbox idea into a repo that is standards-compliant from line one (AGENTS.md + CLAUDE.md symlink, ROADMAP, canonical deny-by-default .gitignore, .claude wiring, inbox-check line), publishes via a manual Gitea-create gate, and clears the (new) inbox item. Resolves ROADMAP item 5 open questions (manual Gitea gate; stack quality gate deferred to /harden; workshop seeds Current state) and marks it BUILT.

ROADMAP.md

@@ -78,31 +78,25 @@ automatic so every repo inherits it.
 - Decide whether the canonical wording lives in `how-i-work.md` (so it's truly universal)
   or stays a per-repo line.
 
-## 5. `new-project` — idea → scoped → scaffolded → Gitea repo
+## 5. `new-project` — idea → scoped → scaffolded → Gitea repo ✅ BUILT
 
-**Why:** the inverse of `/retrofit`. Retrofit moves an *existing* project onto disk; this
-takes a captured `(new)` inbox idea and turns it into a real, standards-compliant repo. It
-closes the capture loop: `/capture (new) …` → bootstrap → a repo that already has AGENTS.md,
-the CLAUDE.md symlink, ROADMAP.md, the canonical `.gitignore`, and the inbox-check line.
+Built and live: `guides/new-project.md` + `adapters/claude/commands/new-project.md`. The
+inverse of `/retrofit` — main-thread and collaborative, it turns a captured `(new)` inbox
+idea into a repo that's standards-compliant from line one. Phases: locate the inbox seed →
+workshop the scope (the high-value, interactive step) → brief + scaffolding-plan sign-off →
+scaffold (`AGENTS.md` + `CLAUDE.md` symlink, `ROADMAP.md`, `README.md`, canonical
+`.gitignore`, `.claude/`, minimal stack skeleton; inbox-check line tagged `(<name>)`) →
+publish (git init + commit, Gitea manual-create gate, remote + push) → close the loop
+(remove the `(new)` item from `INBOX.md`) → portability-checker verify.
 
-**Shape:** a command (`/new-project`, run from `~/Projects`), main-thread and collaborative
-— scoping is a conversation, not a delegated job. Phases:
+**Open questions, resolved:** (a) Gitea repo creation is a **manual web-UI gate** (no API
+token — matches retrofit-playbook Part 4); (b) the standards layer is always scaffolded, the
+stack skeleton stays minimal, and the **linter/pre-commit quality gate is deferred to the
+future `/harden`** (item 1) rather than hand-rolled; (c) the workshop **does** seed the first
+`## Current state` with the first milestone.
 
-1. **Workshop the scope** — back-and-forth to sharpen objectives, non-goals, stack, and the
-   key early decisions. Pull the seed from the `(new)` inbox item if one exists. This is the
-   high-value step and stays interactive (like roundup, the reasoning is the user's).
-2. **Seed prompt** — synthesize the workshop into a concrete project brief / initial build
-   prompt plus a scaffolding plan; get the user's sign-off.
-3. **Scaffold** — create the new folder under `~/Projects`, write the initial AGENTS.md
-   (from the brief) + CLAUDE.md symlink, ROADMAP.md, README, the canonical `.gitignore`,
-   `.claude/` wiring, and the starting directory structure. Compliant from line one.
-4. **Publish** — `git init` + initial commit, create the Gitea repo, add the remote, push
-   (reuse retrofit-playbook Part 4; if no Gitea API token is available, hand back the manual
-   "create empty repo, copy URL" step). Then remove the `(new)` item from the inbox.
-
-**Open questions:** Gitea repo creation — API token vs. manual UI step; how much scaffolding
-is generic vs. stack-specific (does it call a `/harden` step from item 1 to install the
-stack's linter+hook?); whether the workshop output also seeds the first `## Current state`.
+**Remaining option:** once `/harden` (item 1) exists, call it as the scaffold's last step so a
+new repo gets its stack's quality gate installed automatically.
 
 ## 6. Cross-repo git-hygiene audit + remediation ✅ DONE (2026-06-14)