TanStack Start Wiki Scaffold

Initial Debt

dp scaffold init can seed a Fumadocs wiki, but the generated app is hard-coded to Next.js. Fumadocs and TanStack Start both support a first-class TanStack Start docs app, and issue #20 asks for that framework option. Without a durable framework pin, a manually converted TanStack Start wiki can also be pulled back toward Next.js by dp update wiki alignment.

Evidence

• apps/cli/src/content/wiki.ts emits Next.js package scripts, next.config.mjs, App Router files, and fumadocs-ui/provider/next.
• apps/cli/src/scaffold/stage.ts prompts only for backlog provider and writes only backlog-provider.md.
• apps/cli/src/update/run.ts stages expected wiki output with scaffoldWikiForDirectory() and has no framework pin lookup.
• Fumadocs current docs list TanStack Start as a supported create-fumadocs-app framework and its manual install uses Vite, TanStack routes, and fumadocs-ui/provider/tanstack.

Resolution

• Add a wiki framework prompt to dp scaffold init.
• Persist the framework choice in <wiki-root>/wiki-framework.md.
• Emit framework-specific Next.js or TanStack Start runtime files from the shared wiki template.
• Teach dp update to preserve a pinned TanStack Start wiki.
• Update scaffold docs and record implementation evidence.

Resolution Spec

• apps/wiki/content/docs/project/specs/cli/issue-20-tanstack-start-wiki/SPEC.md

Resolution Plan

• apps/wiki/content/docs/project/specs/cli/issue-20-tanstack-start-wiki/PLAN.md

Implementation Notes

• apps/wiki/content/docs/project/specs/cli/issue-20-tanstack-start-wiki/IMPLEMENTATION-NOTES.md

Validation

• bun run --cwd apps/cli test -- src/scaffold/stage.test.ts src/update/run.test.ts