Consolidate tools and fix static assets

This commit is contained in:
2026-04-12 01:18:26 +02:00
parent 7843073d13
commit f625cdae0d
14 changed files with 639 additions and 221 deletions

View File

@@ -30,7 +30,7 @@ It is intentionally implementation-focused:
- Branch: `frontend/tables-overhaul`
- Last updated: `2026-04-12`
- Current focus: `Phase 5`
- Current focus: `Phase 6`
- Document mode: living plan and progress log
### Progress Log
@@ -77,6 +77,7 @@ It is intentionally implementation-focused:
| 2026-04-11 | Post-P3 fix 2 | Completed | Simplified `/tables` by removing static prose and context controls, dropped the redundant selected-result inspector in favor of a floating action menu, and moved the canvas onto its own scroll region so sticky headers layer correctly beneath the context bar. |
| 2026-04-12 | Phase 4 planning | Planned | Expanded the `Curation` phase from a route placeholder into a concrete migration plan that moves queue-first curation out of `Tables` and into a dedicated workflow surface. |
| 2026-04-12 | Phase 4 | Completed | Replaced the placeholder `/curation` route with a real queue-first workspace, added queue scope and context persistence, moved browse-to-curation handoff out of `Tables`, and preserved diagnostics and full-editor escape hatches without keeping queue work on the reference page. |
| 2026-04-12 | Phase 5 | Completed | Consolidated the existing tooling routes into a coherent `Tools` workspace with a real hub, shared tooling page frame, preserved-context exits from diagnostics back into `Tables` and `Curation`, and a grouped API reference surface. |
### Lessons Learned
@@ -688,6 +689,22 @@ Create a dedicated queue-first curation workflow so repair work is fast and does
## Phase 5: `Tools` Consolidation
### Status
`Completed`
### Task Progress
| Task | Status | Notes |
| --- | --- | --- |
| `P5.1` | Completed | The thin `Tools` panel was replaced with a real hub page presenting diagnostics and API docs as destination cards. |
| `P5.2` | Completed | Diagnostics remained on the canonical `/tools/diagnostics` route established earlier. |
| `P5.3` | Completed | API docs remained on the canonical `/tools/api` route established earlier. |
| `P5.4` | Completed | Tooling pages now reuse a shared tooling frame and the same table-context URI patterns already used by `Tables`, `Curation`, and diagnostics. |
| `P5.5` | Completed | Diagnostics now exposes preserved-context links back into `Tables` and `Curation`, plus a stable return path to the `Tools` hub. |
| `P5.6` | Completed | Deep inspection remains isolated to tooling surfaces; browse and curation flows still link outward instead of embedding engineering detail inline. |
| `P5.7` | Completed | The tooling pages now share a stronger cool-slate documentation/workbench treatment instead of ad hoc panel stacks. |
### Goal
Separate diagnostic and developer tooling from player-facing flows without losing deep-link usefulness.