[tnunamak]

Stacked on #620: the base is feat/console-connector-identity-icons, because the backgroundColor field on the shared mark renderer (ConnectorIcon) comes from that PR. Merge #620 first and GitHub retargets this PR to main.

What

The consent screen showed a connector's manifest glyph without its declared brand background. buildHostedMcpConsentChallengeModel (reference-implementation/server/routes/as-consent-ui-helpers.ts) copied only color, kind and svg from the manifest icon and dropped brand.background_color. A white glyph then rendered on the default tile and was invisible.

How

• The server model's icon now carries backgroundColor from manifest.brand.background_color. The server checks it with hexColorOrNull (#rgb or #rrggbb), which lives in @pdpp/brand-react (hex-color.ts) and is the same check the console uses in feat(console): show one identity-based connector mark everywhere #620; anything else, or no declaration, gives null and the default tile. validateManifestIcon covers icon only, so brand needed its own check.
• brand is an implementation extension: spec-collection-profile.md in this repo does not define it. It is operator-trusted manifest data, not connector-asserted identity, and the doc comment on ConsentPickerManifest says so.
• ConsentPickerManifest declares the optional brand and icon fields, so the compiler checks the capability boundary; the projection reads them without a cast.
• ConsentSourceIcon in consent-screen-model.ts mirrors the field. The shared mark validates it as a hex color and paints it as the tile background.

Relation to #620

#620 resolves each manifest's display mark, backdrop included, once in the console (resolve-manifest-display-mark.ts). The consent challenge is built by the authorization server from its own manifest reader, which the console cannot call, so this projection is that boundary for the consent screen and is still needed. It follows the same rule: the declared brand.background_color travels with the supplied mark, and a source with no mark falls back to the bundled one.

Tested

• New consent-screen-runtime.test.mjs case: a manifest with a white glyph and brand.background_color: "#1DB954" goes through the real projection and the real screen, and the mark tile's computed background is rgb(29, 185, 84). Before the change it is rgba(0, 0, 0, 0); the test fails there.
• Red then green: six cases (transparent, white, rgb(0 0 0 / 0), a declaration break-out string, a number, an empty string) failed before hexColorOrNull (the model carried the raw value) and pass after. Also pinned: a short hex is accepted, and a brand background with no manifest glyph is not applied to the resolved identity mark.
• From apps/console, npm run test:files on the consent-screen directory: 56 pass, 0 fail.
• From reference-implementation, node --import tsx --test on hosted-mcp-picker-scope-render, hosted-mcp-picker-render, hosted-mcp-selection and consent-challenge-csrf: 69 pass, 0 fail (re-run after the validation change).
• node --import tsx --test test/connector-manifest-validation.test.ts: 51 pass, 0 fail (the manifest icon.color check now uses the shared function).
• tsc --noEmit in reference-implementation and npm run types:check in apps/console: clean.

Assisted-by: AI