feat(frontend): two-pane GM Workbench layout — tool palette + history rail (#153) #224
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/153-workbench-ux"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Replaces GM Planning's stacked
max-w-2xlcolumn with the two-pane workbench the report specs — the layout that makes the Workbench feel like one coherent surface rather than a stack of forms.Layout
WORKBENCH_TOOLSregistry drives it):Active tool highlighted; opens on Beat Planner (the primary planning organizer).
GenerationHistoryscratchpad (#138); its Re-open switches the active tool to the matching generator (handleReopen).lg→ 3 columns (palette | center | history);md→ 2 columns with history full-width below; mobile → single column with the palette collapsed to a grouped<select>(<optgroup>per category). Widened tomax-w-7xl.Scope note (interpretation)
This pass delivers the palette + dispatcher + history-rail shell — the coherent-workbench UX and the two-pane layout (acceptance criteria 1, 5). Collapsing the eight already-shipped, tested bespoke panels into a single config-driven
GeneratorPanelwith one uniform action row (criteria 2/3) is intentionally deferred: it would rewrite working, tested code (each tool has genuinely different inputs and result shapes), and the panels already share theWorkbenchResultActionslanding bar. Flagged for your call — happy to follow up if you want the full config-driven collapse. Criterion 4 (name-gen session gate) and 6 (shared API client — already true) unaffected.Verification (Docker)
Closes #153.