Scaffold Wiki Fumadocs Routing

Initial Debt

The scaffolded wiki seed provided a Fumadocs app and base /docs/project pages, but did not include the bridge from existing monorepo documentation sources into content/docs. Repos with source material under docs/, <wiki-root>/specs, or <wiki-root>/domains still needed manual content copying, recursive meta.json repair, and app-root Vercel build handling before nested docs were discoverable.

Resolution

• Added a generated <wiki-root>/scripts/sync-content.mjs to the wiki scaffold template.
• Wired generated wiki build and check-types scripts to run content sync before Fumadocs generation.
• Synced <wiki-root>/specs, optional <wiki-root>/domains, and monorepo docs/requirements, docs/reference, docs/runbooks, and docs/tech-decisions.md into routed Fumadocs content when present.
• Generated or merged recursive meta.json files so nested copied folders appear in the Fumadocs tree.
• Documented the sync and app-root Vercel fallback in scaffold operator docs.

Resolution Spec

• apps/wiki/content/docs/project/specs/cli/issue-11-scaffold-wiki-fumadocs-routing/SPEC.md

Implementation Notes

• apps/wiki/content/docs/project/specs/cli/issue-11-scaffold-wiki-fumadocs-routing/IMPLEMENTATION-NOTES.md

Validation

• bun run test --filter=@punks/cli -- scaffold/stage.test.ts
• bun run check-types --filter=@punks/cli
• git diff --check