Skip to content

test(app): qualify Quiet Companion for production #68

Closed

Description

@trmosala

What to build

Qualify the complete Quiet Companion interface for production across responsive layouts, accessibility, localization, visual parity, and regression behavior. This issue is the integration gate for the independently delivered navigation, new-task, session, and Browser/Changes slices.

Accessibility and localization should be built into each preceding slice; this issue closes remaining cross-slice gaps and verifies the assembled experience rather than postponing all such work until the end.

Acceptance criteria

  • The assembled interface preserves the approved Quiet Companion visual direction, including its calm light palette and landing and thread presentations.
  • Desktop presents the applicable navigation, session, and context panes without overlap or clipped primary actions.
  • Tablet hides or adapts the context pane at the intended breakpoint while keeping its state intact.
  • Mobile provides a usable primary session surface and an accessible way to reach navigation and context actions.
  • Layout remains usable at supported zoom levels and with long content, long localized strings, and narrow widths.
  • All new visible strings use the application's typed localization system.
  • Keyboard users can reach and operate all interactive controls with logical focus order and visible focus.
  • Controls expose appropriate accessible names, roles, states, and error associations.
  • Color contrast and reduced-motion behavior meet the project's accessibility expectations.
  • Left-to-right and right-to-left layouts are verified, including pane order, directional icons, mixed-direction text, scrolling, and resizing.
  • End-to-end coverage exercises both legacy and Quiet Companion modes, toggle persistence, new-task submission, session interaction, navigation, Browser/Changes switching, and responsive breakpoints.
  • Existing timeline performance checks remain within their accepted baseline.
  • Package typecheck, scoped lint, relevant application tests, and desktop integration checks pass.
  • Visual comparison against the approved prototype records any intentional differences.

Blocked by

Activity

  1. added
    enhancementNew feature or request
    ready-for-agentScoped work with acceptance criteria and recorded blockers
    on Oct 6, 2026
  2. trmosala commented on Oct 17, 2026

    @trmosala
    OwnerAuthor

    Implemented and verified in local commit 3d66d6530a9ffcefb8edbb65e444422450d66414 on interface-toggle.

    Production qualification is recorded in packages/app/QUIET_COMPANION.md. The accepted later in-app white Light/Dark direction is retained, with intentional differences from the original cream/sample design documented before prototype retirement.

    Passing evidence: desktop/mobile Light/Dark and contrast checks, Arabic RTL/long labels at tablet width with 125% zoom/reduced motion, keyboard navigation, both branded interface transition directions and persistence, real session/submission/context flows, app and E2E typechecks, scoped lint (zero errors), 18 unit tests, 30 browser component tests, navigation/lifecycle/environment probes, and real Electron rendering/tab-lifecycle checks. The post-retirement branded production build passed 10 workflow/toggle cases. Navigation retained zero blank/unknown samples; timings are diagnostic.

    Recorded limits: the existing tall-row visual probe and nested-keyboard scroll probe also fail on the unchanged baseline. The existing preview/capture DOM fixture stalls alone and grouped. These were not repaired or presented as passing evidence. The drag-selection probe now waits for its target to be in the viewport and passes. Live WPP inference and packaged Windows behavior remain unverified. Closure records completion of the requested integration with these explicit baseline/verification limits.

    This commit is local only: it has not been pushed, merged into dev, or released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentScoped work with acceptance criteria and recorded blockers

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions