stack/docs/scratchpads/prd-implementation-20260222.md

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
S1	2026-02-22	MS16+MS17	PG-FND-001 to PG-VER-001	13 implementation tasks completed. PRs #470-#483 merged. 3 test failures fixed. All 5125 tests pass.
S2	2026-02-22	MS16+MS17	PG-DOC-001	Documentation updates — PRD statuses, manifest, scratchpad, TASKS.md.

Open Questions (Resolved)

1. Kanban DnD library: RESOLVED — @hello-pangea/dnd selected (maintained fork of react-beautiful-dnd, better TS support)
2. Workspace page default view: RESOLVED — Shows project selector when no project param, workspace detail when ?project=id
3. File Manager vs Knowledge: RESOLVED — File Manager maps directly to Knowledge entries via /api/knowledge. API shape matches UI needs.

Execution Summary

PRs Merged (14 total)

PR	Task	Description
#470	PG-PLAN-001	Planning artifacts (TASKS.md, manifest, scratchpad)
#471	PG-FND-002	Settings root page — 4 category cards
#472	PG-FND-001	Custom 404 pages (global + authenticated)
#473	PG-API-001	Tasks page wired to real API
#474	PG-API-002	Calendar page wired to real API
#475	PG-API-001	Tasks API updateTask function
#476	PG-API-003	Knowledge pages wired to real API (238 lines mock removed)
#477	PG-PAGE-001	Projects list page (809 lines)
#478	PG-PAGE-003	Kanban board with DnD
#479	PG-PAGE-002	Project workspace with tabs
#480	PG-PAGE-005	Logs & telemetry page
#481	PG-PAGE-004	File manager page
#482	PG-PAGE-006	Profile page
#483	PG-VER-001	Test fixes (3 failures resolved, 5125 pass)

Issues Closed

• #466 (Phase 1: Foundation pages)
• #467 (Phase 2: Mock elimination)
• #468 (Phase 3: New pages)
• #469 — pending closure after deploy

Deployment Blocker — 2026-02-23

Issue: Traefik proxy does not route HTTPS to the API container (api.mosaic.woltje.com) after service restart.

Observed behavior:

• HTTP (port 80) works for both mosaic.woltje.com and api.mosaic.woltje.com (301 redirect)
• HTTPS to mosaic.woltje.com (web) returns 200 — pages render
• HTTPS to api.mosaic.woltje.com (API) hangs after TLS handshake — zero bytes received
• Issue persists through multiple stop/start/restart cycles
• Same behavior from external IP and from direct connection to 10.1.1.44
• All containers healthy internally (Coolify reports running:healthy)
• Docker labels for Traefik routing are correct (verified via API)
• Go-Live MVP deployment (pre-restart) had both working

What IS verified:

• CI pipeline #585 green (lint, typecheck, test, build, docker, trivy)
• Web container serving latest code — all 10 new page routes return HTTP 200
• 404 page renders correctly ("Page Not Found", "Go to Dashboard")
• API container healthy (health endpoint works internally)
• All 15 PRs merged to main (#470-#484)

What is NOT verified (requires API access from browser):

• Auth flow (login via Authentik)
• Pages rendering with real API data in browser
• No console errors during navigation

Root cause: Likely Traefik cert store or internal routing table corruption after container restart. Requires server-level access to inspect Traefik logs (docker logs coolify-proxy).

Resolution needed: Jason to check Traefik proxy logs on Coolify server (10.1.1.44). May need Traefik proxy restart or cert store cleanup.

Corrections

(none)