Repository Public License
1<!-- ORIX Clean / File: docs/release/checklist.md / Author: Simon-Pierre Boucher / Contact: contact@spboucher.ai -->2# Release checklist34Quality gates for a release of ORIX Clean. Copy this list for each release and tick the boxes as each gate is5actually passed, with the evidence (command output, submission id, checksum) kept next to it. All boxes are6unchecked here on purpose: this file is the template, not a record.78Release: `____________` Version / build: `______ (____)` Date: `____________` Machine: `____________`910## 1. Source state1112- [ ] Working tree is clean and committed; the commit to release is identified.13- [ ] `MARKETING_VERSION` and `CURRENT_PROJECT_VERSION` in `project.yml` are set for this release.14- [ ] `Scripts/check.sh` prints `clean`: author headers present, no signing material, no credentials, no15 network code, no privilege-escalation or private-API markers.16- [ ] `App/ORIXClean.entitlements` is still an empty dictionary.17- [ ] `ENABLE_APP_SANDBOX: NO`, `ENABLE_HARDENED_RUNTIME: YES` and the macOS 15.0 deployment target are18 unchanged in `project.yml`, or the change is intended and documented.1920## 2. Localization2122- [ ] `python3 Scripts/localize.py` succeeds: no `MISSING` key and no `PLACEHOLDERS DIFFER` line.23- [ ] Every new string was reviewed in French (fr-CA), including the five privacy usage descriptions.24- [ ] The application was launched once in French and once in English and the main sections were looked at25 for truncation.2627## 3. Tests2829- [ ] `Scripts/build.sh core-test`: all core tests pass. Number of tests executed: `____`.30- [ ] `Scripts/build.sh debug`: `** BUILD SUCCEEDED **` with no new warnings.31- [ ] `Scripts/build.sh uitest` on an otherwise idle machine: all 8 scenarios pass.32- [ ] Any UI test failure was rerun alone (`ORIX_ONLY=<name>`) and explained (focus theft or real regression).33- [ ] `/tmp/orix-uitest` is detached and `/tmp/orix-uitest.dmg` is gone after the run.3435## 4. Safety review3637- [ ] No change weakens `SafetyPolicy`; any new rule has a test in `SafetyPolicyTests`.38- [ ] `CleanupAuthorization` is still created in exactly one place in Release code (`AppModel.confirm`).39- [ ] Every new catalogue rule has a reason, a consequence and a regeneration note (`everyRuleIsDocumented`).40- [ ] No list preselects items; permanent deletion is still limited to Trash items and requires typing41 `DELETE`.42- [ ] Manual pass on the sample folder (`orix-bench fixture` in `/tmp`): select, preview, cancel, confirm,43 Put Back, and one workflow with the review declined.44- [ ] Manual pass with Full Disk Access off, then on: unreadable folders are reported, the Trash banner45 appears and disappears, nothing crashes.4647## 5. Performance and accuracy4849- [ ] `orix-bench scan` on a large folder: the allocated total equals `du -sk` on a tree that is not changing.50- [ ] Scan throughput and memory per object are in line with `docs/development/performance.md`; any51 regression is explained.52- [ ] If numbers in the documentation were updated, they are measurements with their environment stated.5354## 6. Accessibility5556- [ ] Full keyboard pass: every section reachable, cleanup preview operable, shortcuts work.57- [ ] VoiceOver pass over the sidebar, the list beside the storage map, a candidate list and the cleanup58 preview. Result recorded honestly in `docs/ACCESSIBILITY.md`.59- [ ] Light and dark appearance, both map palettes, Reduce Motion and Increase Contrast looked at.6061## 7. Build and signing6263- [ ] `Scripts/sign.sh` ends with `RESULT: … is built and signed`.64- [ ] `codesign --verify --deep --strict --verbose=2 "dist/ORIX Clean.app"` succeeds.65- [ ] `codesign -dvv` shows the expected `Developer ID Application` authority, team identifier and a timestamp.66- [ ] Flags include `runtime`; entitlements are empty; no `get-task-allow`.67- [ ] `lipo -archs` lists both `arm64` and `x86_64`.68- [ ] Bundle identifier is `ai.spboucher.orix.clean`; version and build match section 1.6970## 8. Notarization7172- [ ] `Scripts/notarize.sh` ends with `RESULT: dist/ORIX Clean.app is notarized by Apple (submission …) and73 stapled.` Submission id: `____________`.74- [ ] `Scripts/package.sh` built the DMG with artwork (no "falling back to a plain image" message) and the ZIP.75- [ ] `Scripts/notarize.sh dist/ORIXClean-<version>.dmg dmg` ends with the notarized-and-stapled result.76 Submission id: `____________`.77- [ ] `xcrun notarytool info <id>` reports `Accepted` for both submissions.78- [ ] `package.sh` was **not** run again after the DMG was notarized.7980## 9. Final verification8182- [ ] `Scripts/finalize.sh` completes: Gatekeeper accepts the application, the image and the application83 extracted from the ZIP; `stapler validate` succeeds on all three.84- [ ] `dist/SHA256SUMS.txt` and `dist/release.json` exist; version, build, minimum macOS and architectures in85 `release.json` are correct and both submission ids are non-empty.86- [ ] On a second Mac that never saw the build: download, verify the checksum, open the image, install,87 launch. The first-launch dialog is the standard one for a notarized application.88- [ ] On that Mac: onboarding appears, a scan of a folder completes, one item is moved to the Trash and put89 back.90- [ ] Intel Mac and macOS 15 / 26 smoke test done, or the release notes state that they were not run.9192## 10. Documentation9394- [ ] `docs/release/RELEASE_NOTES.md` describes this version and its known limitations.95- [ ] `README.md` and `RELEASE-REPORT.md` are updated by their owner.96- [ ] `docs/PRIVACY.md` still matches what the application reads and stores.97- [ ] Capability matrix and architecture documents updated for any behaviour that changed.98- [ ] No document claims a signature, notarization, measurement or test result that was not obtained for this99 release.100101## 11. Publication102103- [ ] Artifacts uploaded: DMG, ZIP, `SHA256SUMS.txt`.104- [ ] The published checksums equal those in `dist/SHA256SUMS.txt`.105- [ ] The download was fetched back from its public location and verified once more with `shasum` and `spctl`.106- [ ] The release commit is tagged.107- [ ] No credential, keychain profile content or private path appears in anything published.108109## 12. After release110111- [ ] `build/notary/*.json` and the notary logs are archived with the release evidence.112- [ ] Follow-up issues opened for every gate that was passed with a stated exception.113