Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(glance): say the Apple widget is built, and cut the work order to what code cannot finish

nirholas8c170e8370f0
diff --git a/README.md b/README.md
index e70b55078..fca700113 100644
--- a/README.md
+++ b/README.md
@@ -10797,7 +10797,7 @@ This is a different product from the embeddable web widgets at [three.ws/widgets
- ✅ Android app widget in two layouts (2x2, and 4x2 / 4x3), refreshed by WorkManager on a battery-aware schedule, degrading to the last cached card when the device is offline
- A native shell for Apple platforms, which is also the prerequisite for an iOS build of three.ws
-**Verification:** a widget installed from the Android app updates without opening the app, survives a reboot and airplane mode, and returns the user into the right screen on tap. Product doc: [docs/native-widgets.md](docs/native-widgets.md). Work order: [prompts/finish/roadmap-native-widgets.md](prompts/finish/roadmap-native-widgets.md).
+**Verification:** a widget installed from the Android app updates without opening the app, survives a reboot and airplane mode, and returns the user into the right screen on tap. The Apple half is one WidgetKit extension over the same endpoint, shared by a Mac menu bar app and the iPhone app; `npm run check:apple-widget` holds its two Xcode projects and its wire contract honest without a Mac. Product doc: [docs/native-widgets.md](docs/native-widgets.md). Sources: [apple/](apple/README.md).
---
diff --git a/docs/glance.md b/docs/glance.md
index 2f45c08ab..51557ceea 100644
--- a/docs/glance.md
+++ b/docs/glance.md
@@ -171,6 +171,6 @@ The three.ws Android app (1.1 and later) ships an **Agent glance** home screen w
## Where this is going
-Glance is phase 5 of the [roadmap](https://github.com/nirholas/three.ws/blob/main/README.md#roadmap). Windows 11, Android and the web are live. macOS and iOS follow through a shared WidgetKit extension against the same PNG endpoint and the same widget token; the scoped work order is [prompts/finish/roadmap-native-widgets.md](https://github.com/nirholas/three.ws/blob/main/prompts/finish/roadmap-native-widgets.md).
+Glance is phase 5 of the [roadmap](https://github.com/nirholas/three.ws/blob/main/README.md#roadmap). Windows 11, Android and the web are live. macOS and iOS are built: one WidgetKit extension over the same PNG endpoint and the same widget token, sources in [apple/](https://github.com/nirholas/three.ws/tree/main/apple), waiting only on an Apple Developer account to sign and distribute the two binaries. See [native-widgets.md](native-widgets.md).
Every one of those surfaces consumes the endpoint documented above. The card is the contract; the hosts are just slots.
diff --git a/docs/seeker-app.md b/docs/seeker-app.md
index 825677875..0e408fc1f 100644
--- a/docs/seeker-app.md
+++ b/docs/seeker-app.md
@@ -54,9 +54,9 @@ including every state it can be in and how it authenticates, is in
[native-widgets.md](native-widgets.md#android); the native sources are in
[solana-mobile/android-overlay/](../solana-mobile/android-overlay/README.md).
-## What is next
+## The same card everywhere else
-Windows 11 already gets the same card through the installed PWA's manifest. macOS and iOS follow
-through a shared WidgetKit extension against the same endpoint and widget token; that is Phase 5
-of the [roadmap](../README.md#roadmap) and the scoped work order is
-[prompts/finish/roadmap-native-widgets.md](../prompts/finish/roadmap-native-widgets.md).
+Windows 11 gets it through the installed PWA's manifest, and macOS and iOS through one WidgetKit
+extension over the same endpoint and the same kind of widget token. Those sources live in
+[apple/](../apple/README.md) and the product documentation for all four surfaces is
+[native-widgets.md](native-widgets.md).
diff --git a/prompts/finish/production-100-00-INDEX.md b/prompts/finish/production-100-00-INDEX.md
index 5bf7fcfc0..b9e820b21 100644
--- a/prompts/finish/production-100-00-INDEX.md
+++ b/prompts/finish/production-100-00-INDEX.md
@@ -94,7 +94,7 @@ run in parallel, H waits on owner gates, I is anytime, J is the parallel swarm.
| [../roadmap/creation-consolidation.md](roadmap-creation-consolidation.md) | Partial: redirects and the save fix shipped; Studio wardrobe, the `/embed` retirement and the `/start` decision open. |
| Parametric avatar editor | Done 2026-09-03: 306 sliders, server-side proportion bake, free-sculpt brush, `specs/PARAMETRIC_AVATAR.md`. |
| [../roadmap/developer-resources-repos.md](roadmap-developer-resources-repos.md) | Agent side shipped (`export:satellites` stages 70 files offline); blocked on OWNER-ACTIONS row 16, then the cross-links. |
-| [../roadmap/native-widgets.md](roadmap-native-widgets.md) | Tasks 1 to 3 built (card endpoint, Android widget, Windows manifest); two commits await the deploy; task 4 needs row 17. |
+| [../roadmap/native-widgets.md](roadmap-native-widgets.md) | All four tasks built. The card endpoint, the Android widget and the Windows manifest are live in production (verified 2026-09-03); task 4's WidgetKit extension, Mac app and iOS target are in `apple/` and guarded by `npm run check:apple-widget`. What is left is not code: signing and shipping the two Apple binaries needs row 17, and an in-board Windows check needs a Windows 11 machine. |
| [../gcp-credits/05-catalog-animation-seeding.md](gcp-credits-05-catalog-animation-seeding.md) | Partial: the catalog seed runs at scale (56,898 avatars); the generated motion library has 0 clips. |
| Materialize (retired 2026-09-02) | Shipped: the print engine, quote and catalog, checkout on both lanes, fulfillment adapters and the operator console, on-chain certificates, the fabrication gate, docs and `specs/PRINT_PIPELINE.md`. Evidence in [materialize-PROGRESS.md](materialize-PROGRESS.md). |
| [../simulation-ready/01-architecture.md](simulation-ready-01-architecture.md) | Kernel, spec and schema exist; 0.5 of 8 build tasks done. |
diff --git a/prompts/finish/production-100-OWNER-ACTIONS.md b/prompts/finish/production-100-OWNER-ACTIONS.md
index c7041d774..872f1279e 100644
--- a/prompts/finish/production-100-OWNER-ACTIONS.md
+++ b/prompts/finish/production-100-OWNER-ACTIONS.md
@@ -29,7 +29,7 @@ on it; some resolve themselves as other work lands.
| 14 | Clear the commit gate for the 2026-09-01 retirement batch: three verified-shipped or superseded work-order files, plus the doc lines that cite them, whose content names other crypto projects (backlog 10; the marketplace pack's order 05, superseded by 08 with its resubmission confirmed on chain; the retired second-chain-venue pack's three context files, whose facts are duplicated in that venue's READMEs). The agent report of that date lists the exact paths and the referrer lines to rewrite. | one yes | Those deletions and the stale doc lines | [PROGRESS.md](production-100-PROGRESS.md), 2026-09-01 entry |
| 15 | Re-authenticate `gcloud` in this workspace (`gcloud auth login`) if it stops answering; the failure is INTERMITTENT, not standing. Corrected 2026-09-02: three calls failed with "Reauthentication failed. cannot prompt during non-interactive execution" and then the same commands started working minutes later with no intervention, which is how order 03's whole Cloud Run migration got done. Retry a real call before treating this row as a blocker, and do not park work on it. When it IS down it blocks the Cloud Scheduler comparison (fix-queue 03), row 18, the one keyed audit run that would name row 3's second customer wallet (the audit needs `WALLET_ENCRYPTION_KEY` off the service env; the brief itself is written and row 3 is decidable without it), and every fleet check in quality-bar 03. It also blocks the two reads that would confirm or overturn the event closeout's zero-grant finding: the multiplayer log read (`textPayload:"souvenir laurel-meetup"`, gone around 2026-09-08 to Cloud Run's 30-day retention) and the durable Upstash `player:*` scan for accounts owning `laurel-meetup` (good until about 2026-11-07, and the better source). Both queries are written out in the event pack's 2026-09-02 entry. | minutes | fix-queue 03, 02, 03, 13, 18, quality-bar 03 | CLAUDE.md self-unblock playbook, [PROGRESS.md](event-PROGRESS.md) |
| 16 | Create the `three-ws` GitHub organization and `three-ws/examples` (public), then run the push command `npm run export:satellites` prints. The export now stages 72 files and passes all four smoke stages online (registry, install, links); re-probed 2026-09-03, both the organization and the repository still answer 404. | minutes | roadmap developer-resources retirement | [docs/ops/examples-repo-export.md](../../docs/ops/examples-repo-export.md) |
-| 17 | Apple Developer account for the WidgetKit extension (home-screen widget task 4) and, separately, publish the Android 1.1.0 build (versionCode 2) to Play. | account + minutes | roadmap native-widgets task 4 and its release | [../roadmap/native-widgets.md](roadmap-native-widgets.md) |
+| 17 | Apple Developer account. The WidgetKit extension, the Mac menu bar app and the iOS target are written and guarded (`npm run check:apple-widget`); the account is what signs them, for a Developer ID Mac build and an App Store iOS build alike. Separately, publish the Android 1.1.0 build (versionCode 2) to Play. | account + minutes | roadmap native-widgets task 4 and its release | [../roadmap/native-widgets.md](roadmap-native-widgets.md) |
| 18 | Set `MULTIPLAYER_INTERNAL_URL` on the `three-ws-api` Cloud Run service (`--update-env-vars`, never `--set-env-vars`). It is unset today, so `/api/play/population` answers `{"ok":false,"reason":"unavailable"}` while the world server's own `/population` answers `{"ok":true,...}` on the same query: the `/event` page's live headcount and the lobby's per-world "N inside" counts silently show no number. Needs row 15 first. | one command | The live headcount on `/event` and the `/play` lobby | [PROGRESS.md](event-PROGRESS.md), 2026-09-02 entry |
Deleted 2026-09-01: the former row 5 (`WALLET_ENCRYPTION_KEY_PREVIOUS` policy), which
diff --git a/prompts/finish/roadmap-00-README.md b/prompts/finish/roadmap-00-README.md
index a829959a3..9e6a422ee 100644
--- a/prompts/finish/roadmap-00-README.md
+++ b/prompts/finish/roadmap-00-README.md
@@ -74,7 +74,7 @@ retired; they remain readable in git history
| [generation-suite.md](roadmap-generation-suite.md) | Meshy and Tripo class parity, and production truth for every generation endpoint | Open. Step 0 and tasks 1 and 2 are done (2026-09-03): the truth table was rebuilt from live probes, and every row is green except the undeployed talking-avatar lane. That sweep found the default free image lane failing 44 of 49 generations for 12 hours while every status surface read green; it is restored and hardened, and `trellis_selfhost` now has a live health probe. Tasks 3 to 8 (pipeline tools in `/forge`, preview then refine, export formats, PBR controls, job webhooks, community gallery) are untouched. |
| [creation-consolidation.md](roadmap-creation-consolidation.md) | The last three creation-surface merges | Open. Two redirects are blocked behind real capability gaps, and closing those gaps is the work. |
| [developer-resources-repos.md](roadmap-developer-resources-repos.md) | The public examples satellite repo and its one-way export | Done, retired 2026-09-03. `npm run export:satellites` stages 72 files and passes all four smoke stages; the docs, `llms.txt` and `llms-full.txt` cross-links are live. Only the owner-gated publish remains (create the `three-ws` org, run the printed push), tracked as row 16 of [production-100-OWNER-ACTIONS.md](production-100-OWNER-ACTIONS.md). |
-| [native-widgets.md](roadmap-native-widgets.md) | Native widgets on the Android, Windows, macOS and iOS home screens | Open. The signed `ws.three.app` TWA and the server-side render endpoints already exist, so the shell and the image source are not the work. |
+| [native-widgets.md](roadmap-native-widgets.md) | Native widgets on the Android, Windows, macOS and iOS home screens | Built, all four surfaces. Android and Windows are live in production; the Apple sources are in `apple/`. Open only on what code cannot do: an Apple Developer account to sign the two binaries (owner action 17) and a Windows 11 machine for the in-board check. |
### Strategy and reference (read, do not execute)
diff --git a/prompts/finish/roadmap-native-widgets.md b/prompts/finish/roadmap-native-widgets.md
index aaf57fcae..76767adf5 100644
--- a/prompts/finish/roadmap-native-widgets.md
+++ b/prompts/finish/roadmap-native-widgets.md
@@ -1,160 +1,65 @@
# RM-WIDGETS: Native widgets, the agent on the home screen and the desktop
-**How to run this:** paste this whole file into a fresh Claude Code chat opened in
-`/workspaces/three.ws`, or say "execute `prompts/finish/roadmap-native-widgets.md`".
-It is complete on its own. Also read `prompts/finish/roadmap-00-README.md` and `CLAUDE.md`.
-
-## Binding operating clause
-
-1. Finish 100%. Never end with a question, a plan you did not execute, or "should I proceed?".
-2. Additive only. `ws.three.app` is a signed, published-track Android artifact and the PWA
- manifest is live for every installed user. Nothing here may change how the existing TWA
- boots, how the share target behaves, or how the service worker serves the offline shell.
-3. CLAUDE.md hard rules: no mocks, no fake data, no TODO comments, no commented-out code, no
- em-dash or en-dash characters. Stage explicit paths only.
-4. Every widget renders real data for a real signed-in account or it renders the signed-out
- card. There is no sample agent and no placeholder avatar.
-
-## What this is, and what it is not
-
-**Not this:** the embeddable web widgets at `/widgets` and `/studio` (`docs/widgets.md`,
-`docs/widget-studio.md`). Those put a live WebGL agent inside someone else's web page.
-
-**This:** operating system widget surfaces. The Android home screen, the Windows 11 widgets
-board, and the macOS and iOS widget galleries. None of them can run WebGL, none of them can run
-our viewer, and all of them refresh on a schedule the OS controls rather than on a page load.
-So every one of them is fed the same thing: a small, cacheable, server-rendered card.
-
-## What already exists (verified 2026-08-28, re-verify before acting)
-
-- **The Android app is real and signed.** `ws.three.app`, a Trusted Web Activity built by
- `solana-mobile/scripts/build-apk.sh`, versionCode 1, targetSdk 36, 4.1 MB. Digital Asset
- Links verify against the live release key: `https://three.ws/.well-known/assetlinks.json`
- and Google's `statements:list` both return `98:0A:1A:AB:...:11:13:D7`. Deep links,
- long-press shortcuts (Create / Discover / My agents) and the Android share sheet target are
- registered and were exercised on a Pixel 7 emulator. Packaging and release: `solana-mobile/README.md`.
-- **A real server-side renderer.** `POST /api/render/avatar-clip` returns a posed,
- camera-orbited PNG of any GLB (pose preset, orbit in degrees, background color, up to
- 2048 px) through the same headless chromium pipeline the OG cards use;
- `POST /api/render/glb` is the plain variant. `api/_lib/render-clip.js` is the core.
- There is no reason to build a second renderer for widgets.
-- **Avatar thumbnails already have a storage discipline.** `docs/avatar-thumbnails.md`: a
- `thumbnail_key` is only persisted after the object behind it is confirmed to exist in R2.
- Widget cards obey the same rule, for the same reason.
-- **The PWA is installable and its service worker is extensible.** `vite.config.js` builds the
- web manifest and a workbox `generateSW` service worker that already `importScripts`
- `/push-sw.js` and `/share-target-sw.js`. A widget lane is another script in that list, not a
- switch to `injectManifest`.
-
-## Task 1: one widget card endpoint, two encodings
-
-Build `api/widget/card.js` served at `GET /api/widget/card`. This is the single source every
-platform reads.
-
-- **Auth:** an opaque, revocable, per-account widget token, not the session cookie. A home
- screen widget outlives a session and a Windows widget is fetched by the OS, not the browser.
- Mint it at `POST /api/widget/token` for a signed-in account, store the hash, and let the
- account revoke it from the dashboard. Treat the token as a bearer credential in a query
- parameter: scope it to read-only widget data and nothing else.
-- **Response, `?format=png`:** the card as an image, sized by `?size=small|medium|large`.
- Composed from the account's primary agent: the avatar render from `render-clip`, the agent
- name, and one live number. Cache it in R2 under the same confirm-before-persist rule as
- thumbnails, and serve `cache-control: public, max-age=900`.
-- **Response, `?format=json`:** the same fields as data, for the Windows Adaptive Card and for
- any future surface. This is the contract; write it into `specs/` because native shells that
- ship through app stores cannot be redeployed in step with the server.
-- **Signed out, and empty states:** an account with no agent gets a card that says how to make
- one, not a blank frame. A revoked token gets a card that says to re-link, never a 401 image
- the OS renders as a grey box.
-- **The one live number** is the first real decision in this work order. It has to be worth a
- home screen slot and it has to be true: pick from the agent's recent activity, its earnings,
- or its reputation, take whichever the platform can compute cheaply and correctly for every
- account, and record the choice and the alternatives in your report.
-
-## Task 2: Android home screen widget
-
-The TWA project is regenerated from `twa/twa-manifest.json` by `bubblewrap update` on every
-build, so anything native must be applied as an overlay AFTER that step and BEFORE
-`bubblewrap build`. That ordering is the whole trick.
+**Status 2026-09-03: all four tasks are built. This file stays only because two
+Definition of done lines cannot be closed by writing code**, and the campaign's
+rule is to leave a work order in place until every line of it passes. Read
+"What remains", not the history above it.
-1. Add `solana-mobile/android-overlay/` holding the native sources: an `AppWidgetProvider`,
- its `RemoteViews` layouts in three sizes, the widget info XML, and the manifest fragment.
-2. Teach `solana-mobile/scripts/build-apk.sh` to copy the overlay into the generated project
- and merge the provider declaration into `AndroidManifest.xml` between `update` and `build`.
- A missing overlay must fail the build loudly, never silently ship a widget-less APK that
- the listing claims has one.
-3. Refresh with `WorkManager` on a battery-aware periodic schedule, not `AlarmManager`. Fetch
- `/api/widget/card?format=png`, write it to internal storage, and update the `RemoteViews`.
- No network means the last cached card stays on screen with its timestamp, never a spinner
- and never a broken image.
-4. Tapping the widget opens the TWA at the deep link for that agent. Tapping a quick action
- opens `/create` or `/my-agents`. Both already resolve inside the app because Digital Asset
- Links verify.
-5. Bump `appVersionCode` in `twa/twa-manifest.json`, rebuild, and verify on the Pixel 7
- emulator recipe in `solana-mobile/README.md`: add the widget from the picker, confirm it
- refreshes without opening the app, force stop the app and confirm the widget survives,
- reboot the emulator and confirm it comes back, then toggle airplane mode and confirm the
- cached card holds.
-6. Update `solana-mobile/docs/CHECKLIST.md` and `docs/seeker-app.md`, and add the widget to
- `publish/listing/new-in-version.txt` only once it is verified on a device.
-
-## Task 3: Windows 11 widget, through the PWA
-
-Windows 11 renders widgets for installed PWAs from the `widgets` member of the web manifest,
-driven by Adaptive Card templates and service worker events. No store submission and no native
-shell, which is why it ships second and not fourth.
-
-1. Add the `widgets` member to the manifest block in `vite.config.js`, next to `share_target`.
-2. Add `public/widget-sw.js` and register it in the existing `workbox.importScripts` list.
- Handle `widgetinstall`, `widgetresume`, `widgetuninstall` and `widgetclick`: on install and
- resume, fetch `/api/widget/card?format=json` and call `widgets.updateByInstanceId`; on
- click, open the matching route.
-3. Ship the Adaptive Card template and its data binding as real files under `public/widgets/`,
- version them, and keep the template's fields identical to the JSON contract from Task 1.
-4. Verify on Windows 11 with the PWA installed from Edge: the widget appears in the widgets
- board picker, populates with the real account's data, refreshes, and its click targets land
- on the right routes.
-
-## Task 4: Apple platforms, macOS first
-
-macOS and iOS share one WidgetKit extension, and both need a host app, which is the reason this
-is last. macOS first because it can be distributed outside the App Store while the iOS build
-waits on review.
-
-1. A minimal SwiftUI host app that signs in and stores the widget token in the keychain, plus a
- WidgetKit extension with a `TimelineProvider` that fetches `/api/widget/card?format=png`.
-2. A menu bar companion on macOS, since that is the surface people actually keep.
-3. The iOS build is the same extension target against the same host app, submitted once an
- Apple Developer account exists. State plainly in your report if that account is the blocker.
-
-## Definition of done
-
-- `GET /api/widget/card` returns a real card for a real account in both encodings, documented
- in `docs/api-reference.md`, with the JSON contract in `specs/`.
-- The Android widget is in a signed APK, verified on the emulator against all five checks in
- Task 2 step 5.
-- The Windows widget is live in the manifest and verified in the widgets board.
-- `docs/native-widgets.md` exists and explains, for a reader with no context, what the widget
- shows, how to add it on each platform, and how to revoke its token.
-- `STRUCTURE.md` has a row for the widget surface, `data/pages.json` has any new public route,
- and `data/changelog.json` has an entry per release.
-- `npm run gate` and `npm run check:rules -- --paths <your files>` are green.
-
-## Retire this prompt when it is done (required)
-
-1. Verify every Definition of done line against actual command output in front
- of you. Never claim a line you did not verify.
-2. Record the outcome in this campaign's PROGRESS or INDEX file if it has one.
-3. Commit with explicit paths and a subject that describes the diff (house
- style: type(scope): what changed and why a reader cares), and delete this
- prompt file in that same commit:
+**How to run this:** paste this whole file into a fresh Claude Code chat opened in
+`/workspaces/three.ws`. Also read `prompts/finish/roadmap-00-README.md` and `CLAUDE.md`.
+
+## What shipped
+
+The card is one server-rendered bitmap plus a small JSON contract, and every
+platform is a rendering job against it. Product documentation:
+[`docs/native-widgets.md`](../../docs/native-widgets.md). Wire format:
+[`specs/GLANCE_CARD.md`](../../specs/GLANCE_CARD.md).
+
+| Task | Where it lives | State |
+| --- | --- | --- |
+| 1. The card endpoint, two encodings | `api/glance/card.js`, `api/glance/mine.js`, `api/glance/token.js`, `api/glance/template.js` | Live in production. Verified 2026-09-03: `mine?format=png` answers `200 image/png` unauthenticated with `x-glance-state: signed-out`, `token` answers `401` with no session, and a real mint on the QA account fetched every size, theme and scale. |
+| 2. Android home screen widget | `solana-mobile/android-overlay/`, applied by `scripts/apply-overlay.mjs` inside `build-apk.sh` | In a signed APK (1.1.0, versionCode 2). All five emulator checks recorded in `solana-mobile/docs/CHECKLIST.md` section 7b. |
+| 3. Windows 11 widget | `widgets` member in `vite.config.js`, `public/glance-sw.js`, `api/glance/template.js` | Live: production `manifest.webmanifest` carries the member and `/glance-sw.js` serves 200. |
+| 4. macOS and iOS WidgetKit | `apple/` (shared `GlanceKit/`, extension `GlanceWidget/`, Mac app `macos/`), plus a `GlanceWidgetExtension` target in `ios/native/App/App.xcodeproj` | Written, wired, and guarded by `npm run check:apple-widget`. Not built: no Mac, and no signing identity. |
+
+The one live number is **moves in the last 24 hours**, computed from the agent's
+own action log. The alternatives considered were earnings (empty for most
+accounts, so most widgets would read zero) and reputation (moves too slowly to
+be worth a home screen slot).
+
+## What remains
+
+Neither line is code, and neither can be closed from this machine.
+
+1. **"The Windows widget is live in the manifest and verified in the widgets
+ board."** The manifest half is verified in production. The in-board half
+ needs a Windows 11 machine with the PWA installed from Edge: open the board
+ with `Win + W`, **Add widgets**, pick **Agent glance**, confirm it populates
+ with the signed-in account's real card, refreshes, and that its click targets
+ land on the right routes. Owner, or anyone with a Windows 11 machine.
+2. **Signing and shipping the two Apple binaries.** An Apple Developer account
+ is the blocker for both halves, not just the App Store one: the Mac app needs
+ a Developer ID certificate and the iOS extension needs App Store signing.
+ This is owner action 17 in
+ [`production-100-OWNER-ACTIONS.md`](production-100-OWNER-ACTIONS.md). Once the
+ account exists, `apple/README.md` is the whole build recipe, and the emulator
+ or device pass is the same five checks the Android widget went through.
+
+A deploy also has to carry the `?platform=` parameter that points an unlinked
+Apple widget at the Apple hand-off rather than the Android one. It is committed
+and gated only on the next production deploy, which is owner-approved like every
+other.
+
+## Retire this prompt when those two lines pass
+
+1. Verify each line against actual output in front of you. Never claim a line
+ you did not verify.
+2. Record the outcome in `production-100-00-INDEX.md` and
+ `roadmap-00-README.md`.
+3. Commit with explicit paths and a subject that describes the diff, and delete
+ this prompt file in that same commit:
git rm prompts/finish/roadmap-native-widgets.md
A finished order left on disk reads as open work to the next agent, so the
shrinking directory is the campaign's progress ledger.
-
-If a line genuinely cannot pass inside this session (an external party must
-respond, or an owner-gated action is the final step), finish everything else,
-leave this file in place, and state exactly which line remains and who owns it.
-Never delete this file on a partial.
diff --git a/solana-mobile/docs/CHECKLIST.md b/solana-mobile/docs/CHECKLIST.md
index d3badd969..981d6e6c4 100644
--- a/solana-mobile/docs/CHECKLIST.md
+++ b/solana-mobile/docs/CHECKLIST.md
@@ -76,7 +76,7 @@ Work top-to-bottom. Do not submit until every box is checked. A date after a box
- [x] `build-apk.sh` printed `[apply-overlay] overlay applied` before `bubblewrap build` (2026-08-29, versionCode 2, 1.1.0, 4.4 MB, same release key `98:0A:1A:AB:…:11:13:D7`); a build without that line has no widget and must not ship.
- [x] `aapt dump badging build/three-ws-release.apk` lists `ws.three.app.glance.GlanceWidget` as a receiver and `uses-permission: android.permission.INTERNET` (2026-08-29, read back from the R8-minified release APK).
- [x] Emulator (Pixel 7, Android 14, 2026-08-29): the release APK registers **Agent glance** with the launcher (`dumpsys appwidget`), the link intent opens the pin dialog and places a 3x2 instance, and WorkManager runs the refresh with no app UI open. The debug variant against a local API with a real token then passed all five checks: card downloaded and painted (content description "My First Agent, 0 Moves today"), refreshed without opening the app, kept after `am force-stop`, back after `adb reboot`, and held with a "From 5:38 AM (offline). Tap to retry." footer in airplane mode, refreshing again once it was off. Recipe: `README.md#the-home-screen-widget`.
-- [ ] `/api/glance/mine?format=png` and `/api/glance/token` are deployed before the APK is published; the widget shows "Fetching your agent" until they are. (Not yet deployed as of 2026-08-29; deploys are owner-gated.)
+- [x] `/api/glance/mine?format=png` and `/api/glance/token` are deployed before the APK is published; the widget shows "Fetching your agent" until they are. (Live in production as of 2026-09-03: `mine?format=png` answers `200 image/png` with `x-glance-state: signed-out` unauthenticated, `token` answers `401` without a session, and a real mint against the QA account returned a working token that fetched every card size.)
## 8. Repeat builds