Verification

Verify the component and the application

Upstream evidence tells you what happened for a particular package, source set and environment. It does not prove that every application adopting it behaves correctly.

Release evidence for v1.1.0

The release links the successful deployment workflow and preserves these results:

Gate	Recorded result
Source validation, generated drift and build	Passed
Source tests	110 passed
Distribution tests	12 passed
Packed consumers across Chromium, Firefox and WebKit	63 passed
Specification browser suite	234 passed, 134 scoped skips
Verification-report generation and consistency	Passed
GitHub Pages deployment	Passed
Selected public-file readback	606 files matched the tested artifact
Live application protocol	All 31 Vue destinations at desktop/narrow/zoom widths, choices, Kanban focus, command search and record flows passed

These are recorded release results, not a permanent statement about a later live deployment. Use the attached evidence and digests to establish identity. Local Windows timing failures were retained separately from the successful complete Linux CI runs.

Which attachment answers which question?

Release attachment	What it establishes
release.json	Package name/version, archive length and digests
ui-consumer-evidence.json	Packed-consumer outcomes, environments and package/protocol identities
specification-evidence.json	Actual specification test records and run reference
verification-subject.json	Artifact/source identity for the tested specimens
delivery-provenance.json	Connection between revision, tag, CI run and artifact digests
live-readback.json	Selected public bytes compared with the tested deployment artifact
live-browser.json	Actual public portal/demo flow checks and limits
agent-consumer-report.json and agent-consumer-app.zip	An isolated app authored using the installed public copy CLI and exercised against the same archive

The isolated consumer was authored by the implementation agent. It is not an independent acceptance review. Automated browser coverage is not a manual screen-reader or physical-device pass.

Evidence vocabulary

Term	Meaning
Implemented	A maintained implementation exists
Demonstrated	A maintained example renders
testImplemented / compatibility alias tested	A test exists; this is not a passing execution
Passed	A named protocol completed its assertions for the recorded subject/environment
Skipped	That run did not exercise the check, with its recorded scope/reason
Stale	An earlier record no longer identifies the current source/artifact/protocol
Unknown / unavailable	There is insufficient evidence for the claim

Component maturity and inventory coverage do not replace execution records. A source or protocol change can make previous evidence stale without making the historical result false.

Test your application's real flows

• Check native successful form values, required validation, reset and disabled states; do not add duplicate hidden values.
• Operate themed choices through visible options and keyboard keys. Hidden native selectOption is not popup coverage.
• Verify keyboard order, focus rings, dialogs, Escape and opener focus return.
• Test errors, busy/success recovery and preservation of entered values where applicable.
• Exercise repeated instances, unique IDs, dynamic options/children and unmount/remount.
• Check narrow layout, text zoom, reduced motion, forced colors and real backgrounds for contrast.
• Test your backend and authorization separately; the synthetic demo provides neither.

Record actual environment and limits. Perform manual accessibility and device checks appropriate to your product; do not infer them from automated scans.

Repository checks versus consumer checks

Theme contributors run the repository's complete check loop from Contributing, including source/generation/drift, Node tests, build/dist, browser and verification-report checks. Package fixtures add ui:consumers, test:ui and ui:report. These verify upstream artifacts.

A consumer instead runs its own application checks against the pinned package/copies/mapping and records its canonical lock and deviations. Do not claim the app is verified because upstream CI is green.

Sources: accessibility contract, consumption guide.