feat: add native read-only macOS experience

[karngyan]

Claim

Alpha PR 5 — the complete local loop (sessions, deterministic findings, mutation candidates, and their lifecycle audit) is now inspectable in a native macOS app without JSON output or a raw SQLite browser, and the app never writes the database.

apps/macos is a SwiftPM package (no Xcode required): a testable AutophagyKit library plus a thin SwiftUI executable. It builds and tests under the Command Line Tools with swift build / swift test, and a small script wraps the binary into a launchable .app.

What it does

• Read-only by construction. Every connection opens with SQLITE_OPEN_READONLY and sets PRAGMA query_only = ON; the app has no SQL write path.
• Onboarding + selection. Resolves the same default path as the CLI (~/Library/Application Support/sh.autophagy.Autophagy/autophagy.db), lets the user pick another .db, validates it is an Autophagy database, and remembers the choice in UserDefaults only.
• Views. Sessions + event timelines (exact event IDs); Patterns as the Evidence Packet preserved inside each registered candidate (exact supporting/counterexample IDs); Mutations with lifecycle state, evidence lineage, audit log, and read-only replay/shadow/installation records; a Privacy view showing on-disk location, schema compatibility, honest content counts, and the ingestion-time redaction/projection/retention posture.
• Schema tolerance. Classifies the database (supported / older-readable / newer-than-known / not-Autophagy) from user_version + schema_migrations, and checks table existence before each query so an off-version database degrades to empty views and a clear message instead of crashing.
• CLI-mediated deletion. Session and delete-all are delegated to the autophagy CLI behind multi-step confirmation (including the delete-all phrase mirroring the CLI guard). The exact command is shown and run via Process, or displayed when no binary is found.

Evidence

• swift test — 23 tests pass (swift-testing) covering:
  • read-only guarantee (a write is rejected on the app's connection);
  • schema tolerance (older, newer, and non-Autophagy databases handled without crashing);
  • session/event reads with exact event IDs, evidence-packet extraction, mutation detail (lineage + audit + package decode), rejection reason, orphaned-evidence flagging, and overview counts;
  • default-path resolution matching the CLI, CLI-command construction/quoting, binary location, and startup-path selection.
• swift build — exit 0 for both the library and the SwiftUI target.
• mise run check — exit 0 (Rust untouched; docs/actionlint/fmt/lint/test stay green, including the new guide and workflow).
• Smoke test. Imported evals/fixtures/** with the existing CLI into a demo database, then drove AutophagyKit against it: it reports schema v6 supported, 15 sessions, working event timelines, 3 findings, and 3 mutations. The SwiftUI executable launches and runs its event loop; the .app bundle produced by scripts/make-app-bundle.sh validates with plutil.

Privacy

The app is a read-only viewer: it opens a local database, sends nothing off the machine, adds no export path, and cannot mutate stored data. Deletion is delegated to the CLI, so the app never becomes an unaudited way to remove or leak evidence. Details in ADR docs/decisions/0005-macos-read-only-app.md.

Roadmap

Satisfies PR 5's exit criterion — "the complete local loop is inspectable without using JSON output or raw SQLite tools" — and marks that section complete.

🤖 Generated with Claude Code