[v0.6.1] Qualify five profiles and admit release #24

Retrospective record created after implementation began; it does not satisfy the original before-implementation ordering required by docs/planning/firmware-v0.6.1-v0.7.0-roadmap.md §9.2. Owner: @yyods.

This issue is the sole physical qualification and release-admission tracker. Host tests, mocks, historical v0.6.0 evidence, or one profile cannot fill another profile row.

Acceptance criteria

• Freeze one clean v0.6.1 candidate identity and immutable source/tool inputs.
• Produce two clean, reproducible builds for each of the five exact profiles.
• Validate five distinct private hardening results: 35 scenario passes total and 250 sequential RUNs total.
• Capture all 10 candidate-bound sacrificial-media receipts: erased first boot and nonblank refusal for each profile.
• Capture 50 reset samples: 10 per profile.
• Capture 25 PUT and 25 GET samples of 64 KiB: 5 per direction per profile.
• Complete 100 reliability transfers: 20 transfers of 16 KiB per profile.
• Capture five fresh physical power-cycle advertising observations: one per profile.
• Complete profile-specific gates: ESP32-C3 G0–G6, Pico GP2 plus UF2/BOOTSEL recovery, and Waveshare display/splash qualification.
• Complete all 10 physical app/profile rows: one iPadOS and one Android device against each firmware profile.
• Pass deterministic-build comparison, provenance, dependency/SBOM/license, no-leak, DCO, evidence assembly, finalization, and public-tree validation.
• Publish only after every candidate-bound gate is green; retain no private identifiers in public evidence.

Current state

Source/specification/automated-test/HIL-runner/release-tooling implementation is complete on local branch firmware/v0.6.1-hardening. Physical execution and release publication remain deliberately unclaimed.