CoreTend 0.9.1-rc.3 (superseded)

Superseded / Remplacée

This release remains available for historical verification, but 0.9.1-rc.4 is now the recommended release candidate. Its original files and checksums are unchanged.

Cette release reste disponible pour la vérification historique, mais 0.9.1-rc.4 est désormais la version candidate recommandée. Ses fichiers et empreintes d’origine restent inchangés.

---

CoreTend 0.9.1-rc.3 (release candidate)

This release candidate supersedes 0.9.1-rc.2. It is not a stable 1.0.

Why rc.3 exists. Two defects made the rc.2 download unusable for someone
installing CoreTend for the first time. rc.2's files are left exactly as they
were published — replacing them would break any checksum already recorded —
and this is a new build from the current source.

The first launch now has a route that works

CoreTend is unsigned and not notarized, so macOS blocks it the first time. That
has always been true and is expected: no Apple Developer identity exists for
this project.

What was broken is the way out. Every instruction we published — the site, the
README, the install guide — told you to Control-click the app and choose
Open. Apple removed that override in macOS 15 Sequoia. On macOS 15 and
later it silently does nothing, so the app appeared to be simply broken, with
no documented way forward. That is the reported "it did not work on another
Mac", and it was a documentation defect, not a crash.

The correct route is now everywhere:

1. Copy CoreTend to /Applications and double-click it once. macOS blocks it —
   this is expected, and it is what makes the next step appear.
2. Open System Settings → Privacy & Security, scroll to Security, and
   choose Open Anyway. Confirm with Touch ID or your admin password.
3. Once per copy is enough.

On macOS 14 and earlier, Control-click → Open still works.

Never disable Gatekeeper, and do not run a blanket quarantine-removal command.
The per-app step above is all that is needed.

The installer window looks like an installer again

The DMG shipped without its .DS_Store, so the volume opened as a plain Finder
window: no background, no icon placement, and three loose licence files to read
past. The window layout was being written by driving the Finder over
AppleScript, which needs an Automation permission a build cannot assume — and
when that permission was missing, the build only warned and published anyway.

• The layout is now generated deterministically, with no Finder, no
  AppleScript, no Automation grant and no graphical session. It builds the same
  way locally, in a non-interactive shell and in CI.
• A DMG without its layout fails the build. There is no opt-out.
• The background is redrawn on the same paper/ink/cobalt palette as the
  website, and ships at both standard and Retina resolution.
• The volume now contains exactly two visible items: CoreTend.app and the
  Applications shortcut. The licence texts moved inside the app bundle.

Verification and testing

• The mounted image is checked on every release: background and both
  resolutions, window bounds, view style, icon size, both icon coordinates, no
  stray visible files, licence texts sealed inside the bundle with the
  signature intact.
• The DMG is built from a clean clone with the Finder quit on every push.
• 37 launch-robustness cases run under a fully isolated HOME and store: missing
  and unwritable directories, empty/truncated/corrupt preferences and database,
  ClamAV absent or broken, no network, invalid update manifests, Unicode and
  emoji and very long paths, symlink cycles, unreadable trees, 3000 files,
  relaunch after a hard kill during startup, plus 50 cold launches and 50
  launch/quit cycles.

Still true

Unsigned and not notarized. Minisign signatures and the provenance attestation
prove the files came from this repository's workflow; they are not Apple
code signing and not notarization, and they do not stop Gatekeeper from
blocking the first launch. Apple silicon, macOS 14 or later.