@@ -11,7 +11,7 @@
 Modex is an open, Codex-App-style desktop app for running coding agents in your local
 repositories. It drives **Claude Code** and **Codex** through their own CLIs (`claude -p`
 stream-json and `codex app-server`), using existing CLI logins or app-owned ChatGPT sign-in.
-App-owned sign-in is under review; see [its acceptance gates](docs/chatgpt-signin.md).
+App-owned sign-in shipped in v0.0.6; see [how it works and its limits](docs/chatgpt-signin.md).
 It never calls a model
 API directly. App-owned ChatGPT credentials use protected OS-encrypted storage; existing
 Claude and Codex CLI credentials remain with their CLIs.
@@ -165,8 +165,11 @@ skills exactly as it would in a terminal.
 ### Run it
 
 For macOS on Apple Silicon, download the DMG or ZIP from the
-[latest release](https://github.com/TypeSafeAI/modex/releases/latest). Replace the existing
-app to upgrade; projects, threads, and preferences remain in `~/.modex`. Builds from v0.0.5
+[latest release](https://github.com/TypeSafeAI/modex/releases/latest). From v0.0.12 the app
+updates itself (see [Release notifications](#release-notifications)); earlier builds upgrade by
+replacing the app. Projects, threads, and preferences remain in `~/.modex`. The same page has
+unsigned Windows x64 and Linux x64 installers from v0.1.0, which update manually; see
+[native platforms](docs/native-platforms.md). Builds from v0.0.5
 are signed with a Developer ID and notarized by Apple, so they open without a Gatekeeper
 warning; v0.0.1–v0.0.4 were ad-hoc signed and need a right-click → Open the first time. You
 still need `claude` or `codex` installed and logged in. To check a download yourself, see
@@ -210,10 +213,10 @@ Starting with v0.0.7, installed macOS builds check for a newer stable release at
 workspace is visible, with a check when you return to it. A small banner links to the
 release page; dismissing it hides that version across relaunches. A later release appears
 again. Checks use public GitHub release metadata and require an uploaded installer for
-your Mac. Offline failures stay quiet. Published builds still require manual downloads and
-installation. The in-flight [automatic update and durable-draft work](docs/update-recovery.md)
-adds verified preparation and recovery and has passed local integration checks. Signed native
-acceptance and release approval remain required before publication.
+your Mac. Offline failures stay quiet. From v0.0.12 the banner also offers **Download update**:
+Modex verifies the archive and its publisher, then offers **Restart to update** and keeps your
+drafts. Builds before v0.0.12 install it manually once. Windows and Linux show no update banner;
+install a newer release by hand. See [update preparation and draft recovery](docs/update-recovery.md).
 
 If you are on v0.0.6 or earlier, install v0.0.7 from the release page once to enable future
 update notifications; older builds do not contain the banner.
@@ -268,13 +271,13 @@ must be public for the rules to apply.
 
 ## Not (yet) here
 
-Codex Cloud tasks and scheduled automations remain deferred until local readiness. Automatic
-update installation and public Windows/Linux installers still need their release gates;
-[native installer candidates](docs/native-platforms.md) already have bounded acceptance
-evidence. Modex has no HTTP-API execution mode;
-if a CLI is not installed or logged in, the thread says so.
+Codex Cloud tasks stay out of scope. Read-only [routines](docs/routines.md) are on `main`,
+unreleased; routines that change code wait on the approval gate decision. Windows and Linux
+installers ship from v0.1.0, and their [acceptance gaps](docs/native-platforms.md) are still
+open. Modex has no HTTP-API execution mode; if a CLI is not installed or logged in, the thread
+says so.
 
-## Images and Plugins (unreleased)
+## Images and Plugins
 
 The full desktop app includes local image imports and a native Claude Code/Codex plugin manager.
 Compatible image skills can generate and revise images through the existing CLI runner, with
 
@@ -21,7 +21,7 @@ counts. Prompts, files and replies are never recorded.
   unpriced rather than free.
 - **Recording is best-effort.** A failed write is logged and never changes the turn. Reading skips lines that
   don't parse, so a torn last line after a crash costs one row.
-- Usage from before this release, from other tools, and from outside Modex is not imported.
+- Usage from before v0.1.0, from other tools, and from outside Modex is not imported.
 
 ## How it is shown
 
@@ -121,7 +121,7 @@ mobile navigation after desktop collapse, Copilot filtering, unknown costs,
 account attribution, and a real CSV download. Browser interaction checks
 complement these; they do not constitute VoiceOver or human keyboard-only acceptance.
 
-Safari verification on 2026-10-07 covered both appearances, navigation, empty
+Before the #248 restyle, Safari verification on 2026-10-07 covered both appearances, navigation, empty
 search, custom dates, call details, and exact project drill-downs. Phone and
 tablet iframe checks (390 and 768 CSS pixels including scrollbars) confirmed no
 page-level horizontal overflow. CSV serialization tests pass; Safari displayed
 
@@ -6,7 +6,7 @@ tools themselves, create approval requests the CLI did not make, or widen a sand
 The gate remains **off** while this integration is reviewed. Settings can save rules and
 **Try it** can preview their decisions during this period. Rules do not answer live approvals;
 the existing thread policy still applies (Ask each time, Always allow, or YOLO).
-This editor follows v0.0.6 and is not included in its replacement release tag.
+The editor shipped in v0.0.7.
 See the [specification](specs/2026-10-01-modex-jev-approval-rules-spec.md).
 
 ## Add a rule
 
@@ -26,8 +26,8 @@ calibrated probabilities. Modex asks six questions in one request
 | `needs_deep_reasoning` | noul | doing it well needs multi-step reasoning about interactions |
 | `depends_on_prior_turns` | noul | only when the thread has history: the request leans on it |
 
-The state sent is the request (clipped to 4k chars), the last six turns as short digests
-(user/assistant text clipped, tool titles), and thread/project facts (backend, mode, plan,
+The state sent is the request (clipped to 4k chars), the last six transcript entries (user
+text clipped, a placeholder for each assistant reply, tool titles), and thread/project facts (backend, mode, plan,
 turn count, project name, branch). No file contents, diffs, or tool output are sent.
 
 ## Key and transport
@@ -51,16 +51,16 @@ locked vault as the problem rather than silently judging with the heuristic.
 
 The judge itself is reached one of two ways (Settings → Judge transport):
 
-- **`jev` CLI** (default when installed): Modex runs `jev run - --raw` with the payload on
-  stdin and the resolved key in the child's environment only. That gives Modex the CLI's
-  config, its retries, its error messages, and `jev doctor`, and keeps one code path for
+- **`jev` CLI** (default when installed): Modex runs `jev run - --raw --compact --attempts 1`
+  with the payload on stdin and the resolved key in the child's environment only. That gives
+  Modex the CLI's config, its error messages, and `jev doctor`, and keeps one code path for
   people, scripts, and agents. Install with `npm link` in `TypeSafeAI/cli`.
 - **Built-in HTTPS** (`POST https://api.typesafe.ai/v1/systemone`): the same request from
   Modex's own process, used when the CLI is absent or the policy says so.
 
 Transport selection is explicit: **Auto** prefers the CLI and may fall back to HTTPS;
-**Always the jev CLI** never uses HTTPS if its executable is unavailable; **Always HTTPS**
-does not inspect the CLI. Saving changed judge transport, executable, or model settings
+**Always the jev CLI** never uses HTTPS if its executable is unavailable; **Always Modex's
+HTTPS call** does not inspect the CLI. Saving changed judge transport, executable, or model settings
 invalidates resolved setup without clearing learned preferences or disrupting an
 already-running turn. General, posture-only, and no-op saves retain connection-test health.
 
@@ -125,8 +125,8 @@ deterministically, and every step that changes the outcome adds a reason to the
    unavailable. Mid-thread switches lose the CLI's context, so this is off by default; model
    switches have their own guard in step 7.
 4. **Model.** The highest rung at or below the target tier on that backend
-   (`routing/catalog.ts`). The ladder is rebuilt from the CLI's live model list: Claude's
-   aliases (haiku 0 · sonnet 1 · opus 2 · fable 3) and Codex's catalogue (gpt-5.5 0 ·
+   (`routing/catalog.ts`). The ladder is rebuilt from each backend's model list: Modex's
+   fixed Claude aliases (haiku 0 · sonnet 1 · opus 2 · fable 3) and Codex's live catalogue (gpt-5.5 0 ·
    gpt-5.6-* 1 · gpt-6-luna/sol 2 · gpt-6-astra 3), with description hints for anything new
    and the middle tier for unknowns.
    Successful non-empty lists are cached for a minute. A failed or empty list retries on
@@ -235,7 +235,8 @@ what each switch actually cost.
 
 ## Bounds you control
 
-Settings has separate General, Coding CLIs, Auto routing, and Advanced sections, with Save
+Settings has separate General, Coding CLIs, Auto routing, Approval rules, and Advanced / demo
+sections, with Save
 and Cancel kept visible while the content scrolls. Auto routing exposes posture, effort
 ceiling, minimum judge confidence, premium turns per day, fast-mode allowance, backend
 switching, and whether new threads start on Auto, plus the judge model and allowed coding
 
@@ -88,8 +88,8 @@ biometric gesture.
 See the [acceptance report](reviews/2026-10-11-browser-credential-acceptance.md) for the exact
 evidence and limits.
 
-Before releasing 1Password filling, use a disposable Login for a controlled HTTPS site in
-a signed app launched normally. Verify real unlock, selection, filling without submission,
+1Password filling shipped in v0.0.11 with this check still open. To complete it, use a
+disposable Login for a controlled HTTPS site in a signed app launched normally. Verify real unlock, selection, filling without submission,
 cancellation during listing and item reads, navigation and close cancellation, and absence
 of credentials from app state, logs, and error surfaces. Enable the CLI integration in
 1Password and select the intended account first if you use several accounts.
 
@@ -1,6 +1,7 @@
 # App-owned ChatGPT sign-in through Codex (#76)
 
-Settings → Coding CLIs offers **Continue with ChatGPT**, account selection,
+Settings → Coding CLIs offers **Continue with ChatGPT** (**Add another ChatGPT account** when
+the Codex CLI is already signed in), account selection,
 reauthorization and sign-out. Actions apply immediately. Existing Codex CLI authentication
 remains available. Each saved account label includes its issued registration so two
 workspaces with the same email remain distinguishable.
@@ -67,7 +68,7 @@ recovery prevents accidental concurrent refresh on a shared home.
 Fixture tests cover public/returning flows, identity validation, state/path rejection,
 encryption, insufficient scopes, refresh serialization, local/remote sign-out and separate
 Codex child ownership. They do not establish a real OpenAI grant or subscription entitlement.
-Before landing: complete a real user-controlled new registration, returning authorization,
+Before landing, the plan required a real user-controlled new registration, returning authorization,
 Codex turn, refresh/resume, multi-account selection and sign-out on macOS Apple Silicon.
 Apple Silicon acceptance completed on 2026-10-04: real registration and returning
 authorization, completed Codex turns, rotating refresh and process replacement,
 
@@ -22,9 +22,10 @@ Claude and Codex coding turns continue to run through their CLIs on the Mac.
 
 The listener is off until enabled. It exposes only a small paired API: snapshots, thread
 creation, provider-scoped command discovery, sending a follow-up, answering an unanswered
-approval once, and archiving or unarchiving a thread. It omits project paths, skill paths, backend session
-handles, settings, and tool arguments from snapshots. The iPhone offers only Approve once and
-Deny, with an extra confirmation before approval. The Mac certificate and token live under
+approval once, setting a thread's approval policy, and archiving or unarchiving a thread. It
+omits project paths, skill paths, backend session handles, settings, and tool arguments from
+snapshots. The phone confirms each answer to an approval card before sending it; see
+[Approvals](#approvals-skills-and-finished-tasks). The Mac certificate and token live under
 `~/.modex/companion/` with owner-only permissions, outside the repository and app bundle.
 The server needs the Mac app to be running. There is no relay or internet endpoint.
 
@@ -92,7 +93,7 @@ recovery permanently. Bonjour publishes only the address and public certificate
 
 Xcode 26.6 and XcodeGen are used to generate the native SwiftUI project from
 `apps/ios/ModexCompanion/project.yml`. The app identifier is
-`works.jev.modex`, version 0.1.0 (build 6), for iPhone on iOS 18 or newer.
+`works.jev.modex`, version 0.2.0 (build 7), for iPhone on iOS 18 or newer.
 
 ```sh
 cd apps/ios/ModexCompanion
@@ -181,8 +182,8 @@ Build 3 adopts the official Modex mark in the App Store icon, onboarding and wor
 On 2026-10-05, all 10 native tests and the paired simulator flow passed. Its signed IPA
 passed Apple validation and upload, then reached `VALID` and `IN_BETA_TESTING` in the
 existing Internal group with one tester (build ID `ee29b4ab-89d6-401d-a4ae-c4a860c71ae0`).
-Physical iPhone installation and acceptance remain open; the public website continues to
-show **Coming soon**. See the [v0.0.7 ledger](reviews/2026-10-05-v0.0.7-release-review.md).
+Physical iPhone installation and acceptance remained open; the public website then showed
+**Coming soon**. See the [v0.0.7 ledger](reviews/2026-10-05-v0.0.7-release-review.md).
 
 Build 4 adds persistent pairing, trusted local discovery and automatic recovery after the
 Mac address or port changes. On 2026-10-05, all 14 native tests and the extended LAN
@@ -211,7 +212,10 @@ settings and full skill descriptions, and keeps the saved pairing and draft whil
 It also rotates through every private address the Mac advertises. On 2026-10-13 its signed IPA
 passed validation and upload (build ID `2f6e7d20-527e-44dd-a337-74564ac23bba`), reached
 `VALID`, and was assigned to the Internal and External groups. Apple returned beta review
-`APPROVED` at submission. Physical installation of this build was not performed. See the
+`APPROVED` at submission. Physical installation of this build was not performed. On
+2026-10-11 a signed development build passed pairing, recovery, approval and retirement on a
+physical iPhone; fresh-install consent and a TestFlight install remain unaccepted
+([physical acceptance](reviews/2026-10-11-iphone-acceptance.md)). See the
 [v0.0.11 ledger](reviews/2026-10-12-v0.0.11-release-review.md#iphone-companion-build-6).
 
 The iPhone build has a separate release path from the signed and notarized macOS release.
 
@@ -3,9 +3,10 @@
 Choose a knowledge folder and install OpenKnowledge in **Space → Knowledge base**.
 **Use your Modex notes** makes the notes folder ([Notes folder](notes.md)) the knowledge base, so
 pages written in Space and in Open Knowledge are the same files. A page's menu then offers
-**Open in knowledge base** instead of a copy. With the notes folder as the knowledge base, each
-project's agents read, write and search only that project's notes; search then runs over those
-files directly rather than through the companion.
+**Open in knowledge base** instead of a copy. When the knowledge base is the notes folder, a
+folder inside it, or a folder that holds it, each project's agents read, write and search only
+that project's notes there; search then runs over those files directly rather than through the
+companion.
 Claude and Codex threads can search and read it from any project or worktree. Modex
 starts the companion when a coding turn needs the connection.
 
 
@@ -76,10 +76,10 @@ renderer reuse, not production transport authorization or Store acceptance.
    cannot submit commands, including requests already in flight. Add real CLI acceptance.
 4. Run signed, sandboxed acceptance under a fresh macOS user. Verify consented file access,
    persistent pairing, sleep/wake, host/client restarts and compatible-version upgrades.
-5. Create the macOS App Store Connect record and provision the distinct Store bundle ID
-   (proposed `works.jev.modex.desktop`, final record/name to be confirmed at that gate).
-   Produce the Apple Distribution package; validate, upload, verify processing and test
-   installation through macOS TestFlight. A Developer ID DMG does not satisfy this gate.
+5. The App Store Connect record (**Modex Mac App Store**, app ID `6819549715`) and the Store
+   bundle ID `works.jev.modex.desktop` exist, and the Apple Distribution package for 0.0.8
+   was uploaded and processed. Installation through macOS TestFlight is still untested. A
+   Developer ID DMG does not satisfy this gate.
 6. Submit truthful metadata and screenshots for App Review. Publish only after acceptance.
 
 The iPhone reconnection work in v0.0.7 supplies useful identity/revocation behavior, but it
 
@@ -1,5 +1,9 @@
 # Mac App Store preview execution ledger
 
+**Status (2026-10-18): partial.** The preview merged in #119. The two open items below remain;
+the other Store gates are in [status, In flight](status.md#in-flight). No open PR carries this
+work.
+
 Val requested a runnable desktop Store preview on 2026-10-05, following approval of the
 separate signed-host direction. Reuse the existing desktop React interface and CLI-owned
 engine. The iPhone-on-Mac Companion is not this desktop target.