Skip to content

Polish the workflow UI after backend truth lands #129

Description

@shiny-code-bot

Parent plan: #120

Problem

Once the state model is correct, the app still needs a deliberate interaction/visual pass so the operator surface is meaningful, simple, and beautiful without losing power.

Goal

Polish the workflow UI after the backend contract and core UX migration are complete.

Scope

Refine the workstation UI against docs/style/workstation-ui.md and docs/style/frontend.md:

  • dense operational layout
  • stable primary action placement
  • clear secondary action grouping
  • scoped labels and navigation
  • stale-state and last-action feedback
  • responsive behavior and text fitting
  • browser-verified interaction states

Acceptance Criteria

  • A first-time operator can answer: what is this scope, what state is it in, what happens if I click the primary button, and how do I switch season/series scope.
  • Primary and secondary actions are visually distinct.
  • State changes after actions are visible quickly and do not require guesswork.
  • No decorative redesign hides operational density.
  • Browser validation passes across representative states and viewports.

Validation Matrix

  • not sampled
  • sampling
  • review ready
  • approved and queueable
  • processing
  • ready to validate
  • ready to promote
  • mixed season/series
  • complete/idle
  • needs attention

Dependencies

Depends on #127 and #128.

Problem

Once the state model is correct, the app still needs a deliberate interaction/visual pass so the operator surface is meaningful, simple, and beautiful without losing power.

Goal

Polish the workflow UI after the backend contract and core UX migration are complete.

Scope

Refine the workstation UI against docs/style/workstation-ui.md and docs/style/frontend.md:

  • dense operational layout
  • stable primary action placement
  • clear secondary action grouping
  • scoped labels and navigation
  • stale-state and last-action feedback
  • responsive behavior and text fitting
  • browser-verified interaction states

Acceptance Criteria

  • A first-time operator can answer: what is this scope, what state is it in, what happens if I click the primary button, and how do I switch season/series scope.
  • Primary and secondary actions are visually distinct.
  • State changes after actions are visible quickly and do not require guesswork.
  • No decorative redesign hides operational density.
  • Browser validation passes across representative states and viewports.

Validation Matrix

  • not sampled
  • sampling
  • review ready
  • approved and queueable
  • processing
  • ready to validate
  • ready to promote
  • mixed season/series
  • complete/idle
  • needs attention

Dependencies

Depends on #127 and #128.

Finish Line

Final operator UX pass makes the workflow simple, clear, beautiful, and browser-validated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issueplan:donePlan completed or superseded

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions