Historical audits and evidence
This index separates recorded observations from current installation and support guidance. Each linked record retains its original commit, date, scope and limits; its package versions and test counts do not automatically describe today’s source. Use current releases, coverage and support profiles for current claims.
Publication evidence
Section titled “Publication evidence”The release ledger retains exact published identities, hashes and verification URLs. Package changelogs explain what changed; the ledger establishes which artifacts were actually checked.
Historical implementation and documentation checks
Section titled “Historical implementation and documentation checks”- Adoption verification
- Compatibility verification
- Boundary hardening
- Cross-port parity review
- Page-by-page implementation audit
- Site verification before publication
- Dated device-compatibility gap ledger
- C candidate release-readiness
- C verification record
- Rust verification record
- Dart historical candidate verification
These are evidence records, not alternative release runbooks. Follow the release procedure for new artifacts.
Protocol authority and reproducible checks
Section titled “Protocol authority and reproducible checks”The specification audit records protocol/errata reasoning and its evidence limits; it is not obsolete merely because it is called an audit. Shared conformance contracts remain authoritative for comparisons. Do not rewrite hash-pinned contracts as documentation cleanup.
Physical equipment
Section titled “Physical equipment”Follow the equipment-testing procedure. The passive KICKR CORE pilot describes one bounded observation, not universal compatibility. Simulation, host tests, compile-only checks, public consumers, device execution and Bluetooth qualification are separate evidence categories.