Record 0.3.x release qualification and resolve capacity handoff
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 4
Description
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.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.