Area: Account & identity (audit phase 1) · Surface: /profile/edit (ProfileController@editProfile) · Dimension: law-3-contrast · Severity: minor
The quick-add chips (Mastodon, GitHub, etc.) set an explicit pill background (--color-bg-input) but their text color references a token that does not exist, so the color is whatever the cascade inherits rather than the intended theme foreground. Per the project rule, text inside a hardcoded/explicit-background container must use a valid semantic token, never an undefined one.
Evidence
platform/templates/profile/edit.php L272: style="background:var(--color-bg-input);border:1px solid var(--color-border);...;color:var(--color-text);"
`--color-text` is never defined: `grep -cE '^\s*--color-text:' public/css/style.css` returns 0 and `grep -oE '\-\-color-text\b[^-]'` returns nothing. Only --color-text-primary / --color-text-muted / --color-text-secondary exist. The var() call has no fallback, so the chip text color resolves to `inherit` instead of a theme token, decoupling it from the explicit --color-bg-input background and risking a low-contrast pairing in one theme.
Suggested fix. Change color:var(--color-text) to color:var(--color-text-primary) on platform/templates/profile/edit.php:272.
Filed by the automated tenant-app audit (phase 1) and adversarially evidence-verified. Status: verified. Open — not yet actioned.
Patrick Bass
@mobieus