feat(capability-matrix): strict cross-SDK parity score + coverage scope#63
Merged
Merged
Conversation
…tyReport - Add CORE_LANGUAGES constant and CoreLanguage type for the subset of language SDKs used in parity computation - Replace perFeature field in ParityReport with coverageScope: number - Expected: report.ts and generate-site.ts will fail typecheck until fixed in tasks 2 and 3
Task 1 removed perFeature from ParityReport per plan; Task 2's implementer re-added it (in both types.ts and report.ts) to make the whole-project typecheck pass early, which was never a Task 2 requirement — generate-site.ts still references parity.perFeature until Task 3 removes that column. Revert to the plan's exact shape; the remaining generate-site.ts typecheck failure is expected until Task 3.
… scope badge - Remove perFeature parity column from feature table - Add Coverage scope badge to header - Remove dead .th-parity and .parity-cell CSS rules - Reduce table colspan from LANGUAGES.length + 2 to LANGUAGES.length + 1
…anguage type Bare .parity-high/mid/low rules were unreachable after the per-feature column was removed — only the higher-specificity .sdk-score.* and .area-card-score.* combinators are ever matched. CoreLanguage was exported but never consumed anywhere.
QuintinWillison
approved these changes
Jul 15, 2026
… site Adds a hover tooltip on each badge plus a short note under them, so "58%"/"32%" don't read as mysterious numbers — states plainly that both are computed only across the 4 core SDKs and what counts as a pass.
…-visible Replace the hover-only badge tooltips with metric cards that show the description text directly under each value — no longer hidden behind a hover. Header restructured: title row on top, metrics row below it, then the SDK score cards.
partially_implemented was being treated as "done" for coverage scope via the shared isDone() helper (same as perLanguage's legacy semantics), but a partial implementation isn't really done — per review feedback on #63, a symbol-linked partial claim shouldn't score the same as a symbol-linked full one. perLanguage keeps its existing isDone-based behavior unchanged; only coverageScope now requires status === "implemented".
…mented Drops isDone() entirely — every metric (overall, perLanguage, coverageScope) now requires the exact "implemented" status. Per discussion on #63, partial credit conflated "claims something is done" with "actually done", which no longer applies anywhere in this pipeline.
2 tasks
grdsdev
added a commit
that referenced
this pull request
Jul 16, 2026
The "Coverage scope" card said features "marked implemented/partial" but the underlying computeParity() logic only counts strictly `implemented` status, per the strict cross-SDK parity change in #63. Reword the text to match the actual logic instead of the logic. Also fix missing leading "%" to match the other metric card's style.
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
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.
Summary
Implements SDK-995 — compute and publish the first cross-SDK feature parity score.
overallif it's exactlyimplementedin every core SDK (javascript, flutter, python, swift).partially_implementedno longer earns credit toward this metric.perLanguagecompletion score (informational, unchanged).symbolslist, i.e. how much of what's marked complete has real code evidence attached.perFeaturefield removed entirely).aggregate-capabilities.yml+deploy-pages.ymlpipeline, so it goes live on supabase.github.io/sdk automatically.Design spec:
docs/superpowers/specs/2026-07-15-first-parity-score-design.md(local, gitignored — not in this diff).Verified locally
Built the site against live compliance data fetched from all 6 available SDK repos (Kotlin has no
sdk-compliance.yamlyet):.th-parity/.parity-cellin rendered HTML, both new/existing badges render correctly.Test plan
npm test— 182/182 passingnpm run typecheck— cleannpm run build-siteagainst real fetched compliance data, manually reviewed in browsergrep -rn "perFeature"— zero remaining references