@@ -55,6 +55,13 @@ jobs:
           cat > "$RUNNER_TEMP/notes.md" <<'NOTES'
           ## FigyTerm v__VERSION__
 
+          ### Updating
+
+          FigyTerm updates itself from here on — it checks for new versions and
+          installs them in-app, with no Gatekeeper prompt and no `xattr` step.
+          If you're coming from **v0.0.6 or earlier**, this one install is manual;
+          after it, updates are automatic.
+
           ### Installation (macOS)
 
           1. Download `FigyTerm___VERSION___aarch64.dmg` (Apple Silicon) or `FigyTerm___VERSION___x64.dmg` (Intel)
@@ -186,16 +193,108 @@ jobs:
         uses: tauri-apps/tauri-action@v1
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          # Minisign keypair for the updater. Unrelated to Apple code signing —
+          # it only lets installed clients verify an update came from us.
+          TAURI_SIGNING_PRIVATE_KEY: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY }}
+          TAURI_SIGNING_PRIVATE_KEY_PASSWORD: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY_PASSWORD }}
+          # Apple signing is optional and currently unset; tauri-action builds
+          # unsigned when these are absent. Present so enabling notarization
+          # later is a secret upload rather than a workflow change.
+          APPLE_CERTIFICATE: ${{ secrets.APPLE_CERTIFICATE }}
+          APPLE_CERTIFICATE_PASSWORD: ${{ secrets.APPLE_CERTIFICATE_PASSWORD }}
+          APPLE_SIGNING_IDENTITY: ${{ secrets.APPLE_SIGNING_IDENTITY }}
+          APPLE_ID: ${{ secrets.APPLE_ID }}
+          APPLE_PASSWORD: ${{ secrets.APPLE_PASSWORD }}
+          APPLE_TEAM_ID: ${{ secrets.APPLE_TEAM_ID }}
         with:
           releaseId: ${{ needs.create-release.outputs.release_id }}
           args: ${{ matrix.args }}
+          # The manifest is written by the updater-manifest job instead. With a
+          # two-target matrix, letting both builds upload latest.json races:
+          # whichever finishes last overwrites the other's entry, producing an
+          # updater that silently 404s for one architecture.
           uploadUpdaterJson: false
 
-  publish-release:
+  # Composes latest.json once, after both architectures have uploaded their
+  # updater artifacts, so it always describes both.
+  updater-manifest:
     needs: [create-release, build-macos]
     permissions:
       contents: write
     runs-on: ubuntu-latest
+    steps:
+      - name: Compose and upload latest.json
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          TAG: ${{ needs.create-release.outputs.tag }}
+          VERSION: ${{ needs.create-release.outputs.version }}
+          RELEASE_ID: ${{ needs.create-release.outputs.release_id }}
+        run: |
+          set -euo pipefail
+
+          # The release is still a draft here, so it must be addressed by id.
+          gh api --paginate "repos/$GH_REPO/releases/$RELEASE_ID/assets?per_page=100" \
+            > assets.json
+
+          PLATFORMS='{}'
+
+          for ARCH in aarch64 x64; do
+            case "$ARCH" in
+              aarch64) PLATFORM=darwin-aarch64 ;;
+              x64)     PLATFORM=darwin-x86_64 ;;
+            esac
+
+            TARBALL="FigyTerm_${VERSION}_${ARCH}.app.tar.gz"
+            SIG_ID=$(jq -r --arg n "${TARBALL}.sig" \
+              '.[] | select(.name == $n) | .id' assets.json | head -n1)
+
+            if [ -z "$SIG_ID" ]; then
+              echo "::error::${TARBALL}.sig is missing from the release. Is TAURI_SIGNING_PRIVATE_KEY set?"
+              exit 1
+            fi
+
+            SIG=$(gh api -H "Accept: application/octet-stream" \
+              "repos/$GH_REPO/releases/assets/$SIG_ID")
+
+            # Public download URL, valid once the release is undrafted.
+            URL="https://github.com/$GH_REPO/releases/download/$TAG/$TARBALL"
+
+            PLATFORMS=$(jq \
+              --arg k "$PLATFORM" --arg s "$SIG" --arg u "$URL" \
+              '. + {($k): {signature: $s, url: $u}}' <<<"$PLATFORMS")
+          done
+
+          jq -n \
+            --arg v "$VERSION" \
+            --arg d "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
+            --argjson p "$PLATFORMS" \
+            '{version: $v, notes: "See the release notes on GitHub.", pub_date: $d, platforms: $p}' \
+            > latest.json
+
+          cat latest.json
+
+          # Re-runs: drop the previous manifest so the upload doesn't collide.
+          OLD_ID=$(jq -r '.[] | select(.name == "latest.json") | .id' assets.json | head -n1)
+          if [ -n "$OLD_ID" ]; then
+            gh api --method DELETE "repos/$GH_REPO/releases/assets/$OLD_ID" >/dev/null
+          fi
+
+          curl -sSf -X POST \
+            -H "Authorization: Bearer $GITHUB_TOKEN" \
+            -H "Content-Type: application/json" \
+            --data-binary @latest.json \
+            "https://uploads.github.com/repos/$GH_REPO/releases/$RELEASE_ID/assets?name=latest.json" \
+            >/dev/null
+
+          echo "Uploaded latest.json for $TAG"
+
+  publish-release:
+    needs: [create-release, build-macos, updater-manifest]
+    permissions:
+      contents: write
+    runs-on: ubuntu-latest
     steps:
       - name: Undraft release
         env:
 
