Repository Public
1# Distribution23How the signed application becomes downloadable artifacts, where the source lives, and which steps4are deliberately not automated because they need the owner's authorization.56Chain: [signing](signing.md) → [notarization](notarization.md) → this document. Gates:7[release checklist](checklist.md).89**State on 2026-11-21:** a signed Release bundle, `dist/ORIX Sheet.app`, was produced by10`Scripts/sign.sh`: universal (`x86_64 arm64`), Developer ID Application, hardened runtime, no11`get-task-allow`, with the `orix-sheet` command-line tool embedded at `Contents/MacOS/orix-sheet`12and `libduckdb.dylib` in `Contents/Frameworks`, both re-signed (details in [signing](signing.md)).13The record of the release run — notarization, stapling, artifact sizes, checksums and the14Gatekeeper assessments — is `RELEASE-REPORT.md` at the repository root; this document describes15the mechanism and does not repeat those results.1617## Artifacts1819| Artifact | Built by | Content |20|---|---|---|21| `dist/ORIX Sheet.app` | `Scripts/sign.sh` | universal app, Developer ID, hardened runtime; contains the `orix-sheet` tool (`Contents/MacOS/orix-sheet`) and `Contents/Frameworks/libduckdb.dylib` |22| `dist/ORIXSheet-<version>.zip` | `Scripts/package.sh` | `ditto -c -k --keepParent` archive of the app |23| `dist/ORIXSheet-<version>.dmg` | `Scripts/package.sh` | compressed disk image with the app and an Applications link, signed |24| `dist/ORIXSheet-<version>.sha256` | `Scripts/notarize.sh` | `shasum -a 256` of the DMG and the ZIP |2526Source: `Scripts/package.sh`, `Scripts/notarize.sh`.2728`<version>` is `CFBundleShortVersionString` read from the app's `Info.plist` (`1.0.0` in29`project.yml`). The build number is not part of the file name. `dist/` and `build/` are ignored by30git: artifacts are never committed.3132## `Scripts/package.sh`3334```bash35Scripts/package.sh # normally called by Scripts/notarize.sh after the app is stapled36```37381. Stops if `dist/ORIX Sheet.app` is missing.392. Reads the version; removes any previous DMG and ZIP of that version.403. **ZIP:** `ditto -c -k --keepParent "dist/ORIX Sheet.app" "dist/ORIXSheet-<version>.zip"`.41 `ditto` preserves the bundle's extended attributes and symbolic links, which a plain `zip` does not.424. **Background:** uses `design/dmg/background.png`; if the file is missing it is regenerated with43 `swift design/dmg/make-background.swift design/dmg`.445. **DMG, preferred path:** if `create-dmg` is installed, it is called with:4546 | Option | Value |47 |---|---|48 | Volume name | `ORIX Sheet <version>` |49 | Window | position 200, 140; size 660 × 420 |50 | Icon size | 112 |51 | App icon position | 170, 205 |52 | Applications drop link | 490, 205 |53 | Other | `--hide-extension "ORIX Sheet.app"`, `--no-internet-enable` |5455 Source: `Scripts/package.sh`.5657 Its output is discarded and its failure is tolerated (`>/dev/null 2>&1 || true`).586. **DMG, fallback:** if no DMG exists after step 5, the script prints59 `create-dmg unavailable or failed: building a plain disk image`, adds an `/Applications` symlink60 to the staging directory and runs `hdiutil create -format UDZO`. This image has no background61 and no icon layout.627. **Signing the DMG:** the identity is read back from the app's own signature (the63 `Authority=Developer ID Application: …` line of `codesign -dvv`). If found, the DMG is signed64 with `codesign --force --timestamp`. If the app is not Developer ID-signed, the DMG is left65 unsigned without an error.668. Prints the size and path of both files.6768`create-dmg` 1.3.0 is installed on the build machine (`/opt/homebrew/bin/create-dmg`, observed692026-11-21). `create-dmg` arranges the window through Finder scripting, so the preferred path needs70a logged-in graphical session; on a headless run the fallback applies.7172Two details worth knowing:7374- The header comment of `package.sh` describes the ZIP as "the signed, stapled app". That is true75 only when the script is called from `notarize.sh` after stapling. Run on its own after `sign.sh`,76 it archives an app without a ticket.77- The staging copy is made in a `mktemp -d` directory and removed at the end; on an error under78 `set -e` it is left behind in the temporary directory.7980## Disk-image artwork8182`design/dmg/make-background.swift` (33 lines, AppKit/CoreGraphics) draws83`design/dmg/background.png`:8485| Property | Value |86|---|---|87| Pixel size | 1320 × 840 (the 660 × 420 pt window at 2x; the PNG is tagged 660 × 420 pt) |88| Background | vertical gradient `#16233F` → `#0B0F1E`, radial glow `#1E6A8A` at 55 % from the top-left |89| Grid | faint sheet grid, white at 3.5 %, every 110 px horizontally and 56 px vertically |90| Arrow | cyan `#22D3EE` at 90 %, between the two icon positions (y = 205 pt) |91| Text | "ORIX Sheet" (56 px bold, white), "Beyond Spreadsheets." (26 px medium, cyan), "Drag ORIX Sheet to the Applications folder" (26 px, white at 72 %) |9293Source: `design/dmg/make-background.swift`; pixel size confirmed with `sips` (file size 886,139 bytes).9495The text of the background is English only. The icon positions in `package.sh` and the arrow96coordinates in the generator are two independent literals: change them together.9798## Verifying a download99100```bash101cd dist && shasum -a 256 -c ORIXSheet-1.0.0.sha256102xcrun stapler validate ORIXSheet-1.0.0.dmg103spctl --assess --type open --context context:primary-signature --verbose=2 ORIXSheet-1.0.0.dmg104```105106The checksum file is produced next to the artifacts and proves integrity only against an107accidental change; it is not signed separately. Authenticity comes from the Developer ID signature108and the notarization ticket.109110## Where the source lives111112| Fact | Value | Observed with |113|---|---|---|114| Remote `origin` (fetch and push) | `gitsrv:srv/git-private/orix-sheet.git` | `git remote -v` |115| Branch | `main`, tracking `origin/main` | `git status -sb` |116| Last commit on 2026-11-21 | `1a190fd` ("release: 1.0.0 (1) signed, notarized and packaged; release report, facts and badges") | `git log --oneline -1` |117| Bare repository on the host | `srv/git-private/orix-sheet.git` exists; `srv/git/orix-sheet.git` does not | `ssh gitsrv ls -d …` (read-only) |118| Files tracked | 1,071 | `git ls-files \| wc -l` |119| Tags | `v1.0.0-build1` | `git tag` |120121Source: read-only git and ssh commands run on 2026-11-21. `gitsrv` is an SSH host alias defined in122the developer's SSH configuration, not in this repository.123124Why a path outside the forge: the SPB Git forge serves the bare repositories under `srv/git/`, and125it has no notion of a private repository — everything in that directory is publicly listed. ORIX126Sheet's source is not meant to be public, so its bare repository sits in a sibling directory,127`srv/git-private/`, on the same host, reachable only over SSH with the developer's key. The listing128above confirms the location; that the forge does not expose `srv/git-private/` is a property of the129forge's configuration, which this repository does not contain and this document did not test.130131Consequences:132133- There is **no web page, issue tracker or release page** for ORIX Sheet on the forge. Nothing in134 the repository publishes an artifact anywhere.135- Access to the source is by SSH to that host; cloning needs an authorized key.136- Third-party binaries are not in git: DuckDB is downloaded by `Scripts/fetch-duckdb.sh` from the137 project's GitHub release (`v2.0.1`, pinned SHA-256) on the first build. A fresh clone therefore138 needs network access once.139140## Steps that require the owner's authorization141142None of the following is performed by a script without an explicit command from the owner. Whether143each was performed for a given release is recorded in `RELEASE-REPORT.md`, not here:144145| Step | Why it needs the owner |146|---|---|147| `Scripts/notarize.sh` | uploads the application to Apple under the owner's developer account (keychain profile `MacLustr-Notarize` by default) |148| `git push` to `origin` | publishes commits to the private repository; `Scripts/secret-scan.sh` is to be run first |149| Making any artifact downloadable (a release page, a website link, sending the DMG to someone) | no public location exists for this project; choosing one is a product decision. If a public forge repository were created for releases, it would be public in full |150| Tagging a release | one tag exists, `v1.0.0-build1` (`git tag`); creating or moving a tag is the owner's decision |151| An update feed | Sparkle 2 is "the candidate" but "not included in 1.0": it needs a hosted, signed appcast and a key-management decision (`docs/research/technology-evaluation.md`). The app has no updater and performs no update check |152| Mac App Store submission | not prepared: the app is not sandboxed and has no App Store configuration |153154Source: `Scripts/notarize.sh`, `Scripts/secret-scan.sh`, `docs/research/technology-evaluation.md`, `project.yml`.155156## Not implemented157158- No automatic upload, no release notes generator, no appcast, no licence or EULA shown in the DMG.159- No separate arm64-only artifact: the Release configuration is universal (`arm64 x86_64`).160- No dSYM archive is kept by the scripts.161- `RELEASE-REPORT.md` is the record of the actual release run and takes precedence over this162 document for results (notarization, checksums, Gatekeeper).163