Part of QA PAR-457. Signed-out Paradaux public workspace banner says 'Sign in to vote and comment'. Fresh QA account signs in, opens /w/paradaux/issues/PAR-357, and Activity instead says 'Your role in this workspace can read but not comment.' No comment composer exists. Account is not a Paradaux member. Signing in fulfills the advertised requirement but does not unlock the promised action; community users are sent through registration with a false expectation and no explanation of how to gain access. Expected permission-aware CTA/copy ('Sign in to vote' if only voting is public), or an explicit request-to-join/comment permission flow. Do not loosen permissions just to fit copy. Observed anonymous and authenticated contexts on live production. Original banner captured in browser snapshots; authenticated permission state confirmed with native accessibility role queries.
Implemented in the dependent QA stack: https://github.com/ParadauxIO/taskl.ie/pull/101
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.