Repository navigation
coverage-rank: rank candidate lanes by real-world CSS reach on native per size - #146
Open
thejackshelton wants to merge 1 commit into
Open
thejackshelton wants to merge 1 commit into
thejackshelton wants to merge 1 commit into
Conversation
… per unit of work scripts/coverage-rank.ts (pnpm coverage:rank) compiles a probe set for every current chromestatus property plus curated value, selector, at-rule and element features through the compiler for web, iOS and Android, weights them by chromestatus and Web Almanac usage, and ranks the lanes in docs/goals/milestone-2-proof/data/coverage-rank-input.json by reach per size, with Tailwind sweep and north-star counts. It writes docs/goals/milestone-2-proof/coverage-rank.md.
This was referenced Oct 5, 2026
Merged
This branch has not been deployed
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.
COVERAGE-RANK (notes/PM-2026-10-04.md, owner: maximal CSS support on native, ranked by real-world reach).
What changed
scripts/coverage-rank.ts(pnpm coverage:rank): for every current chromestatus CSS property, plus curated value, selector, at-rule and element features, it compiles probe declarations through the compiler (createProjectWith, profiles enforced, parity environment) for web, iOS and Android and classifies each probe as supported, not-applicable-on-native (an info-level verdict, ready for NA-NATIVE), unproven context, or refused with its first blocking code. It weights rows by chromestatus / Web Almanac usage, attributes Tailwind-sweep refusals (iOS) and north-star declarations, and ranks the candidate lanes by reach / size. It writesdocs/goals/milestone-2-proof/coverage-rank.md(already on master as a board commit, together with its inputdocs/goals/milestone-2-proof/data/).package.json: thecoverage:rankscript entry.Statuses are never written down: they come from compiling, so rerunning the script after a feature lands moves its rows and lanes.
Input checks: every committed input (the curated input, both chromestatus snapshots, the Tailwind snapshot, north-star-check.json, webref) is validated and a malformed one stops the run; a compiler throw or harness diagnostic stops the run; a fixture-reader rejection is recorded as FIXTURE_MARKUP only for "unsupported markup" (inline SVG), anything else stops the run; a property Dragon accepts without curated samples is reported as a warning.
What passed
pnpm typecheck: pass.npx vitest run packages/parity/test/chrome-ports.test.ts(scans scripts/): 13/13 pass.node --conditions=dragon-internal scripts/coverage-rank.ts: runs in about 45 s, 0 warnings, output byte-identical on two runs and identical to the committed board file.pnpm test(lane contract: the driver proves it). No tests, checks, tolerances or fixtures changed.🤖 Generated with Claude Code