[roomote-roomote]

​Opened on behalf of @daniel-lxs. Follow up by mentioning @roomote-roomote, in the web UI, or in Telegram.

What changed

Use the existing muted-foreground color without extra opacity for Sessions-list actor and source metadata. Preserve the row's size, layout and controls.

Why this change was made

On current develop, seven visible 12px metadata rows fail light-mode contrast at 3.72:1 against the list background, below the 4.5:1 requirement. Removing the extra opacity makes session ownership and entry surface easier to read without competing with the title.

Impact

This is one color-token adjustment with no new styles, state, UI or dependencies. The actual list now has zero axe color-contrast violations at desktop/mobile sizes in both light and dark themes. Dark mode was checked as a preserved adjacent flow, and an actual mobile card link still opens its session. All 14 existing SessionCard behavioral tests, web typecheck and repository pre-push gates pass; no tests asserting CSS classes were added. This is scoped contrast evidence, not a claim that every accessibility issue is resolved.

Screenshots

Genuine local seeded sessions with native viewport/color-scheme emulation. Screenshots show appearance; numerical contrast is established by the browser audit.

Related PRs

• Personal instructions draft preservation — independent settings fix.
• Users settings read recovery — independent settings fix.
• Settings and analytics main landmark — independent accessibility fix.
• Mobile password-reset link wrapping — independent dialog layout fix.

[roomote-community]

No code issues found. See task

Reviewed the one-line metadata color change in SessionCard.tsx, surrounding component behavior, list/board usage, light/dark theme tokens, and existing test coverage. The change removes only the extra color opacity and preserves layout and interactions. Current-head lint, type check, and Knip checks passed; tests, app build, and JavaScript/TypeScript CodeQL were still running when checked. No local suites or browser audit were rerun.

_{Reviewed 3f9cc2e}