Release candidate: complete final parity, security, packaging, and clean-machine audit #107

New Issue

hugo · 2026-08-08T08:26:28Z

hugo commented

2026-08-08 08:26:28 +00:00

Objective

Cut and validate the first release candidate only after every milestone gate is satisfied.

Deliverables

Run full format/check/clippy/test/doc/fuzz-smoke/feature/platform/program suites and review all live/manual evidence.
Verify zero open milestone-owned implementation gaps, zero unimplemented shims, 100% API/test/program completeness, changelog/versioning, and signed/reproducible release artifacts as configured.
Perform clean-machine install, offline tools, fake-grid integration, and opt-in dedicated-account smoke.

Validation

All release gates and audits are green with recorded evidence.
No critical/open compatibility defect is waived silently.
Release notes clearly state supported platforms/features/native prerequisites and any documented intentional API differences.

Prerequisite

All implementation and program milestones are complete with their fixed parity suites green.

Project constraints

The released implementation is entirely native Rust and must pass the explicit no-CLR/no-bridge artifact audit.
Do not weaken API coverage or semantic parity to satisfy hardening, performance, or packaging goals.
Preserve reproducible evidence, update release documentation, and keep all default/live destructive boundaries explicit.

## Objective Cut and validate the first release candidate only after every milestone gate is satisfied. ## Deliverables - Run full format/check/clippy/test/doc/fuzz-smoke/feature/platform/program suites and review all live/manual evidence. - Verify zero open milestone-owned implementation gaps, zero unimplemented shims, 100% API/test/program completeness, changelog/versioning, and signed/reproducible release artifacts as configured. - Perform clean-machine install, offline tools, fake-grid integration, and opt-in dedicated-account smoke. ## Validation - All release gates and audits are green with recorded evidence. - No critical/open compatibility defect is waived silently. - Release notes clearly state supported platforms/features/native prerequisites and any documented intentional API differences. ## Prerequisite All implementation and program milestones are complete with their fixed parity suites green. ## Project constraints - The released implementation is entirely native Rust and must pass the explicit no-CLR/no-bridge artifact audit. - Do not weaken API coverage or semantic parity to satisfy hardening, performance, or packaging goals. - Preserve reproducible evidence, update release documentation, and keep all default/live destructive boundaries explicit.

hugo added this to the 12 - Hardening and release milestone 2026-08-08 08:26:28 +00:00

hugo added the enhancement label 2026-08-08 08:26:28 +00:00

hugo referenced this issue from a commit

2026-08-12 14:44:39 +00:00

Complete first release candidate audit (#107)

hugo referenced this issue from a commit

2026-08-12 14:57:11 +00:00

Repair Gitea release workflows (#107)

hugo referenced this issue from a commit

2026-08-12 15:03:42 +00:00

Restore the non-default OpenJPEG boundary (#107)

hugo referenced this issue from a commit