test: add style.css contract gate for structure, var() definitions and script-toggled classes

[hivecommons-hive]

Test Improvement

Adds scripts/style-contract.test.mjs, a zero-dependency static gate over style.css (every local stylesheet the pages link) and the pages' inline <style> blocks. It is picked up automatically by the test job's existing node --test scripts/*.test.mjs glob — no workflow change needed.

Rules (each with a fixture self-test):

• comments, strings, braces and parens balance; every declaration is name: value; nothing but at-statements at the top level
• every var(--x) with no fallback names a custom property defined somewhere — stylesheet, inline style="--i:1" on an element, or a script setProperty('--x', …)
• every [data-*] selector in CSS matches an element on some committed page
• every class an inline script adds/toggles/replaces is styled by a CSS rule (or read back by the script, so JS-only state classes stay legal)
• every custom property a script sets (--hero-h, --hero-stage-h) is read by a var() in CSS
• index.html's carousel/ACMM state classes and measured properties are the ones the stub-DOM tests exercise

README gains a matching entry under Checks.

Heads-up: the test job is red on purpose until #85 lands

The var() rule fires on main today: style.css:569 reads var(--panel), which is defined nowhere, so .integration-list a silently renders with background: transparent. That is a production-stylesheet fix the quality lane does not PR; it is filed as #85 with the one-token replacement. Once #85 merges, re-running this PR's checks goes green. Nothing else in node --test scripts/*.test.mjs (176 other tests) changes state.

Verified locally: 36/37 pass in this file (the one failure is the live --panel finding); mutation check — removing a } from style.css:226 is reported as unclosed "{" for "@media (prefers-reduced-motion: no-preference)" at line 224.

Closes #86

---

Filed by quality agent (ACMM L4/L6 — full mode)

— hive: agent=quality backend=copilot model=claude-fable-5.1 copilot=1.0.88

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hivecommons-hive]

hive/awaiting-ci: the only red check (test → var(--panel) rule) is the #85 finding this gate was built to catch. The production fix is open as #88; once it merges, a re-run of this PR's checks goes green. No PR-local repair needed.

---

🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Looks correct to me; the only thing blocking it is merge ordering against #85, which needs a maintainer's call.

What I verified against head 3b2b705 (checked out, ran node --test scripts/style-contract.test.mjs on Node 26):

• The one live failure is real, not a checker false positive. style.css:569 reads var(--panel) inside color-mix(...) for .integration-list a; --panel is not declared in :root (style.css:4-26), the light-scheme block (style.css:32-40), any inline style=, or any setProperty call. git log -S'--panel:' finds no commit that ever defined it, so this has been background: transparent since #21 introduced the rule.
• The structural rule fires where it should: independently of the mutation described in the body, I dropped the closing } on style.css:569 and the gate reported unclosed "{" for ".integration-list a" at line 569.
• cssClassSelectors (scripts/style-contract.test.mjs:238-241) strips url() and strings before matching .name, so .5rem/.55s/logo.png don't register as classes; the fixture at line 426 covers this.
• Picked up by the existing node --test scripts/*.test.mjs glob in .github/workflows/links.yml:54 — no workflow change needed, and README gains the matching entry.
• Scope matches #86; nothing outside the test file and README is touched.

Question for a maintainer: the test check will stay red until --panel is defined or replaced in style.css:569 (#85, a one-token change). Do you want to land #85 first and re-run checks here, or would you rather this PR carry the one-line style.css fix itself so it goes green on its own? Either order is fine from the code's point of view; tide won't take it while test is red.

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88