test(20): UAT diagnosed — Phase 20 work in wrong directory (go-backend vs backend)

.planning/phases/20-tablo-detail-kanban-restyle/20-HUMAN-UAT.md

@@ -1,40 +1,72 @@
 ---
-status: partial
+status: diagnosed
 phase: 20-tablo-detail-kanban-restyle
 source: [20-VERIFICATION.md]
 started: 2026-05-18T14:30:00Z
-updated: 2026-05-18T14:30:00Z
+updated: 2026-05-18T16:00:00Z
 ---
 
 ## Current Test
 
-[awaiting human testing]
+[testing complete]
 
 ## Tests
 
 ### 1. Tablo detail page visual layout
 expected: Page renders at /tablos/{id} with 1.75rem tablo name h1, metadata row (owner, due, status badge, progress bar), 5-tab bar, and kanban board with 4 columns matching Figma design
-result: [pending]
+result: issue
+reported: "All Phase 20 work was implemented in go-backend/ (old prototype directory) instead of backend/ (the actual production codebase). The tablo detail page does not exist in backend/ at all."
+severity: blocker
 
 ### 2. Drag-and-drop task reorder
 expected: Tasks can be dragged within a column; on drop the reorder-form submits to POST /tablos/{id}/tasks/reorder and the new order persists on page reload
-result: [pending]
+result: blocked
+blocked_by: prior-phase
+reason: Cannot test — tablo detail page does not exist in backend/
 
 ### 3. HTMX tab navigation
 expected: Clicking a tab sends hx-get to /tablos/{id}/{tab}, swaps #tab-content, and pushes URL — no full page reload
-result: [pending]
+result: blocked
+blocked_by: prior-phase
+reason: Cannot test — tablo detail page does not exist in backend/
 
 ### 4. Global /tasks page regression check
 expected: The global My Tasks page (/tasks) still renders correctly — .task-row layout unchanged, no CSS bleeding from the new .task-card rules
-result: [pending]
+result: blocked
+blocked_by: prior-phase
+reason: Cannot test — Phase 20 CSS was added to go-backend/internal/web/ui/app.css, not backend/internal/web/ui/app.css
 
 ## Summary
 
 total: 4
 passed: 0
-issues: 0
-pending: 4
+issues: 1
+pending: 0
 skipped: 0
-blocked: 0
+blocked: 3
 
 ## Gaps
+
+- truth: "Tablo detail page exists and renders in backend/ at /tablos/{id}"
+  status: failed
+  reason: "User reported: All Phase 20 work was implemented in go-backend/ (old prototype directory) instead of backend/ (the actual production codebase). The tablo detail page does not exist in backend/ at all."
+  severity: blocker
+  test: 1
+  root_cause: "Phase 20 plans executed against go-backend/ (old prototype) instead of backend/ (production codebase). backend/ uses a different structure: templates live flat in backend/templates/, handlers in backend/internal/{tablos,tasks}/, CSS in backend/internal/web/ui/. No tablo_detail.templ, no tablo detail handler, and no tablo detail CSS exist in backend/."
+  artifacts:
+    - path: "go-backend/internal/web/views/tablo_detail.templ"
+      issue: "Exists in wrong directory — needs to be ported to backend/templates/ as tablo_detail.templ"
+    - path: "go-backend/internal/web/views/tablo_detail_view.go"
+      issue: "View model exists in wrong directory — needs to be ported to backend/internal/tablos/"
+    - path: "go-backend/internal/web/handlers/tablo_detail.go"
+      issue: "Handler exists in wrong directory — needs to be ported to backend/internal/tablos/"
+    - path: "go-backend/internal/web/handlers/tablo_detail_tab.go"
+      issue: "Tab handler exists in wrong directory — needs to be ported to backend/internal/tablos/"
+    - path: "go-backend/internal/web/ui/app.css"
+      issue: "Tablo detail CSS section was added to go-backend CSS, not backend/internal/web/ui/app.css"
+  missing:
+    - "backend/templates/tablo_detail.templ — tablo detail page template"
+    - "backend/internal/tablos/tablo_detail_view.go — view model adapted to backend package structure"
+    - "backend/internal/tablos/tablo_detail_handler.go — HTTP handler wired to backend router"
+    - "Tablo detail CSS section in backend/internal/web/ui/app.css"
+    - "Routes registered in backend router for /tablos/{id} detail and tab endpoints"