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(prompts): update the backlog and fix-queue progress notes

nirholas1050be8f2f9a
diff --git a/prompts/finish/909-backlog-10-x402scan-listing.md b/prompts/finish/909-backlog-10-x402scan-listing.md
index 9ba22e6fd..34770dbb4 100644
--- a/prompts/finish/909-backlog-10-x402scan-listing.md
+++ b/prompts/finish/909-backlog-10-x402scan-listing.md
@@ -46,23 +46,37 @@ hand-authored paths so the 24 richer entries keep their exact wording.
Five guards in [tests/openapi-aggregator.test.js](../../tests/openapi-aggregator.test.js)
keep it from reopening.
-## What remains
+## What remains (re-measured 2026-09-09)
-1. **Deploy.** The `/openapi.json` fix is in the tree and production is behind
- `main`. Until it ships, registration still sees 24 endpoints.
+1. ~~**Deploy.**~~ **Done.** The `/openapi.json` fix shipped on 2026-09-08
+ (production `880bdcef8`, revision `three-ws-api-00418-j26`). The document now
+ declares **82** paid `/api/x402/*` paths, not 24.
2. **Register the missing resources** (owner: one SIWX wallet signature, no
- funds move). 53 live endpoints answer a valid 402 today and are absent from
- the origin listing. After the deploy, the whole set is reachable from
- `/openapi.json`, so the "Add API" flow for origin `https://three.ws` at
- <https://www.x402scan.com/resources/register> picks them up in one pass.
- Wallet sign-in is a signature, not a spend, but it binds an identity: render
- what is being signed and get an owner yes.
-3. **Five endpoints cannot be registered until work order 01 lands capital.**
- `dance-tip`, `feed-health`, `ring-settle`, `spend-session` and `three-buy`
- are Solana-only, so while the sponsor wallet is under its SOL settle floor
- they answer 503 `settlement_unavailable` instead of a 402 and any probe
- fails. This is correct behavior, not a bug: every Base-carrying endpoint
- keeps its 402 through the same outage.
+ funds move). This is the ONLY remaining step. Run
+ `npm run preview:x402scan-registration` first: it reproduces x402scan's
+ classify/probe/deprecate pipeline against live production and, on 2026-09-09,
+ reported 123 registrable endpoints declared, 63 already listed, **60 rows
+ added and 0 deprecated**, with 59 of the 60 answering a spec-valid 402 to a
+ bare probe. The zero is the safety property, so re-run the preview
+ immediately before signing and stop if it is no longer zero. Then use "Add
+ API" for origin `https://three.ws` at
+ <https://www.x402scan.com/resources/register>. Wallet sign-in is a signature,
+ not a spend, but it binds an identity: render what is being signed and get an
+ owner yes.
+3. **The "five blocked endpoints" line was wrong and is retired.** Re-probed
+ 2026-09-09: `dance-tip`, `feed-health` and `spend-session` all answer a
+ spec-valid 402 advertising USDC and $THREE on Solana mainnet, so they are
+ probe-registerable today. The sponsor floor bites at settle time, not at
+ challenge time (`/api/healthz` reports `x402.self_facilitator.settle` at
+ 84 ok / 366 failed, every failure `fee_wallet_below_floor`), which stays work
+ order 01's capital problem. `ring-settle` and `three-buy` also answer 402 but
+ are `discoverable: false` internal ring machinery, deliberately absent from
+ the service catalog so `catalogPaidPaths()` never projects them. Listing them
+ would let dogfooded volume masquerade as organic demand. **Leave them out.**
+ One endpoint genuinely will not probe-register and should not: `GET
+ /api/x402/vanity-premium` browses the inventory for free and only
+ `?address=<base58>` triggers the 402, so their required-params-only probe
+ sees the free mode. Marking `address` required would be a lie about the route.
4. **Optional Base leg.** three.ws is in none of the CDP Bazaar's 15,127
resources, exactly as documented: indexing is triggered by a settle through
the CDP facilitator on Base, and production has no `X402_BUYER_PRIVATE_KEY`
@@ -78,10 +92,13 @@ curl -s https://three.ws/api/x402-facilitator/discovery/resources \
| python3 -c "import json,sys; d=json.load(sys.stdin); print(d['pagination']['total'], 'resources')"
curl -s https://three.ws/openapi.json \
| python3 -c "import json,sys; p=json.load(sys.stdin)['paths']; print(len([k for k in p if k.startswith('/api/x402/')]), 'paid paths')"
+npm run preview:x402scan-registration
npx vitest run tests/openapi-aggregator.test.js tests/service-catalog.test.js
```
-The third command reads 24 against production today and 79 after the deploy.
+The third command read 24 before the 2026-09-08 deploy and reads 82 now. The
+fourth is the one to trust before spending the signature: it must report 0 rows
+would be deprecated.
## Definition of done
@@ -90,8 +107,12 @@ The third command reads 24 against production today and 79 after the deploy.
- [x] The discovery endpoint's live output matches what the PR registers,
proven by replaying their own crawler against production.
- [x] Solana settlement unchanged and still self-hosted.
-- [ ] Origin registration: blocked on the deploy, then one owner wallet
- signature. The exact 53 endpoints are listed in PROGRESS.md.
+- [x] The deploy landed 2026-09-08; `/openapi.json` declares 82 paid paths.
+- [x] Registration preview built and validated against x402scan's own discovery
+ library (`npm run preview:x402scan-registration`): 60 rows added, 0
+ deprecated, 59/60 probe-valid.
+- [ ] Origin registration: **owner-gated**, one SIWX wallet signature and
+ nothing else. Re-run the preview immediately before signing.
- [x] [PROGRESS.md](_context/backlog-PROGRESS.md) updated.
## Retire this prompt when it is done (required)
diff --git a/prompts/finish/916-roadmap-native-widgets.md b/prompts/finish/916-roadmap-native-widgets.md
index 485d3e00c..59081ce05 100644
--- a/prompts/finish/916-roadmap-native-widgets.md
+++ b/prompts/finish/916-roadmap-native-widgets.md
@@ -1,12 +1,12 @@
# RM-WIDGETS: Native widgets, the agent on the home screen and the desktop
-**Status 2026-09-04: all four tasks are built, and the endpoints, the Apple
-hand-off and the Windows manifest are re-verified live. This file stays because
-two Definition of done lines cannot be closed from this machine** (one needs a
-Windows 11 machine, one needs an Apple Developer account), and the campaign's
-rule is to leave a work order in place until every line of it passes. The
-Windows worker also carries a 2026-09-04 fix that has to ship before the board
-check is worth running. Read "What remains", not the history above it.
+**Status 2026-09-09: all four tasks are built and re-verified live, and the
+2026-09-04 worker fix is now deployed** (production `/glance-sw.js` is
+byte-identical to `public/glance-sw.js` as of revision 00418). **This file stays
+because two Definition of done lines cannot be closed from this machine** (one
+needs a Windows 11 machine, one needs an Apple Developer account), 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.
**How to run this:** paste this whole file into a fresh Claude Code chat opened in
`/workspaces/three.ws`. Also read `prompts/finish/_context/roadmap-00-README.md` and `CLAUDE.md`.
@@ -22,7 +22,7 @@ platform is a rendering job against it. Product documentation:
| --- | --- | --- |
| 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. |
+| 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. Guarded by `npm run check:windows-widget`. The card fix of 2026-09-09 is not deployed yet. |
| 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
@@ -41,18 +41,33 @@ Neither line is code, and neither can be closed from this machine.
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.
- **Do that check against a deploy that carries 2026-09-04's worker fix, not
- against what is live now.** Reading the board's contract against the
+ **Run it against a deploy that carries 2026-09-09's card fix.** Everything
+ about this line that can be checked without a board now is, mechanically, by
+ `npm run check:windows-widget` (11 checks, in `npm run gate`). What is left
+ for the human is genuinely only "a person sees the pixels".
+
+ Four defects have been found here so far, none of them visible from Linux and
+ each of which would have failed this check on its own. Three came from reading
+ the board's contract against the
[Microsoft widget docs](https://learn.microsoft.com/en-us/microsoft-edge/progressive-web-apps/how-to/widgets)
- found three defects that would each have failed this check on its own, none
- of them visible from Linux: `msAcTemplate` is the URL of the Adaptive Card
- and the worker has to fetch it, but the worker was sending the host that URL
- as a string where the card belonged, so a pinned slot had nothing to draw;
- nothing ever registered the periodic sync, so the advertised 15 minute
- refresh was never scheduled; and a slot pinned before the worker activated
- stayed empty until the board next resumed it. All three are fixed in
- `public/glance-sw.js` and pinned by `tests/glance-sw.test.js`, and the fix
- reaches the board only on the next production deploy.
+ on 2026-09-04: `msAcTemplate` is the URL of the Adaptive Card and the worker
+ has to fetch it, but the worker was sending the host that URL as a string
+ where the card belonged, so a pinned slot had nothing to draw; nothing ever
+ registered the periodic sync, so the advertised 15 minute refresh was never
+ scheduled; and a slot pinned before the worker activated stayed empty until
+ the board next resumed it. All three are fixed in `public/glance-sw.js`,
+ pinned by `tests/glance-sw.test.js`, and **live in production since
+ revision 00418**.
+
+ The fourth was found on 2026-09-09 by expanding the live template in the
+ board's own engine (`adaptivecards-templating`, the Microsoft package the
+ board runs) instead of reading it with our own idea of a path. The template
+ asked for `${stats.0.label}`, which is how JavaScript indexes an array and a
+ syntax error in Adaptive Expression Language; the engine throws on the whole
+ card rather than skipping the one binding, so the widget rendered **nothing
+ at all**. Both the code and the test that covered it shared the same wrong
+ assumption, which is why the guard now uses the real engine. Fixed in
+ `api/_lib/glance-adaptive.js`; **this one still needs a deploy.**
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.
diff --git a/prompts/finish/_context/backlog-00-INDEX.md b/prompts/finish/_context/backlog-00-INDEX.md
index c468b7c71..a73a6121d 100644
--- a/prompts/finish/_context/backlog-00-INDEX.md
+++ b/prompts/finish/_context/backlog-00-INDEX.md
@@ -41,11 +41,11 @@ observable health, so 01 to 03 come first.
| # | Work order | Blocked on | Owner action needed |
|---|---|---|---|
| 01 | [x402 settle: clear `fee_runway_exhausted`](../902-backlog-01-x402-settle-runway.md) | capital and the deploy (three more code defects found and fixed 2026-09-04, incl. a thin top-up that funded the wrong wallet) | SOL to the economy master, and the deploy that carries the ordering fix; the config levers are already applied |
-| 05 | [R2 bucket CORS: verify, then fix at the origin](../906-backlog-05-r2-bucket-cors.md) | one credential | mint an R2 admin token |
+| 05 | [R2 bucket CORS: verify, then fix at the origin](../906-backlog-05-r2-bucket-cors.md) | two credentials (re-measured 2026-09-09, both surfaces still fail) | first re-set `S3_SECRET_ACCESS_KEY` (object storage is DOWN, ISSUES.md item 10), then mint an R2 admin token |
| 07 | [BNB testnet: deploy the two finished contracts](../910-backlog-07-bnb-testnet-deploys.md) | one funded EOA | send tBNB to `0x1C4918894dfA5eE11cfF9629B458b5169Cfa3871` (faucet is reCAPTCHA-gated) |
| 08 | [OKX chat bot: move off the codespace](../907-backlog-08-okx-chat-bot-always-on.md) | **deployed 2026-09-04**; only the reply lane is blocked | clear the GCP billing hold so the bot can author replies |
| 09 | [Telegram bots: durable hosting for both feeds](../908-backlog-09-telegram-bots-durability.md) | **done**, verified live 2026-09-02 | clear the commit gate on its file update |
-| 10 | [x402scan listing: finish the last three steps](../909-backlog-10-x402scan-listing.md) | the deploy (the facilitator listing itself is live) | approve the deploy, then one wallet signature to re-register the origin |
+| 10 | [x402scan listing: finish the last three steps](../909-backlog-10-x402scan-listing.md) | **the deploy landed 2026-09-08**; only the origin registration is left (re-measured 2026-09-09) | one SIWX wallet signature at x402scan `/resources/register` for origin `https://three.ws`; no funds move |
---
@@ -92,8 +92,18 @@ both feeds were verified running on Cloud Run on 2026-09-02 (`Ready=True`, webso
$1,055 of volume to our facilitator, and their own crawler replayed against production returns
4,519 stable items with no duplicates). What was left was on our side: their registration flow
reads `/openapi.json`, which hand-enumerated 24 of the 75 live paid services, so 52 endpoints
-answered a valid 402 and could not be listed. That is fixed in the tree and ships with the next
-deploy, after which one wallet signature re-registers the origin.
+answered a valid 402 and could not be listed. **That shipped on 2026-09-08** (production
+`880bdcef8`), so the document now declares 82 paid paths. Re-measured 2026-09-09 by running
+x402scan's own discovery library against production and by
+`npm run preview:x402scan-registration`, which agrees with it endpoint for endpoint: 123
+registrable endpoints declared, 63 already listed, **60 rows a registration run would add and
+0 it would deprecate**, 59 of the 60 answering a spec-valid 402 to a bare probe. The run is
+purely additive, so the only step left is one owner wallet signature. Two claims from the
+2026-09-02 pass are now false and were corrected in the runbook: the five "503
+`settlement_unavailable`" endpoints all answer a valid 402 today (the sponsor floor bites at
+settle time, not at challenge time, which stays order 01's problem), and `ring-settle` /
+`three-buy` are `discoverable: false` internal ring machinery that must stay unlisted rather
+than being a gap to close.
## Shared rules (every work order obeys these)
diff --git a/prompts/finish/_context/backlog-PROGRESS.md b/prompts/finish/_context/backlog-PROGRESS.md
index cead0232b..557f27bfc 100644
--- a/prompts/finish/_context/backlog-PROGRESS.md
+++ b/prompts/finish/_context/backlog-PROGRESS.md
@@ -1620,3 +1620,151 @@ Left: **the GCP billing hold, owner only.** Vertex denies every call, so chat is
durably and no reply is authored. Nothing needs redeploying when it clears: the credential
probe re-runs every 15 minutes and flips readiness on its own. Do NOT restart the codespace
stopgap; Cloud Run owns the single-writer state object now.
+
+## 2026-09-09: 05 R2 bucket CORS
+
+Measured (all three surfaces, from raw `curl` and from the repaired probe, no bucket
+credentials used):
+
+| Surface | Result |
+|---|---|
+| Site edge `three.ws/avatars/*.glb`, foreign origin GET | PASS, `access-control-allow-origin: *`. |
+| Site edge, same route, `OPTIONS` preflight | PASS, `204` with `access-control-allow-headers: range`. The 2026-09-04 preflight fix is now LIVE (prod at `880bdcef8`), so that line moves from "ships with the next deploy" to verified. |
+| Public bucket host `pub-*.r2.dev` GET/HEAD, foreign origin | FAIL, unchanged. On a real `200` object, `example.org` gets no `access-control-allow-origin`; `three.ws` and `localhost:3000` get their origin echoed with `Vary: Origin`. That differential is the proof the live read rule is still the old allowlist, not the world-open `*`. |
+| Presigned `PUT` preflight on the S3 endpoint | Mixed, unchanged. `204` for `three.ws`, `*.vercel.app`, `localhost:3000`; `403` for `www.three.ws`, `*.app.github.dev`, `localhost:5173`, `example.org`. |
+
+So the item does NOT close: surfaces 1 and 2 both still fail and the fix needs the
+admin token. It stays in ISSUES.md as item 9, dates refreshed.
+
+Did:
+- Repaired `--probe`, which was exiting 1 with nothing measured. It sourced the
+ upload host only from `/api/forge-upload`, and that route returns `503` while
+ object storage is unhealthy, which is exactly now. It now tries three presign
+ routes, accepts explicit `--endpoint=`/`--bucket=` (both non-secret), and when
+ the write host is still unknown it measures and reports the read rule instead
+ of aborting, showing `skip` in the write column. The one-command re-check that
+ ISSUES.md and three docs advertise works again.
+- Refreshed the measurement dates in `docs/media-api.md`,
+ `docs/character-library.md` and both embed tutorials, and documented the new
+ probe flags in `scripts/README.md`.
+- Filed a NEW production outage found while measuring: ISSUES.md item 10.
+ `object_storage` is `down` with `credentialFault: true`, the bucket answering
+ `SignatureDoesNotMatch`. The access key id is accepted, so the secret is wrong.
+ Uploads `503`, the avatar and object libraries return `{"total":0}`, and forge
+ image generation is 0/30 over 6 hours.
+
+The two doc-cleanup lines in the work order were already satisfied by the
+2026-09-04 pass: the script warns against `vercel env pull` rather than
+instructing it, and the `/api/glb` docs already state per-host when the proxy is
+needed and when a direct fetch is fine. Verified both rather than assuming.
+`npm run audit:docs` clean; the four R2/CORS tests pass.
+
+Left: two owner actions, in this order.
+1. Re-set `S3_SECRET_ACCESS_KEY` (Secret Manager `s3-secret-access-key`) to the
+ R2 token's SHA-256 digest. Reading and rotating that secret is gated from this
+ machine. This is the urgent one: it is a live outage.
+2. Mint an "Admin Read & Write" R2 token for `chatty-storage`, put it in
+ `.env.local` as `R2_ACCESS_KEY_ID`/`R2_SECRET_ACCESS_KEY`, run
+ `node scripts/set-r2-cors.mjs`, confirm with `--probe`.
+ Doing this before (1) buys nothing: a correct CORS policy on a bucket we
+ cannot authenticate to changes nothing users can see.
+
+The work order file stays on disk: its "policy correct and applied" line is
+owner-gated.
+
+## 2026-09-09: 10 x402scan listing (the deploy landed; only the signature is left)
+
+Measured, all against live production with no credentials:
+
+- `curl -s https://three.ws/api/version` → `880bdcef8`, revision
+ `three-ws-api-00418-j26`, built 2026-09-08. The `catalogPaidPaths()` fix the
+ 2026-09-02 pass left in the tree has shipped.
+- `curl -s https://three.ws/openapi.json` → **82** `/api/x402/*` paid paths
+ (120 total). The work order predicted 79; the catalog has grown since.
+- `gh pr view 1032 --repo Merit-Systems/x402scan` → `MERGED`
+ 2026-08-11T20:01:45Z, unchanged.
+- Facilitator page live, rendering both fee payers
+ (`WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW`,
+ `GGf9qBhJDCe1UUz4s4Vxq1uPPvcv7UW7sJTuj2Yo5XQj`) and linking `docsUrl`
+ `three.ws/docs/x402-distribution` (200). `/api/x402-facilitator/supported` 200.
+- Discovery endpoint: 4,521 resources, `total` stable across the sweep.
+- `npx vitest run tests/openapi-aggregator.test.js tests/service-catalog.test.js`
+ → 26 passed.
+
+Ran x402scan's own discovery library (`@agentcash/discovery`
+`discoverOriginSchema`) against `https://three.ws` rather than reasoning about
+what it would do: source `openapi`, 123 endpoints, 83 of them `/api/x402/*`, and
+82 of those classified `paid` with the right price and `pricingMode: fixed`. The
+one non-paid classification is correct: `GET /api/x402/forge` is genuinely free
+price discovery and reads `unprotected`, matching the free row already listed
+beside the paid `POST /api/x402/forge`. That answers the question worth
+answering before a signature is spent, because every paid operation declares
+`security: []` and it was not obvious that `x-payment-info` overrides it. It
+does, so our paid endpoints register as paid rows rather than free catalog rows.
+
+Did:
+
+- Added `scripts/x402scan-registration-gap.mjs`
+ (`npm run preview:x402scan-registration`), which reproduces their
+ classify/probe/deprecate pipeline against live production with no third-party
+ dependency. Validated it against the real library: 123 registrable both ways,
+ and zero classification mismatches on the rows it reports as new. It exists
+ because the alternative was freezing a 60-line endpoint list into a document
+ that would rot within a week.
+- Rewrote the runbook entry in
+ [docs/ops/x402-discovery-listings.md](../../docs/ops/x402-discovery-listings.md)
+ with the measured state, wired the script into its inventory table and its
+ registration steps, and corrected two claims the 2026-09-02 entry got wrong.
+
+What a registration run would do now: 123 registrable endpoints declared, 63
+already listed, **60 rows added and 0 deprecated**, 59 of the 60 answering a
+spec-valid 402 to a bare probe. The zero is the point: the run is purely
+additive and cannot drop any of the 63 rows already listed.
+
+Two corrections to the 2026-09-02 entry, both from re-probing rather than
+re-reading:
+
+1. It recorded five endpoints as answering 503 `settlement_unavailable` and
+ therefore unregisterable. False today. `dance-tip`, `feed-health` and
+ `spend-session` all answer a spec-valid 402 advertising USDC and $THREE on
+ Solana mainnet. The sponsor floor bites at settle time, not at challenge
+ time: `/api/healthz` reports `x402.self_facilitator.settle` at 84 ok / 366
+ failed with every failure `fee_wallet_below_floor`, which stays order 01's
+ capital problem and is not a listing blocker.
+2. `ring-settle` and `three-buy` were listed among those five as if they were a
+ gap to close. They are not. Both answer a valid 402 but carry
+ `discoverable: false` and are deliberately absent from the service catalog,
+ so `catalogPaidPaths()` never projects them. They are internal ring
+ machinery, and listing them would let dogfooded volume masquerade as organic
+ third-party demand. They must stay unlisted.
+
+Swept all 98 handlers under `api/x402/` against `/openapi.json` to check for
+more of the defect class the work order fixed: exactly two live-402 handlers are
+absent from the document, and they are those two deliberate exclusions. Every
+other absent handler is a genuinely free or internal helper route
+(`debug`, `echo`, `preflight`, `market`, `my-receipts`, `verify-receipt`, and
+similar). No further gap exists.
+
+One endpoint will not probe-register and should not: `GET
+/api/x402/vanity-premium`. A bare GET browses the premium inventory for free and
+only `?address=<base58>` triggers the 402. Their probe fills required query
+params only, and `address` is genuinely optional, so the probe sees the free
+mode. Marking it required to force a registration would be a lie about the
+route, so it stays unlisted.
+
+Left: one owner action, and nothing else.
+
+- **One SIWX wallet signature** at <https://www.x402scan.com/resources/register>,
+ "Add API" for origin `https://three.ws`. It binds an identity and moves no
+ funds. Run `npm run preview:x402scan-registration` immediately before signing
+ and confirm "would be deprecated" still reads 0.
+- The alternative their repo exposes, the paid `registry-register` x402
+ endpoint, registers one URL per settled payment and would need 60 payments, so
+ the bulk SIWX flow is strictly better.
+- The optional Base leg (CDP Bazaar) is unchanged and still a nice-to-have:
+ three.ws remains absent from that catalog because indexing is triggered by a
+ settle through the CDP facilitator and production has no
+ `X402_BUYER_PRIVATE_KEY`. Solana settlement stays self-hosted and must not be
+ re-pointed for visibility.
+
+The work order file stays on disk: its origin-registration line is owner-gated.