Wayfinder: Restructure monorepo per repository organization conventions

Destination

Restructure the monorepo to follow the repository organization conventions from the wayfinder skill content — top-level layout, Diátaxis documentation structure, agent skills format, packaging conventions, and cleanup strategy.

Notes

Domain: TypeScript monorepo for Kimi Code CLI. Skills to consult: repository-organization (the skill content provided), domain-modeling, grilling. Standing preferences: follow conventions exactly, use git mv for moves, archive superseded docs, ignore generated artifacts.

Decisions so far

• Inventory current repository structure — Complete. 6,948 files categorized: 1,682 source, 417 docs, 2,341 tests, 321 build outputs (18.6 GB), 187 dev files. Key finding: massive build output in apps/*/dist directories.
• Monorepo package structure conventions — Complete. 17 packages audited: 15 compliant with src/tests/README pattern, 2 exceptions (kimi-code, vis) need restructuring.

Not yet specified

• Top-level directory layout alignment (src/, docs/, tests/, assets/, scripts/, dist/, scratch/) — #2518
• Root directory cleanup (tool-mandated + community health files only) — #2519
• Source files organization (what ships vs what doesn't) — #2530
• Documentation restructure to Diátaxis quadrants (tutorials/, how-to/, reference/, explanation/) — #2520
• Tests and evidence organization — #2521
• Assets classification (shipped vs project assets) — #2522
• Workspace layout: ignored directories (dist/, build/, node_modules/, scratch/) — #2523
• Cleanup strategy implementation — #2524
• Packaging conventions (build from src/, stage, validate, package) — #2525
• Agent skills portable bundle format compliance — #2526
• Publication preparation checklist — #2527
• Decide target tree on paper before moving anything — #2531

Out of scope

Start with the repository-organization skill content and the completed inventory in issue #2528 and package audit in #2529. Resolve the target tree on paper in issue #2531 before coordinating the remaining layout, documentation, tests, packaging, skills, and cleanup issues; done means the monorepo follows the agreed conventions without moving generated artifacts.