@bongos/core 1.23.22 → 1.24.2

package/docs/file-map.md

@@ -117,6 +117,7 @@
 │   ├── copy-desk/               ← CORE-DOMAIN module (task 1003113 / R02 of goal 1000074, default-on): the COPY half of the design contract — ADR 0081 gave design TOKENS a repo-owned source of truth, text had none. Owns the FLAG (anyone in any role marks a string or a whole surface as needing an artist's attention, with a reason required in BOTH the route and a CHECK constraint) and the QUEUE an artist reads it from. READS R01's committed registry (docs/copy-registry.json, generated by scripts/bongos/copy-inventory.js) and never writes it. NO LIVE CMS is the hard non-goal: no column here could hold replacement text, and copy_no_cms.mjs pins that. Key is `copy-desk`, not `copy` — the branding contract already owns a `copy` block, so the bare word reds the "core carries no module code" fitness check. R03 (task 1003114, ADR 0233) added the PROPOSAL: an artist writes the replacement wording and it becomes a Bongos task carrying a fenced copy-proposal patch — no row, NO second migration (a proposals table is the forbidden column with extra steps), and scripts/bongos/copy-apply.js lands it as a real diff under a claim. BV2.TW05 (task 1004316, ADR 0341 D8) added Tweak Mode's three derived READS — GET /copy-desk/pages, /copy-desk/pages/:pageId, /copy-desk/tally: page status and count, changelog, drift, "N of M tweaked" per surface, and the artist's tally — over the page-tweak tasks (lifecycle port), docs/page-inventory.json and docs/page-readings.json (both now in the publish manifest), with no status table. BV2.TW06 (task 1004317, ADR 0341 D2, D5, D6) added its first two page WRITES: POST /copy-desk/pages/:pageId/claim (an artist-craft builder opens or takes the page's tweak round as a web-claimed task, through the lifecycle port's webClaimPageTweak, under an advisory lock on the page) and POST /copy-desk/pages/:pageId/asks (anyone files a page ask, a copy_desk_flags row with scope 'page', added by copy_desk_002_page_asks.sql). CLAUDE.md, module.json, registry.js, flags.js, proposals.js, pages.js (the page-tweak block format), page-status.js (the pure derivation), page-data.js (the page artifacts' read side), routes/copy-desk.js, migrations/copy_desk_001_flags.sql, migrations/copy_desk_002_page_asks.sql, tests/{copy_flags,copy_queue,copy_no_cms,copy_proposals,copy_page_status}.mjs + tests/fixtures/page-tweak.cjs. Its hall surface lives with hall-ui (public/copy-desk.{html,js,css}), per the one-key-per-web-surface precedent. skills/tweak/SKILL.md is the /tweak skill (contributes.skills; moved out of .claude/skills/ in task 1004471, hidden from the model listing, typed as /tweak).
 │   ├── page-notes/              ← the artist's page feedback docs (task 1004496, default-on): the Artistry palette button's store. A doc about one hall page, with up to eight reference images (stored in the DB, images only), turned into ideas by an AI split on submit and kept as the page's reference (?note=N). Apart from copy-desk, which may hold no wording. module.json, CLAUDE.md, notes.js (pure), split.js, db.js, routes/, migrations/.
 │   ├── ai-studio/               ← AI generation for artists (task 1004916, ADR 0392, default-off; hub first): a sketch or image set plus a prompt gets a Gemini reply and generated images on our key (processor-held balance, one named price multiplier, funds held first, released on failure) or the builder's own key (no charge). Keys entered only in Settings, never leave the server. module.json, CLAUDE.md, routes/.
+│   ├── market-watch/            ← Market Watch (task 1004935, goal 1000137, default-off): a weekly AI watch on a project's competitors, partners and topics. No routes yet; the manifest declares spend.requiresPayer. Kept out of the creation picker (HUB_ONLY_MODULES) until it does something. Data layer (task 1004936): migrations/ (market_watch_* tables), db.js (read queries), seed.js + seed/ (the 2026-10-28 research, hub only), pollers/hub-seed.js. module.json, CLAUDE.md.
 │   ├── raise/                   ← the /raise investor page (task 1004847, ADR 0384, default-off; hub only): password-gated for investors (signing in accepts the NDA, non-binding interest), edited in place by any active builder with every change logged. The copy in content/ is the owner's words — never reword it in code. module.json, CLAUDE.md, raise.js (pure), page.js, web.js (the GET-only raise.web port core mounts at /raise), db.js, routes/ (every write), migrations/, content/, views/, public/.
 │   ├── npm-release/             ← the deploy page for a project that publishes an npm package from GitHub (task 1002622, default-OFF — on only in the Bongos hall, which publishes @bongos/core). "Where the work is": every task finished in the last 14 days, placed in the stage it has actually reached (not merged · merged, no version yet · published, not running here · running here, not released · released · in no version), plus the version history — each version's tasks. The version↔task join reads the release-notes.json the package itself carries (scripts/bongos/release-notes.js writes it at pack time), streamed out of the NEWEST version's npm tarball in-process (no child process, no sync call) when the running core's own copy stops short. module.json, work.js (the reading + the stage placement — the packument, tarball stream and tar reader it uses are the core's src/bongos/package-registry.js, reached through the doorway's readPackageRegistry since task 1004296), routes/work.js (GET /npm-release/work, gated core.pin.move like the page), public/work.{js,css} (the two sections /deploy lends it: #nr-work, #nr-versions). Task 1004301 added the same line on a task's own page: routes/task-where.js (GET /npm-release/task/:id, any signed-in builder — it shows nothing not already public) + public/task-widget.js, injected into task.html by the loader's uiSections seam (hallWidgetScripts file task-widget.js) to fill #task-contrib on otb:task-shown. Tests sit at the repo root — tests/npm_release_{work,page}.mjs — because a default-off module's own tests/ is skipped by the unit runner.
 │   ├── render-deploy/           ← the deploy page for a project whose app deploys through Render (task 1004270, default-OFF). The service's Render deploys, each tied to its commit and the Bongos tasks in it, what is live now, and deploy + roll back behind a two-step confirm the server also holds. The owner's Render key is never stored: it rides each request in a header. Uses the one Render client, scripts/bongos/render-api.js, and its ownerId guard. `deploys.js` (shaping + ledger), `render.js` (key + client), `routes/` (app, history, act), `public/deploy.js` (the page, mounted in /deploy), `migrations/` (one two-id table)

package/docs/module-api-changelog.md

@@ -3259,5 +3259,12 @@ is load-bearing: the script throws rather than guess if it is missing, and
         landed since 1.23.20 with no explicit bump. run 40804017640. (task 1002620)
   1.23.22 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
         landed since 1.23.21 with no explicit bump. run 40815670165. (task 1002620)
+  1.24.0 — taskNeeds: what a task needs (owner, server) and what a builder can do,
+        read fresh per call like rank (src/bongos/task-needs.js; task 1004950, ADR 0395).
+        The lifecycle feed and claim gate apply it. Additive, so MINOR.
+  1.24.1 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.24.0 with no explicit bump. run 40985289858. (task 1002620)
+  1.24.2 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.24.1 with no explicit bump. run 41000649913. (task 1002620)
 ---------------------------------------------------------------------------
 ```

package/docs/onboarding/diagrams/03-drachmae-karma.mmd

@@ -2,9 +2,9 @@
 title: Credits & karma — where each comes from, where each goes  (AUTO-GENERATED from live facts — do not hand-edit; see scripts/bongos/gen-diagrams.js)
 ---
 flowchart LR
-    subgraph CURRENCY["CREDITS  (the builder reward — equity / reputation, a stake, not a spendable currency)"]
+    subgraph CURRENCY["CREDITS  (the builder reward — a contribution meter: not money, not equity, not a spendable currency)"]
         direction TB
-        D_TOKEN["Ship a SESSION — the main reward\nround(true_cost_usd × 1.20) cents — cost-plus on real token spend\n(LIVE: priced server-side from token counts; ADR 0054, idempotent per session)"]
+        D_TOKEN["Ship a SESSION — the main reward\nround(true_cost_usd × 1.20) — sized by real token spend in USD\n(LIVE: priced server-side from token counts; ADR 0054, idempotent per session)"]
         D_SHIP["SHIP a TASK — books when the code lands on main, not at confirm\ncredits_reward × kind multiplier (0.8–1.5×)\n+ 25% idea-promotion bonus to the capturer\n(LIVE: ADR 0023; pay-on-land ADR 0120; withheld entirely on a cost-plus-only instance, ADR 0146)"]
         D_ACH["Unlock an achievement\nachievements.credit_bonus (LIVE: 16 seeded)\n+ small net-negative-ship bonus"]
         D_BOUNTY["Red-team / security bounty\ncredits payout by severity\n(rate card LIVE: R65 #284 — src/bongos/security.js + shown on /builders;\nawarding still PLANNED: R67 #286 + vulnerability_reports R63 #282)"]
@@ -16,7 +16,7 @@ flowchart LR
         D_ACH --> D_BAL
         D_BOUNTY -.PLANNED.-> D_BAL
 
-        D_SPEND["Spent on: nothing yet.\nCredits are EQUITY / reputation — a stake, not a\nspendable currency. They persist losslessly across exit (migration 025)."]
+        D_SPEND["Spent on: nothing yet.\nCredits measure contribution — never money, never\nredeemable, never equity (ADR 0387). They persist losslessly across exit (migration 025)."]
         D_BAL --> D_SPEND
     end
 

package/docs/onboarding/diagrams/README.md

@@ -42,7 +42,7 @@ The 16-value reserved rank enum (migration 023) in three Greek bands, which rank
 Source: [`02-rank-ladder.mmd`](02-rank-ladder.mmd)
 
 ### 3. Example & karma — sourcing and spending
-Where each comes from and where each goes. Key facts: **example = credits** (same thing, in-world name), they are **equity, not a spendable currency**, and the **primary source is now a cost-plus reward on each shipped session** — `round(true_cost × 1.20)` ([ADR 0054](../../adr/0054-session-token-reward-cost-plus.md)) — alongside per-task `credits_reward × kind multiplier` ([ADR 0023](../../adr/0023-kind-multipliers-and-idea-bonus.md)), achievements, and the (rate-card-live) security bounty. Karma is a separate peer-trust signal that does **not** gate rank promotions; its LIVE/PLANNED state tracks its backing tasks (R25/R32/R26). The full write-up is [`docs/onboarding/example-and-karma.md`](../drachmae-and-karma.md).
+Where each comes from and where each goes. Key facts: **example = credits** (same thing, in-world name), they are **a contribution meter — not money, not equity, not a spendable currency** ([ADR 0387](../../adr/0387-two-ledgers-credits-measure-work-money-stays-with-the-processor.md)), and the **primary source is now a cost-plus reward on each shipped session** — `round(true_cost × 1.20)` ([ADR 0054](../../adr/0054-session-token-reward-cost-plus.md)) — alongside per-task `credits_reward × kind multiplier` ([ADR 0023](../../adr/0023-kind-multipliers-and-idea-bonus.md)), achievements, and the (rate-card-live) security bounty. Karma is a separate peer-trust signal that does **not** gate rank promotions; its LIVE/PLANNED state tracks its backing tasks (R25/R32/R26). The full write-up is [`docs/onboarding/example-and-karma.md`](../drachmae-and-karma.md).
 
 ![Example and karma](03-drachmae-karma.png)
 

package/docs/onboarding/drachmae-and-karma.md

@@ -1,4 +1,4 @@
-# Example & karma — how you get paid, and how you earn trust
+# Example & karma — how your work is counted, and how you earn trust
 
 *The complete reference for the two reputation tracks in Bongos. The [primer](primer.md) gives you the one-paragraph version; this is the full picture, kept honest against the live system. ~8 minutes.*
 
@@ -8,8 +8,8 @@
 
 ## The 30-second version
 
-- **Example** (the code calls them *credits*) are your **equity** in Example. You earn them by shipping work, and they only ever go up. They are a score and a stake — **not** a currency you spend on anything in-game.
-- The **headline change (June 2026):** most of your example now come from a **cost-plus reward on each shipped session** — we pay you the real API cost of the work you did, **plus 20%**. Expensive, real work pays more than declaring a big number ever did.
+- **Example** (the code calls them *credits*) are a **contribution meter**: they measure the work you did on this project. They are **not money, not redeemable and not equity** ([ADR 0385](../adr/0385-money-lives-with-a-processor-credits-stay-a-project-meter.md), [ADR 0387](../adr/0387-two-ledgers-credits-measure-work-money-stays-with-the-processor.md)). You earn them by shipping work. Any pay — cash, or equity a project grants — is set by the project separately.
+- The **headline change (June 2026):** most of your example now come from a **cost-plus reward on each shipped session** — sized by the real API cost of the work you did in USD, **plus 20%**. Expensive, real work counts for more than declaring a big number ever did.
 - **Karma** is a *separate* signal. It measures **peer trust** — how other trusted builders rate your work — not how much you shipped. It is surfaced on your profile and the leaderboard, and it feeds your "builder strength" score. It is **not** a gate on rank promotions.
 - A **monthly budget cap** ($50 by default) limits how much you can *spend*; it's the cost side of the same coin the reward is computed from.
 
@@ -19,11 +19,11 @@
 
 ### What they are
 
-Example are the in-world name for the `total_credits` counter on your builder row. The owner's framing ([ADR 0054](../adr/0054-session-token-reward-cost-plus.md)) is that **example are equity** — units of ownership in the thing you're helping build. Practically, today, they are:
+Example are the in-world name for the `total_credits` counter on your builder row. They are a **project-scoped contribution meter** ([ADR 0387](../adr/0387-two-ledgers-credits-measure-work-money-stays-with-the-processor.md)): they belong to the project that issued them, cannot be bought or transferred, and are never cashed out. An older framing in [ADR 0054](../adr/0054-session-token-reward-cost-plus.md) called them equity; the owner retired that on 2026-10-29. Equity, if a project offers any, is granted by the project separately. In practice they are:
 
 - **Append-only.** Every award is a row in `credit_log`; the `total_credits` counter is maintained by a database trigger. History is never rewritten — a correction is a new (sometimes negative) row, never an edit.
 - **Persistent across exit.** If you leave and come back, your example are still there (migration 025). They are reputation, not a session balance.
-- **Not spendable.** There is no shop, no sink, nothing to buy with them. They are a *score and a stake*. (This may change in a future version; today it does not.)
+- **Not spendable, not money.** There is no shop, no sink, nothing to buy with them, and no dollar value is read off them. They measure work done.
 - **Public.** Your total is visible on the [builders' hall](https://example.com/builders) leaderboard.
 
 ### How you earn them
@@ -32,26 +32,26 @@ There are several sources. They all land in the same `credit_log` and roll up in
 
 #### 1. The cost-plus session reward — *the main one* ([ADR 0054](../adr/0054-session-token-reward-cost-plus.md))
 
-When you **ship** a session, the server looks at the LLM tokens that session actually burned, prices them, and pays you:
+When you **ship** a session, the server looks at the LLM tokens that session actually burned, prices them, and credits you:
 
 ```
-example = round( true_cost_usd × 1.20 )            // whole example (1 drachma = $1)
+example = round( true_cost_usd × 1.20 )            // whole example, sized by cost in USD (not worth USD)
                                   └─ REWARD_MARGIN_PCT = 20 (a code constant in src/bongos/db.js)
 ```
 
 The important details, because they're designed to be fair *and* un-gameable:
 
-- **The cost is computed server-side**, from the per-model token counts your ship uploads (`session_records.model_usage`), priced via the locked list-price table in `src/bongos/llm-pricing.js`. **You never send a dollar figure** — a client can't inflate its own payout.
-- **It's the API *list* price, deliberately** — not your discounted subscription cost. If you got those tokens cheaply (e.g. on a flat Claude Code subscription), the spread between list price and what you actually paid is routed to *you* as profit, on top of the 20%. That's intentional: it's how the reward funds your time and your ideas.
+- **The cost is computed server-side**, from the per-model token counts your ship uploads (`session_records.model_usage`), priced via the locked list-price table in `src/bongos/llm-pricing.js`. **You never send a dollar figure** — a client can't inflate its own award.
+- **It's the API *list* price, deliberately** — not your discounted subscription cost. If you got those tokens cheaply (e.g. on a flat Claude Code subscription), your credits are still sized by the list price, on top of the 20%. That's intentional: the meter counts the work, not what you happened to pay for it.
 - **PASS-gated.** Only a *successful ship* uploads a session record. A session that burned tokens and shipped nothing earns nothing.
-- **Idempotent per session.** Re-shipping or retrying the same session is a true no-op — keyed on `session_id`, you can't get paid twice.
+- **Idempotent per session.** Re-shipping or retrying the same session is a true no-op — keyed on `session_id`, you can't be credited twice.
 - **Reversible.** A bad award is undone with a compensating negative `credit_log` row; the trigger nets it out. History stays intact.
 
-> **Why pay for cost at all — doesn't that reward waste?** It can, and that was accepted on purpose ([ADR 0054](../adr/0054-session-token-reward-cost-plus.md)). The guardrails are: you only get paid for sessions that *ship*; example are *equity*, so padding your own cost dilutes a pool you hold (early builders self-police); and the [BFG session-inefficiency evaluator](../adr/0027-bfg-session-inefficiency-evaluator.md) already flags wasteful sessions, so a future version can discount the reward by an efficiency factor. The stated direction is to move toward market/bidding pricing once there's a real multi-builder pool.
+> **Why count cost at all — doesn't that reward waste?** It can, and that was accepted on purpose ([ADR 0054](../adr/0054-session-token-reward-cost-plus.md)). The guardrails are: you only earn for sessions that *ship*; and the [BFG session-inefficiency evaluator](../adr/0027-bfg-session-inefficiency-evaluator.md) already flags wasteful sessions, so a future version can discount the reward by an efficiency factor. The stated direction is to move toward market/bidding pricing once there's a real multi-builder pool.
 
 #### 2. Per-task credits, adjusted by *kind* ([ADR 0023](../adr/0023-kind-multipliers-and-idea-bonus.md))
 
-Every task carries a `credits_reward` an author set when scoping it. When the task is **confirmed** (verification passes — see the [lifecycle](#where-in-the-lifecycle-credits-land)), you're paid that reward **times a multiplier for the kind of work**:
+Every task carries a `credits_reward` an author set when scoping it. When the task is **confirmed** (verification passes — see the [lifecycle](#where-in-the-lifecycle-credits-land)), you're credited that reward **times a multiplier for the kind of work**:
 
 | Kind | × | Why |
 |---|---|---|
@@ -97,7 +97,7 @@ active ──▶ completed ──▶ confirmed ──▶ shipped
 
 ### One honest caveat: a drachma means two things
 
-We knowingly run two conventions on the same ledger ([ADR 0054](../adr/0054-session-token-reward-cost-plus.md)): a *unitless author estimate* (the per-task path) and a *whole-dollar drachma of real cost + 20%* (the session-reward path). That inconsistency is a deliberate MVP trade-off, recorded so it's a known decision and not a latent bug. A future version may reconcile them.
+We knowingly run two conventions on the same ledger ([ADR 0054](../adr/0054-session-token-reward-cost-plus.md)): a *unitless author estimate* (the per-task path) and a *drachma sized by real cost in USD + 20%* (the session-reward path). [ADR 0387](../adr/0387-two-ledgers-credits-measure-work-money-stays-with-the-processor.md) settles it without converting anything: credits stay a work meter, used only as relative weight inside a project, and any money lives on a separate record held by a payment processor. No credit is ever read as dollars.
 
 ---
 
@@ -162,11 +162,11 @@ Karma is evidence an Archon *can weigh* when deciding a discretionary promotion,
 | Earned by | Shipping (cost-plus reward, per-task credits, bonuses) | Metic+ peer votes, ratification, idea promotion |
 | Direction | Only goes up | Can go up or down |
 | Who can grant | The system, automatically, on a successful ship | Metic+ builders (votes) + system signals |
-| Spendable? | No — equity/score | No — trust signal |
+| Spendable? | No — a contribution meter, not money or equity | No — trust signal |
 | Gates promotions? | No (Xenos→Thetes is by ship count) | No (informs, doesn't gate) |
 | Lives in | `builders.total_credits` / `credit_log` | `builders.karma` / `karma_log` |
 
-Both are reputation. Neither is a spendable currency today. You don't have to *do* anything special to start earning either — claim a task, do good work, ship it, and both tracks take care of themselves.
+Both are reputation. Neither is money or a spendable currency. You don't have to *do* anything special to start earning either — claim a task, do good work, ship it, and both tracks take care of themselves.
 
 ---
 

package/docs/onboarding/primer.md

@@ -68,9 +68,9 @@ So the sandbox is short: ship three small `newcomer_friendly` tasks and the city
 
 ## Example and karma
 
-Two parallel reputation tracks. You don't need to *do* anything special to earn either — claim a task, do good work, ship it, and the system tracks both. The full mechanics (formulas, the kind table, the budget cap, every karma source) live in **[Example & karma — how you get paid](drachmae-and-karma.md)**; here's the shape of it.
+Two parallel reputation tracks. You don't need to *do* anything special to earn either — claim a task, do good work, ship it, and the system tracks both. The full mechanics (formulas, the kind table, the budget cap, every karma source) live in **[Example & karma — how your work is counted](drachmae-and-karma.md)**; here's the shape of it.
 
-- **Example** (called "credits" in code) are your **equity** in the project — a score and a stake, *not* a currency you spend on anything. They only go up, and they persist if you leave and come back. Most of your example now come from a **cost-plus reward on each shipped session**: the server prices the LLM tokens your work actually burned and pays you that real cost **plus 20%** ([ADR 0054](../adr/0054-session-token-reward-cost-plus.md)). On top of that, each task pays its `credits_reward` adjusted by the *kind* of work (a captured learning or a resolved blocker is worth 1.5×; cleanup 0.8×), and capturing an idea that someone else then ships earns you a 25% bonus ([ADR 0023](../adr/0023-kind-multipliers-and-idea-bonus.md)). Credits land at the `confirmed → shipped` edge — when your code actually merges and deploys, not when verification passes ([ADR 0120](../adr/0120-pay-on-land-and-builder-owned-rebase-gate.md)). Which of those two streams actually pays is per-instance config ([ADR 0146](../adr/<redacted><redacted>.md)): the default pays both, while a `cost-plus-only` instance pays the session reward alone and treats each task's `credits_reward` as an advertised estimate only. See the standings on [/builders](https://example.com/builders).
+- **Example** (called "credits" in code) are a **contribution meter** for the project — they measure your work and are *not* money, not redeemable and not equity ([ADR 0387](../adr/0387-two-ledgers-credits-measure-work-money-stays-with-the-processor.md)); any pay or equity is set by the project separately. They persist if you leave and come back. Most of your example now come from a **cost-plus reward on each shipped session**: the server prices the LLM tokens your work actually burned and credits you an amount sized by that real cost in USD **plus 20%** ([ADR 0054](../adr/0054-session-token-reward-cost-plus.md)). On top of that, each task pays its `credits_reward` adjusted by the *kind* of work (a captured learning or a resolved blocker is worth 1.5×; cleanup 0.8×), and capturing an idea that someone else then ships earns you a 25% bonus ([ADR 0023](../adr/0023-kind-multipliers-and-idea-bonus.md)). Credits land at the `confirmed → shipped` edge — when your code actually merges and deploys, not when verification passes ([ADR 0120](../adr/0120-pay-on-land-and-builder-owned-rebase-gate.md)). Which of those two streams actually pays is per-instance config ([ADR 0146](../adr/<redacted><redacted>.md)): the default pays both, while a `cost-plus-only` instance pays the session reward alone and treats each task's `credits_reward` as an advertised estimate only. See the standings on [/builders](https://example.com/builders).
 
 - **Karma** is a *separate* signal that measures **peer trust** — how other builders rate the *way* you work, not how much you ship. It's earned when Metic-and-above builders upvote your confirmed work (tallied weekly), when a proposal of yours is ratified, and when you capture ideas; it can also go *down* if you break things. Karma shows up on your profile (with a 30-day trend) and as a sortable column on the leaderboard, and it feeds your "builder strength" score. **It does not gate rank promotions** — those happen automatically by ship count (Xenos → Thetes after three ships) or by an Archon's deliberate decision. A builder who ships fast but breaks things gains example and loses karma; a builder who ships thoughtfully gains both.
 

package/docs/page-inventory.json

@@ -10,10 +10,10 @@
     "An id changes only when the host prefix, the data-page value or the file name changes; that is a rename, and records keyed on the old id move with it."
   ],
   "counts": {
-    "pages": 47,
+    "pages": 48,
     "surfaces": 3,
-    "with_states": 40,
-    "states": 353
+    "with_states": 41,
+    "states": 363
   },
   "surfaces": [
     {
@@ -22,7 +22,7 @@
       "at": "modules/hall-ui/public",
       "answers_at": "host prefix builders.",
       "origin": "https://builders.{apex}",
-      "pages": 35
+      "pages": 36
     },
     {
       "id": "landing",
@@ -42,6 +42,47 @@
     }
   ],
   "pages": [
+    {
+      "id": "builders:ai-studio",
+      "surface": "builders",
+      "module": "hall-ui",
+      "page": "ai-studio",
+      "id_from": "data-page",
+      "title": "Studio",
+      "document_title": "Studio — {{worldName}}",
+      "path": "/ai-studio",
+      "url": "https://builders.{apex}/ai-studio",
+      "files": [
+        "modules/hall-ui/public/ai-studio.html",
+        "modules/hall-ui/public/style.css",
+        "modules/hall-ui/public/studio.css",
+        "modules/hall-ui/public/ai-studio.css",
+        "modules/hall-ui/public/dom-utils.js",
+        "modules/hall-ui/public/shell-trail.js",
+        "modules/hall-ui/public/craft-mode.js",
+        "modules/hall-ui/public/shell.js",
+        "modules/hall-ui/public/palette.js",
+        "modules/hall-ui/public/tweak-editor-lib.js",
+        "modules/hall-ui/public/studio-lib.js",
+        "modules/hall-ui/public/ai-studio-lib.js",
+        "modules/hall-ui/public/ai-studio.js"
+      ],
+      "states_files": [
+        "modules/hall-ui/public/ai-studio.states.json"
+      ],
+      "states": [
+        "pick",
+        "describe",
+        "make",
+        "waiting",
+        "result",
+        "result-own",
+        "failed",
+        "balance",
+        "balance-all",
+        "out"
+      ]
+    },
     {
       "id": "builders:atlas",
       "surface": "builders",
@@ -101,7 +142,8 @@
         "modules/hall-ui/public/task-detail.js",
         "modules/hall-ui/public/blockers-lib.js",
         "modules/hall-ui/public/hall-ask.js",
-        "modules/hall-ui/public/blockers.js"
+        "modules/hall-ui/public/blockers.js",
+        "modules/hall-ui/public/blockers-by-person.js"
       ],
       "states_files": [],
       "states": []
@@ -210,7 +252,8 @@
         "modules/hall-ui/public/shell.js",
         "modules/hall-ui/public/palette.js",
         "modules/hall-ui/public/collab-lib.js",
-        "modules/hall-ui/public/collab.js"
+        "modules/hall-ui/public/collab.js",
+        "modules/hall-ui/public/blockers-by-person.js"
       ],
       "states_files": [
         "modules/hall-ui/public/collab.states.json"
@@ -506,6 +549,7 @@
         "modules/hall-ui/public/oversight.css",
         "modules/hall-ui/public/hall-ask.css",
         "modules/hall-ui/public/goals.css",
+        "modules/hall-ui/public/notes-panel.css",
         "modules/hall-ui/public/dom-utils.js",
         "modules/hall-ui/public/shell-trail.js",
         "modules/hall-ui/public/craft-mode.js",
@@ -526,6 +570,7 @@
         "modules/hall-ui/public/goal-author-lib.js",
         "modules/hall-ui/public/goal-author.js",
         "modules/hall-ui/public/hall-ask.js",
+        "modules/hall-ui/public/notes-panel.js",
         "modules/hall-ui/public/goals-render.js",
         "modules/hall-ui/public/goals-page.js"
       ],
@@ -566,7 +611,8 @@
         "modules/hall-ui/public/palette.js",
         "modules/hall-ui/public/hall-kit.js",
         "modules/hall-ui/public/board-lib.js",
-        "modules/hall-ui/public/government.js"
+        "modules/hall-ui/public/government.js",
+        "modules/hall-ui/public/government-access.js"
       ],
       "states_files": [
         "modules/hall-ui/public/government.states.json"
@@ -1037,6 +1083,7 @@
         "modules/hall-ui/public/settings.js",
         "modules/hall-ui/public/settings-sessions.js",
         "modules/hall-ui/public/settings-passkeys.js",
+        "modules/hall-ui/public/settings-ai-keys.js",
         "modules/hall-ui/public/settings-interaction.js",
         "modules/hall-ui/public/settings-specialities.js",
         "modules/hall-ui/public/settings-render.js",
@@ -1180,6 +1227,7 @@
         "modules/hall-ui/public/approval-queue.js",
         "modules/hall-ui/public/tweak-editor-lib.js",
         "modules/hall-ui/public/studio-lib.js",
+        "modules/hall-ui/public/ai-studio-lib.js",
         "modules/hall-ui/public/studio.js"
       ],
       "states_files": [
@@ -1221,6 +1269,7 @@
         "modules/hall-ui/public/record.css",
         "modules/hall-ui/public/hall-ask.css",
         "modules/hall-ui/public/task.css",
+        "modules/hall-ui/public/notes-panel.css",
         "modules/hall-ui/public/dom-utils.js",
         "modules/hall-ui/public/shell-trail.js",
         "modules/hall-ui/public/craft-mode.js",
@@ -1232,6 +1281,7 @@
         "modules/hall-ui/public/hall-visual.js",
         "modules/hall-ui/public/claim-action.js",
         "modules/hall-ui/public/hall-ask.js",
+        "modules/hall-ui/public/notes-panel.js",
         "modules/hall-ui/public/task.js"
       ],
       "states_files": [