Part of QA PAR-457. Live mobile journey: create GENE-2 ('QA triage: review new request') explicitly in Triage → open Triage queue → tap request → Accept. Queue shows Triage is clear. Open /w/design-qa-20261018/issues/GENE-2 and reload/revisit minutes later: Status is still Triage and Activity contains only issue creation, with no accepted decision. This creates two contradictory meanings of Triage and loses the review audit trail. Expected: acceptance moves into a clearly chosen ready/backlog status, records who accepted and when, or explicitly exposes a separate reviewed state throughout the product. Verify status-group list/board agree with queue. Confirmed after fresh navigation, not just optimistic state. Evidence: triage-selected-mobile-stable.png; persisted issue checked at 22:34 UTC.
Implemented in the dependent QA stack: https://github.com/ParadauxIO/taskl.ie/pull/92
Combined verification passed: full API suite (1,306 tests), web lint and TypeScript, unit suite (1,211 passed; one existing skip), 483 Chromium story checks, and the production Next.js/CSS build. Desktop/mobile component evidence and a flow diagram are attached where applicable; server-rendered screenshot gaps and GitHub rollout prerequisites are explicit in the PR.
Awaiting review and merge; production application code has not been deployed by this task.