chore(orchestrator): bootstrap MS16+MS17 planning (#470)

Co-authored-by: Jason Woltje <jason@diversecanvas.com>
Co-committed-by: Jason Woltje <jason@diversecanvas.com>

docs/scratchpads/prd-implementation-20260222.md

@@ -0,0 +1,66 @@
+# Mission Scratchpad — PRD implementation
+
+> Append-only log. NEVER delete entries. NEVER overwrite sections.
+> This is the orchestrator's working memory across sessions.
+
+## Original Mission Prompt
+
+```
+Active mission detected: PRD implementation. Read the mission state files and report status.
+User instruction: start planning. Be complete and thorough.
+```
+
+## Planning Decisions
+
+### 2026-02-22 — Task Breakdown
+
+**Decision**: Combined MS16 (Pages) and MS17 (Backend Integration) into a single milestone because 19 backend API modules with 42 controllers already exist. Work is primarily frontend page creation and API wiring.
+
+**Task structure**: 15 tasks across 4 phases:
+
+- Phase 1 (Foundation): 404 page + Settings root — quick wins to fill navigation gaps
+- Phase 2 (Mock Elimination): Wire tasks/calendar/knowledge to real APIs
+- Phase 3 (New Pages): Projects, Workspace, Kanban, File Manager, Logs, Profile — the bulk of new work
+- Phase 4 (Verification): Theme/responsive check, docs, deploy + smoke test
+
+**Branch strategy**: One feature branch per task, PR to main, squash merge.
+
+**Dependency rationale**:
+
+- PG-PAGE-002 (Workspace) depends on PG-PAGE-001 (Projects) — workspace shows single project detail, needs project list/selection pattern established first
+- PG-PAGE-003 (Kanban) depends on PG-API-001 (Tasks API wiring) — Kanban needs the tasks API client to be working with real data before building the board UI
+- Phase 4 tasks are sequential: verification → docs → deploy
+
+**Codebase findings** (from exploration):
+
+- TaskStatus enum: NOT_STARTED, IN_PROGRESS, PAUSED, COMPLETED, ARCHIVED (5 Kanban columns)
+- Mock data locations: `apps/web/src/lib/api/tasks.ts`, `events.ts`, `knowledge.ts`, `client.ts`
+- API client pattern: `apiGet<T>()`, `apiPost<T>()`, etc. with CSRF + workspace headers
+- 17 shared UI components in packages/ui (Button, Card, Badge, Input, Modal, DataTable, etc.)
+- Sidebar nav defined in `apps/web/src/components/layout/AppSidebar.tsx` — all links already point to correct routes
+- Design tokens in `apps/web/src/app/globals.css` with full light/dark support
+
+**Estimate**: ~320K tokens total across all tasks.
+
+**Issues created**: #466 (Phase 1), #467 (Phase 2), #468 (Phase 3), #469 (Phase 4)
+**Milestone**: MS16+MS17-PagesDataIntegration (Gitea)
+
+### Profile Page Addition
+
+**Decision**: Added PG-PAGE-006 (Profile page) — PRD FR-003 notes "profile page navigation pending (MS16)" and the sidebar user card should link to it. Included in Phase 3.
+
+## Session Log
+
+| Session | Date       | Milestone | Tasks Done  | Outcome                                                                                             |
+| ------- | ---------- | --------- | ----------- | --------------------------------------------------------------------------------------------------- |
+| S1      | 2026-02-22 | MS16+MS17 | PG-PLAN-001 | Planning complete — milestone created, 4 issues created (#466-#469), 15 tasks populated in TASKS.md |
+
+## Open Questions
+
+1. **Kanban DnD library**: dnd-kit vs react-beautiful-dnd vs @hello-pangea/dnd — worker should evaluate during implementation
+2. **Workspace page default view**: Should it require project selection or show a default? (PRD open question #5) — ASSUMPTION: Show project selection/list if no project context, else show project detail
+3. **File Manager vs Knowledge**: PRD ASSUMPTION #5 says File Manager maps to Knowledge entries — worker should confirm API shape matches UI needs
+
+## Corrections
+
+(none yet)