VERIFY / RELEASE REPORT
Release reports
A public control surface for release readiness, security, accessibility, performance, provenance, and the commands that reproduce every verdict.
Release readiness
SHIP
control gates passed
A dated repository snapshot — never a claim of permanent health.01 / Signals
The reading, at a glance.
Platform and evidence metrics are shown together because a beautiful interface is not ready when its proof, security, or runtime budget is missing.
- Browser · macOS
- 97/97
- retries disabled
- Browser · Linux
- 97/97
- retries disabled
- Unit contracts
- 243
- 34 test files
- Reference Atlas
- 128
- 47 rules · 54 artifacts
- Known vulnerabilities
- 0
- 611 packages scanned
- Route budget headroom
- 4.8%
- 714.0 kB / 750.0 kB
02 / Controls
Every claim has a gate.
PASS is earned by an executable command and a repository-owned artifact. The ledger exposes both.
- 01Core qualityPASS
Lint, formatting, build, type contracts, unit tests, graph validation, and package artifacts run as one gate.
pnpm qa:core - 02Cross-platform browserPASS
E2E, visual, no-JS, and hydrated behavior run with retries disabled on macOS and official Playwright Ubuntu.
pnpm exec playwright test --retries=0 - 03AccessibilityPASS
WCAG-tagged axe checks, keyboard paths, forced colors, reflow, reduced motion, and no-JS reading are enforced.
pnpm test:a11y - 04SecurityPASS
Strict script CSP, defensive headers, dependency scanning, and leak-safe repository boundaries are checked.
osv-scanner scan --lockfile=pnpm-lock.yaml - 05PerformancePASS
Route bundles, transfer size, Japanese font cost, and package entry points stay inside explicit budgets.
pnpm performance:check - 06Evidence provenancePASS
References, canon rules, artifacts, backlinks, freshness, and external links remain graph-consistent.
pnpm evidence:check - 07LocalizationPASS
English and Japanese routes preserve meaning, metadata, navigation, responsive layout, and keyboard behavior.
pnpm test:e2e
03 / Proof chain
Evidence becomes a verdict.
The report follows the same Proof Grammar as the product: source, executable rule, inspected artifact, bounded verdict.
- 01Evidence
Versioned first-party sources and measured repository state.
- 02Command
A deterministic check that another contributor can run.
- 03Artifact
A report, snapshot, test, or build output owned by the repository.
- 04Verdict
SHIP only when every blocking control is green.
04 / Honest boundary
What this report does not promise.
Enterprise quality includes visible uncertainty. These boundaries remain explicit instead of being flattened into a green badge.
- 12 upstream changes remain queued for human review.
- Automated accessibility checks supplement manual assistive-technology testing.
- The verdict applies to the recorded source revision and verification date.