fix(styles): move the last raw colour literals into tokens.css (§4.1.1)

[buddywhitman]

The "no raw colour literals outside tokens.css (§4.1.1)" step in ci.yml has failed every run on main since at least 1 October, on two lines:

• src/components/ConnectCallout.astro:74: the dark surface hex appeared in a comment. The comment now says "near-black".
• src/components/SiteHeader.astro:435: the More menu's float shadow was an inline rgb(). It is now --shadow-float in src/styles/tokens.css, and the header uses var(--shadow-float). The value is unchanged.

No visual change. The gate's grep now returns nothing, and check-contrast.mjs and check-hub-intros.mjs pass.

Follow-up to #57 (Employed), which surfaced the red ci run.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DCSn5sr8sYzppbRPy4wR9X

[scheemunai]

Applied to main (718e78b) and live on https://grokbot.dev — and main's ci is green again for the first time since the regression landed. Thank you, this was exactly the right fix: the comment reword costs nothing and --shadow-float is a genuinely better home for that shadow than an inline literal.

One process note rather than a criticism: the merge gate is content-only by design (community PRs may only ADD files under content/ — code changes come in through a maintainer, per the gate's own message), so I applied your branch to main directly instead of merging the PR. Credit is in the commit's Co-Authored-By trailers.

Maintainer edits: none — your diff went in exactly as submitted. I ran the local gate before pushing (npm run build + contrast + hub-intro checks, all green), and the deployed CSS now carries --shadow-float with the value unchanged.

Thanks again — clean diagnosis, minimal diff, and it un-blocks every future autopublish run from landing red.