Record 0.3.x release qualification and resolve capacity handoff

PR #183 is merged and tag 0.3.0 names c21afcd05ee8ac984ced905a0a1bf822dca1ddcf.
The owner-authorized release is publishing in workflow 34678413630.

Finish delivery by checking the actual published x86_64 package with both-camera
installed UI and active-playback capacity runs, authenticating the public signed
channel's version/ref/commit for both architectures, and recording the exact
package identities and remaining limits in the current roadmap/release record.
Do not treat branch-package acceptance or a green build as this release check.

The locally installed test origin points to a scratch repository with GPG checks
disabled; final delivery must not mistake that for the signed public channel.
Retain the accepted branch bundle for recovery and retain private evidence in
worktree scratch paths, never /tmp or public release assets.

Make the already-validated source-regeneration-plus-player release hook durable
in release.toml so future Cargo.lock version transactions obey AGENTS.md without
requiring a one-off scratch config. No stitching arithmetic or cadence change.

Owner acceptance and stronger outstanding limits remain in #183, #185, #186
and #88. This task does not reopen broad reverse engineering.

Begin with `release.toml` and `AGENTS.md` to confirm how the source-regeneration-plus-player hook should be made durable for future `Cargo.lock` handling. Next inspect workflow `34678413630` and verify the actual public signed-channel x86_64 releases for both architectures (version/ref/commit, both-camera installed UI, active-playback capacity). Capture private evidence in worktree scratch paths (not `/tmp`), retain the accepted branch bundle, and mark done by updating the roadmap/release record with exact package identities and remaining limits.

Escrita pelo modelo de indexação a partir do texto da issue.