Release checklist — version 1.0.0 (build 2)
State on 2026-11-21. A gate is marked ✓ only when a file proves it; partial when the evidence covers part of the claim, with the missing part named; ✗ when it is not done.
Evidence files quoted throughout:
test-results.json— engine tests: 582 tests, 85 suites, 10 targets,passed, 0 issues; interaction self-test: 19 scenarios, 19 passed, 0 failed; recovery:PASS: autosaved text survived SIGKILL.selftest-release.json— the 19 interaction scenarios recorded for the Release build: 19 passed, 0 failed. The file lists each scenario by name.coverage.json— engine line coverage 92.9 %.dist/release.json— not committed; its content is reproduced in distribution.md, signing.md and notarization.md.
The test report records totals, not the outcome of each test by name. Where a gate cites a named test, the proof is that the test exists in the sources and that the run as a whole passed with 0 issues.
Product gates
| # | Gate | Status | Evidence | Notes |
|---|---|---|---|---|
| 1 | Application builds | ✓ | dist/release.json (version 1.0.0, build 2, architectures x86_64 and arm64); Scripts/release.sh; the self-test ran inside the built application (test-results.json) |
The Intel slice is built, never run. |
| 2 | Rich text editing works | ✓ | selftest-release.json scenarios "typing, Return and Backspace", "Unicode typing deletes whole characters", "arrow keys, word and line movement", "undo, redo and select all", "bold shortcut applies to typed text", "copy, cut and paste through the pasteboard", "lists: …"; DocModelTests in test-results.json |
Events are synthesised in-process; the XCUITest suite was not run (testing.md). |
| 3 | Pagination validated | partial | Tests/DocLayoutTests/PaginationTests.swift; rule-by-rule table in pagination.md; scenario "page breaks create pages; many pages scroll with the caret" |
Rules without a test: space before and after, the footnote reserve, float registration and carried exclusions, lists of figures and tables. Layout is not compared with any other application. |
| 4 | Styles | ✓ | DocModelTests (character and paragraph formatting, style inheritance); DOCX feature check "styles": 19 documents, 699 instances, 19 pass, 0 fail (docx-compatibility.md); DocTemplatesTests |
The Styles inspector itself is covered by no automated interaction; it appears in 20-styles.png. |
| 5 | Tables | ✓ | Scenario "table: insert, type, Tab between cells, new row at the end"; DocModelTests (table editing, sorting, formulas); tablesSplitByRowsAndRepeatTheirHeader, mergedCellsCoverTheirGrid (pagination.md) |
Rows do not split across pages; no nested tables (limitations.md). |
| 6 | Images and figures | partial | imagesKeepTheirResolution (pdf.md); DOCX feature checks "images" and "image assets" 3 / 3 documents pass; floatingObjectsNarrowTheLinesBesideThem |
No interaction scenario inserts or resizes an image; float placement across pages has no pagination test (pagination.md). |
| 7 | Equations | ✓ | Tests/DocLayoutTests/MathRobustnessTests.swift (hostile and random LaTeX, valid equations typeset); MathConverterTests; DOCX feature check "equations" 3 / 3; DocMath coverage 100.0 % (coverage.json) |
A subset of LaTeX math (limitations.md). |
| 8 | Document saving reliable | ✓ | Tests/DocFormatsTests/NativeContainerTests.swift (lossless round trip, corruption detected, recovery) — see formats.md; scenario "save, reopen and autosave through NSDocument" |
Files larger than a few megabytes were not verified. |
| 9 | Autosave validated | ✓ | "recovery": "PASS: autosaved text survived SIGKILL" in test-results.json; Scripts/recovery-test.sh |
Scope: a saved document. Untitled documents, a kill during a write and power loss are not covered (persistence.md). |
| 10 | DOCX import/export tested | ✓ | docx-compatibility.md: 19 / 19 imported, model equal after both cycles 19 / 19, text integrity 100.00 %, 172 / 0 feature checks; pandoc, textutil and LibreOffice read the exports 19 / 19 |
Microsoft Word was not used. Small, mostly synthetic corpus; layout not measured. |
| 11 | Unsupported DOCX features disclosed | ✓ | compatibility/docx.md (feature tables with "Approximated" and "Not supported"); import warnings by document in docx-compatibility.md; limitations.md | Warnings are also shown in the app on open and before export (18-export-sheet.png). |
| 12 | PDF output validated | partial | Tests/DocLayoutTests/PDFTests.swift (pages, text extraction with PDFKit, links, outline, crop marks, page range; Poppler checks for embedded fonts and image resolution) — pdf.md |
No PDF/A or PDF/UA validator was run and no conformance is claimed. The report does not record whether the Poppler checks ran or were skipped. Tag structure is partial. |
| 13 | Comments and revisions | ✓ | Scenarios "track changes: insert, delete, accept and reject" and "comment anchored on the selection"; TrackChangesTests; DOCX feature checks for comments, replies and tracked insertions, deletions, format changes and paragraph marks, all pass |
What is not tracked is listed in text-engine.md. |
| 14 | Long-document performance measured | ✓ | benchmarks.json (487 pages, 177162 words) and benchmarks-100-pages.json (98 pages); meanings in performance.md |
Single runs, synthetic document, one machine; drawing and end-to-end typing latency are not measured. |
| 15 | No known release-blocking crashes | ✓ | test-results.json: 0 issues, 19 / 19; selftest-release.json: 0 failed; hostile-input tests listed in security.md |
"Known" means recorded in this repository: none is. The application has no crash reporting, and it was run on one Mac. |
| 16 | Privacy declarations accurate | ✓ | OnDeviceOnlyTests in Tests/DocAutomationTests/IntelligenceTests.swift; empty ORIXDocs.entitlements; security.md |
The no-network test scans five source folders; for the rest of the sources the statement rests on a search made on 2026-11-21, not on a test. |
| 17 | Accessibility reviewed | partial | accessibility.md | Review by code inspection only. No VoiceOver session with a listener; Reduce Motion and Increase Contrast not handled. |
| 18 | Icon assets valid | ✓ | App/Resources/Assets.xcassets/AppIcon.appiconset (seven PNG files, 16 to 1024 px, ten slots in Contents.json, each with a file); icon-design.md; AppIcon.icns present in the built bundle |
Pixel sizes were checked with sips on 2026-11-21. |
| 19 | README complete | ✓ | README.md: 38 sections, 22 screenshots, 10 diagrams; relative links and image paths checked on disk |
Its rendering on the SPB Git website is not verified (gate 26). |
Release gates
| # | Gate | Status | Evidence | Notes |
|---|---|---|---|---|
| 20 | SPB Git repository verified | ✓ | Public repository https://git.spboucher.ai/orix-docs (published 2026-11-21); git ls-remote matches the local main; private copy on gitsrv:srv/git-private/orix-docs.git |
|
| 21 | Developer ID signature valid | ✓ | dist/release.json field signing: "Developer ID Application: Simon-Pierre Boucher (3YM54G49SN)"; signing.md |
Hardened runtime, empty entitlements, no get-task-allow. |
| 22 | Notarization accepted | ✓ | dist/release.json: application 5cbffb9c-d031-4702-81c6-ecb0d1068eca Accepted; disk image 794c8ee7-f0ef-491f-b7cc-7ab911771eca Accepted; notarization.md |
Both stapled. |
| 23 | Gatekeeper validation passes | ✓ | dist/release.json field gatekeeper: "accepted, source=Notarized Developer ID" for the application and the disk image |
Assessed on the build machine. |
| 24 | Distribution artifacts verified | partial | distribution.md: sizes, checksums, bundle content, stapling | Verified on the build machine only. No clean second Mac; the Intel slice never run; macOS 15 to 26 not tested. |
| 25 | Release checksums match | ✓ | dist/SHA256SUMS.txt equals the sha256 fields of dist/release.json; shasum -a 256 -c SHA256SUMS.txt answered OK for both files on 2026-11-21 |
Values in distribution.md. |
| 26 | SPB Git release verified | ✓ | Release v1.0.0 at https://git.spboucher.ai/orix-docs/releases; assets downloaded back: checksums match, DMG stapled, Gatekeeper accepts (see RELEASE-REPORT.md §9) |
Not done, in one place
| Item | Where it is described |
|---|---|
| XCUITest suite not run (Automation Mode needs the owner's authentication) | testing.md |
| Microsoft Word never used to validate DOCX | compatibility/docx.md |
| No PDF/A or PDF/UA validation | pdf.md |
| Shortcuts actions never run from Shortcuts | automation.md |
| AppleScript deferred | automation.md |
| Automatic updates not implemented | distribution.md |
| VoiceOver not tested with a listener; Reduce Motion and Increase Contrast not handled | accessibility.md |
| Grammar checking and autocorrection not implemented | text-engine.md |
| Clean second Mac and Intel hardware not used | distribution.md |
Publication on SPB Git and the v1.0.0 release |
distribution.md |
To do when publication is authorised
- Push the repository to SPB Git and create the release
v1.0.0withORIX-Docs-1.0.0.dmg,ORIX-Docs-1.0.0.zipandSHA256SUMS.txt. - Download each asset from the release page and compare its SHA-256 with distribution.md.
- Open the README on the forge: check the badges, the ten Mermaid diagrams, the 22 screenshots and the HTML tables.
- Update gates 20 and 26 and the Release Status table of the README.