You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Complete the production interface by integrating encoded-signal warnings and final generation feedback into the redesigned workflow, then verify the entire application against the parent specification across responsive, keyboard, contrast, and regression requirements.
Acceptance criteria
Encoded-signal warning options are clearly grouped, their purpose remains understandable, and inactive advanced details are hidden or visually de-emphasized where practical.
Warning controls and indicator colors remain fully labeled and keyboard operable.
Generation, import, export, preview validation, success, and failure states use consistent feedback near the action that produced them.
Text, ticks, labels, fields, and muted descriptions maintain practical readability and contrast in the dark interface.
Interactive targets and focus indicators remain visible and usable throughout the page.
Color is not the sole means of identifying a band, warning, selection, error, or status.
A keyboard-only walkthrough succeeds for configuration, graph editing, band actions, warning controls, import/export, and LUT generation.
Manual visual verification succeeds at desktop and narrow viewport widths with no clipped controls or horizontal page scrolling.
Existing editor, graph, web integration, and backend tests pass.
Frontend type checking and the production build pass.
Generated LUT behavior and API contracts remain unchanged.
Parent
What to build
Complete the production interface by integrating encoded-signal warnings and final generation feedback into the redesigned workflow, then verify the entire application against the parent specification across responsive, keyboard, contrast, and regression requirements.
Acceptance criteria
Blocked by