@@ -1,6 +1,6 @@
 # FigyTerm Update System — Design & Implementation Plan
 
-**Status:** Phase 1 implemented. Phases 2–3 planned.
+**Status:** Phases 1–2 implemented. Phase 3 planned.
 **Scope:** macOS only (Apple Silicon + Intel), distributed via GitHub Releases
 **Related:** `.github/workflows/release.yml`, `src-tauri/src/menu.rs`, `src/components/Settings/Settings.tsx`
 
@@ -568,17 +568,44 @@ waiver for nonprofits/educational institutions (unlikely to apply here, but it e
 - Release notes render to React elements with no HTML passthrough at all, so markup
   injection from a remote release body is structurally impossible.
 
-### Phase 2 — Auto-update
-- [ ] Generate + back up the minisign keypair
-- [ ] Add repo secrets
-- [ ] Add `tauri-plugin-updater`, `createUpdaterArtifacts`, `plugins.updater`, capability
-- [ ] Pass signing env to `tauri-action`
-- [ ] Add the `updater-manifest` job; keep `uploadUpdaterJson: false`
-- [ ] Download → progress → install → relaunch flow in the modal
-- [ ] Running-process guard before relaunch
-- [ ] Fallback to the Phase 1 manual flow on every failure path
-- [ ] **Verify on a real Mac:** no quarantine on updater-installed builds; detect
-      translocation / read-only bundle; test both architectures
+### Phase 2 — Auto-update ✅ implemented
+- [x] Generate the minisign keypair (`~/.tauri/figyterm.key`, mode 600, outside the repo)
+- [x] Add `tauri-plugin-updater`, `createUpdaterArtifacts`, `plugins.updater`, capability
+- [x] Pass signing env to `tauri-action`
+- [x] Add the `updater-manifest` job; keep `uploadUpdaterJson: false`
+- [x] Download → progress → install → relaunch flow in the modal
+- [x] Running-process guard before relaunch
+- [x] Fallback to the manual flow on every failure path
+- [ ] **Add the repo secrets** — `TAURI_SIGNING_PRIVATE_KEY` and
+      `TAURI_SIGNING_PRIVATE_KEY_PASSWORD` (empty). Until these exist the
+      `updater-manifest` job fails the release by design, rather than shipping a
+      release whose updater silently does nothing.
+- [ ] **Back up the private key** outside the machine. If it's lost, every
+      installed client stops accepting updates permanently.
+- [ ] **Verify on a real Mac after the first updater-enabled release:** an
+      updater-installed build carries no quarantine flag; both architectures
+      update; a translocated / read-only bundle falls back cleanly.
+
+**Files added:** `src/services/installer.ts`
+
+**Architecture:** discovery and install are deliberately separate. Discovery stays
+on the GitHub Releases API (Phase 1) because it yields rich release notes, dates,
+asset sizes and a prerelease flag — none of which `latest.json` carries. The
+updater plugin is used purely as the mechanism that swaps the bundle. That split
+is also what makes the fallback natural: if the plugin can't install (no manifest
+on old releases, `tauri dev`, a read-only bundle), the UI reveals the manual DMG
+path it already had.
+
+**Running-process guard:** `PtyInstance::foreground_pid()` compares the tty's
+foreground process group leader against the shell's own pid; when they differ the
+user is running something. `running_foreground_commands` resolves those pids to
+names via `sysinfo` so the warning can say *what* would be killed. Undeterminable
+is treated as idle — a false "busy" would block updating forever, while a false
+"idle" costs only a confirmation the user would have clicked through.
+
+**Bootstrapping:** only builds that already contain the updater plugin can
+auto-update, so v0.0.6 and earlier must install the first updater-enabled release
+by hand. The release-notes template says so.
 
 ### Phase 3 — First install (unsigned-permanent)
 - [ ] `install.sh` — arch detect, curl download, mount, copy, `xattr -cr`, detach, launch
 
@@ -14,6 +14,7 @@
     "@headlessui/react": "^2.2.10",
     "@tauri-apps/api": "^2.0.0",
     "@tauri-apps/plugin-shell": "^2.0.0",
+    "@tauri-apps/plugin-updater": "^2.11.0",
     "@xterm/addon-fit": "^0.10.0",
     "@xterm/addon-search": "^0.16.0",
     "@xterm/addon-unicode11": "^0.9.0",