feat(baseline): add web-features Baseline gate (config-driven)#10
Merged
Conversation
…mance evidence) Third and final gate-promotion (epic prx-em8h). Promotes bd-site's bespoke baseline gate into the kit, same pattern as vuln (#7), vnu (#9), axe (#6). Maps the SHIPPED CSS to web-features Baseline data via stylelint-plugin-use-baseline (headless, no browser) and FAILS CLOSED when the site-wide status is below target. HONEST: reports the MEASURED status (widely/newly/limited = the worst feature used); a feature guarded behind an @supports query is a tested fallback and doesn't count. Config-driven ($BASELINE_CSS/$BASELINE_TARGET/$BASELINE_REPORT); no site coupling. Emits the `baseline: {status, fallbackTested}` envelope lone's conformance() consumes for compatibility.baseline. Unlike vnu/axe, the engine (stylelint) is pure npm, so the fixture e2e is DETERMINISTIC and runs in CI (no skip). Tests: pure classify/threshold logic + e2e over good (widely) / bad (:has + ::selection → limited) fixtures. node test/run.mjs → 16/0. With this, all three bd-site gates are reusable in the kit; bd-site can now consume them vendored (prx-v5ry), and the kit is ready to publish (prx-47qm). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Third and final gate-promotion (epic prx-em8h). Same pattern as vuln (#7), vnu (#9), axe (#6).
What
gates/baseline-gate.mjs(+ck-baseline-gatebin): maps the shipped CSS to web-features Baseline data viastylelint-plugin-use-baseline(headless, no browser) and fails closed when the site-wide status is below target.widely/newly/limited= the worst feature used. A feature behind an@supportsquery is a tested fallback and doesn't count against it.classify,meetsTarget,evaluateBaseline) unit-tested; config-driven ($BASELINE_CSS,$BASELINE_TARGET,$BASELINE_REPORT), no site coupling.baseline: {status, fallbackTested}forcompatibility.baseline.Verification
node test/run.mjs→ 16 passed, 0 failed. Unlike vnu/axe, the engine (stylelint) is pure npm, so the fixture e2e is deterministic and runs in CI (good=widely, bad=:has()+::selection→limited; no skip).Epic status (prx-em8h)
All three bd-site gates now reusable in the kit (vuln/vnu/baseline). Next: bd-site consumes them vendored (prx-v5ry), then publish the kit to npm + JSR (prx-47qm).
🤖 Generated with Claude Code