jpmschweitzerandClaude Opus 4.8
9be75d5592
clean-house sweep over governance/ (validate green, 0 broken refs before and after): - RULE-ANCHOR-DRIFT (37): rewrote inline cross-reference links left over from before the decisions/questions/rejected subdir split — flat naming (questions-architecture.md, questions-process.md, rejected.md) and bare same-dir paths that were actually cross-type — to canonical subdir-relative form with current slugs. pql resolved these by ID so they were never broken to the tooling, only to GitHub anchor navigation. - RULE-RECORD-SORT (1): reordered decisions/architecture.md D-records to strictly ascending (the D-1..D-6 block had been appended after D-41); pure block move, line count unchanged, content identical. - RULE-FILE-OVER-THRESHOLD: deferred (architecture.md 435 > 350; splitting would re-churn the anchors just fixed). - EOF/whitespace and Q↔D backlinks clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
956 B
956 B
Open Questions — Testing
Q-11: Coverage gates — hard thresholds vs soft reporting
- Status: Open
- Question:
ci/test_coverage.shemits lcov + a summary. Do we gate merges on a hard threshold (fail < 80%), report softly, or tier per directory (kernel > 90%, built-ins > 70%, widgets covered by goldens exempt)? - Context: Hard thresholds force tests-for-coverage-sake; soft reporting gets ignored.
- Source: 2026-04-21 planning.
Q-12: Screen-reader automation (axe-core via Playwright)
- Status: Open
- Question: D-22 gates contrast at build time. Do we also run axe-core against the WASM build in Playwright for runtime a11y issues (missing labels, invalid roles, orphan focusables)?
- Context: axe-core is JS; runs in the browser against the rendered tree. Extra CI time; extra signal.
- Source: 2026-04-21 planning.