Unpin v1.1.0

Unpin v1.1.0

v1.1.0 adds verified self-updates to the CLI and native macOS workbench and
makes native dashboard screenshots part of the provider-matrix workflow on
macOS.

Highlights

• unpin update check discovers the latest stable GitHub release without
  changing files, and unpin update apply installs only the exact version the
  user confirms.
• The desktop app checks for updates at launch and through Check for
  Updates…, then confirms installation before replacing and relaunching the
  app.
• Downloads are host-restricted and bounded; archives are checksum-verified and
  traversal-safe, and candidates must report the expected version before
  atomic replacement.
• macOS candidates must retain the exact app, bridge, and CLI identifiers and
  byte-for-byte designated requirements of the installed release. Certificate
  or identifier rotation is rejected rather than resetting an existing
  Keychain Always Allow grant.
• scripts/run_local_provider_matrix.py --capture-screenshots captures the
  native provider-matrix dashboard on macOS. Capture is enabled automatically
  on macOS and has a documented manual fallback elsewhere.

Upgrading from v1.0.2

v1.0.2 does not contain the updater, so installing v1.1.0 is a final manual
upgrade. Both releases use the same stable certificate and identifiers, so the
replacement preserves the designated requirements and existing Keychain
Always Allow grants. Compatible releases after v1.1.0 can use the built-in
CLI or desktop update flow.

Artifacts

The release provides three CLI archives and two native desktop archives:

• unpin-v1.1.0-aarch64-apple-darwin.tar.gz
• unpin-v1.1.0-x86_64-apple-darwin.tar.gz
• unpin-v1.1.0-x86_64-unknown-linux-gnu.tar.gz
• unpin-desktop-v1.1.0-aarch64-apple-darwin.tar.gz
• unpin-desktop-v1.1.0-x86_64-apple-darwin.tar.gz

Every archive has a CycloneDX SBOM, GitHub build-provenance and SBOM
attestations, and an entry in SHA256SUMS.

Trust boundary

The stable personal certificate preserves code identity for Keychain access;
it is not an Apple Developer ID certificate and the artifacts are not
notarized. It therefore does not establish Gatekeeper trust. Verify checksums
and GitHub attestations before using Finder's Control-click Open flow. Do
not disable Gatekeeper or strip quarantine metadata. The release uses timestamp
mode none and does not claim secure timestamping for the personal self-signed
certificate. Full instructions are in the desktop guide, and
certificate expiry and rotation are covered in the release
guide.

Verification

This is an ordinary program release. Publication remains blocked until the
exact merged release commit passes the locked Rust workspace checks, macOS
XCTest suite, live Pi and OpenCode validation, and finalized provider matrix;
the draft artifacts must then pass complete checksum, attestation, stable
signature, exact-identifier, designated-requirement, bridge-handshake, and
fresh-download verification. The approved provider-matrix evidence bundle is
attached before publication.

Known limitations

• No Developer ID signing or notarization.
• Desktop support remains macOS-only and architecture-specific.
• Certificate or identifier rotation requires a separately documented manual
  installation and one new Keychain authorization.
• Native provider-matrix screenshot capture requires macOS; other platforms use
  the documented manual dashboard workflow.
• Profiles, gateways, sessions, and hooks remain on CLI, TUI, and MCP surfaces.
• crates.io, Homebrew, Linux ARM64, and Windows distribution remain deferred.