@bongos/core 1.19.777 → 1.19.779

package/.bongos-core.json

@@ -2,22 +2,22 @@
   "artifact": "bongos-core",
   "manifest_schema": 1,
   "generator": "scripts/gds/package-core.js",
-  "core_version": "1.19.777",
-  "core_contract": "1.19.777",
-  "source_commit": "8c4c3db04491300feb300426c07f7d4bce19f981",
+  "core_version": "1.19.779",
+  "core_contract": "1.19.779",
+  "source_commit": "1b37b29ce2a7832804f9b44a6982ea25b57643e3",
   "source_ref": "HEAD",
-  "built_at": "2026-09-16T18:55:13.712Z",
+  "built_at": "2026-09-16T20:08:25.581Z",
   "redaction": {
     "model": "docs-redacted+functional-verbatim",
-    "docs_redacted": 486,
+    "docs_redacted": 482,
     "agent_docs_stubbed": 25,
     "functional_verbatim": 2153,
     "rules": 3,
     "gate_literals": 3,
     "gate": "passed"
   },
-  "file_count": 2664,
-  "tree_sha256": "48b4056d95f14a44152bbeafa4b8208f71b3bbb6890cb8fff14b4b5a70f27b10",
+  "file_count": 2660,
+  "tree_sha256": "dbb45ccb2f44e4771d7a73e06e5ac46faea7115961c48cac9da3877e62f2e61c",
   "files": [
     {
       "path": ".claude/skills/ask-for-help/SKILL.md",
@@ -49,21 +49,11 @@
       "mode": "0000644",
       "sha256": "722cb6ec3054b041e6f39e6ae2f1afa7977153cbcb8b005ef943509962c55d05"
     },
-    {
-      "path": ".claude/skills/builder-box/SKILL.md",
-      "mode": "0000644",
-      "sha256": "2c99f7d3dc8bd89a4c3f4f49b32c630b0a18a5acf004d849b1e3564effa00ced"
-    },
     {
       "path": ".claude/skills/builder-claim/SKILL.md",
       "mode": "0000644",
       "sha256": "e98c9fc650b38916f81b453d20035259006160043c4170d36505756b314c4ffa"
     },
-    {
-      "path": ".claude/skills/builder-connect/SKILL.md",
-      "mode": "0000644",
-      "sha256": "5c8f33777f987c6382e7d232c5ceb1883d0a6964365401169cd5941557e93364"
-    },
     {
       "path": ".claude/skills/builder-cost/SKILL.md",
       "mode": "0000644",
@@ -72,12 +62,12 @@
     {
       "path": ".claude/skills/builder-end/SKILL.md",
       "mode": "0000644",
-      "sha256": "29f4456636d782f942b1d0765edadb6735c2ba48d1193edf3f490527155efa6b"
+      "sha256": "e6d9739aca81fdc54897049d2d5926b0923150a2f8866f5d1f5945f1412014f8"
     },
     {
       "path": ".claude/skills/builder-exit/SKILL.md",
       "mode": "0000644",
-      "sha256": "122599d47266260fa79465754a7f975af106a47703987eba46c9e938efde7e3c"
+      "sha256": "9679ffdcb10af1858d45aa1d00be1141b798f167ee5daead42e0f6374e4e9fd4"
     },
     {
       "path": ".claude/skills/builder-key/SKILL.md",
@@ -112,28 +102,18 @@
     {
       "path": ".claude/skills/builder-ship/SKILL.md",
       "mode": "0000644",
-      "sha256": "e4810f288bc5b0a4d33a62c918c76225b16e6b0c2f733a1c95336d6932512060"
+      "sha256": "fee2003d2f6b12f404109217c14f7e0e22ad2abaf073322e08e8079549a136b3"
     },
     {
       "path": ".claude/skills/builder-stage/SKILL.md",
       "mode": "0000644",
-      "sha256": "f4a6d1569f1a41d42e5c27ec6a1f1717ef937e08cd8b8d771f7b68585d26472d"
+      "sha256": "5f3c09420b08538d66dbe0ab858618907c0b92cf82a6aa44fe0eb53004f224c0"
     },
     {
       "path": ".claude/skills/builder-start/SKILL.md",
       "mode": "0000644",
       "sha256": "fd023863bf2f53447be736ac8972423477005cb542c203b4e089d948507d8944"
     },
-    {
-      "path": ".claude/skills/builder-sync/SKILL.md",
-      "mode": "0000644",
-      "sha256": "ed647c782b56f40792676341344f4b31d1a6f05e24c93d947d921b48c8117159"
-    },
-    {
-      "path": ".claude/skills/close-box/SKILL.md",
-      "mode": "0000644",
-      "sha256": "5cac7dffb190e027b9d3f011c35c16924280c07f6c98ecd60f8a44fcb18d2b50"
-    },
     {
       "path": ".claude/skills/design-sync/SKILL.md",
       "mode": "0000644",
@@ -192,7 +172,7 @@
     {
       "path": ".claude/skills/merge-mode/SKILL.md",
       "mode": "0000644",
-      "sha256": "272799b69a445188f6d2c558b01b467d62bb696975c79e08d994c04de81ed54a"
+      "sha256": "ef2c92c34d047186eaa016a99d4679f09be028120b9d61bc92b1a999bf87bec0"
     },
     {
       "path": ".claude/skills/new-project/SKILL.md",
@@ -1347,7 +1327,7 @@
     {
       "path": "docs/adr/0171-profile-rollup-join-and-consent.md",
       "mode": "0000644",
-      "sha256": "e61c6a4a5c03092934ba452d0566f160488ae1c5ebc510ed08a3caeab1bba0a8"
+      "sha256": "943103bc2fcb66b89a06b13a49593d230b90f33bd3dec35aec82078cdd08f54f"
     },
     {
       "path": "docs/adr/0172-editable-rank-roles-substrate-axis.md",
@@ -1407,7 +1387,7 @@
     {
       "path": "docs/adr/0182-project-visibility-two-axes.md",
       "mode": "0000644",
-      "sha256": "b5774a35062d556a9af643b0726408268c8d91f3a6c9273f4bb610510bbb7342"
+      "sha256": "15387fac9c92e30d305444616865b6aab0b0c391ddc91f08656c74b9e71385ad"
     },
     {
       "path": "docs/adr/0183-criteria-close-themselves.md",
@@ -2517,7 +2497,7 @@
     {
       "path": "docs/file-map.md",
       "mode": "0000644",
-      "sha256": "4f45da7f069720b0f6cd29a9e8946b006bc592830630528a606cc2b252f2ee80"
+      "sha256": "c3130f09be6637d33eb1ccdaf4fdadf6adbebdeae3e264f2f845e668c9fc90fa"
     },
     {
       "path": "docs/handoff-template.md",
@@ -2527,7 +2507,7 @@
     {
       "path": "docs/module-api-changelog.md",
       "mode": "0000644",
-      "sha256": "48accd0cc072b560c546805d257d6ac9695ec17a3702aa7434c17b6eb632f819"
+      "sha256": "b5409eae5a7466352e67fee988116c208a7c748e5dd88052f8a2b45a8e58f907"
     },
     {
       "path": "docs/modules-contract.md",
@@ -2597,7 +2577,7 @@
     {
       "path": "docs/onboarding/slash-commands.md",
       "mode": "0000644",
-      "sha256": "174c90095ed45bf107852c017493fdd0fa3f07bdf8fbe69c09ebf77bc00747f2"
+      "sha256": "748df9bec7434093e32f70915f151b9cc6ac67beebbe226b997d81eba327de31"
     },
     {
       "path": "docs/packs/artist.md",
@@ -6102,7 +6082,7 @@
     {
       "path": "modules/platform-identity/platform-identity.js",
       "mode": "0000644",
-      "sha256": "75034fda91db58e923e6838e8eb6aba92277643fe3ed930fce1e4b3b9a4bdc96"
+      "sha256": "c59bc528fb1bb451b1f1b751b2903b763b1d3e892a8a5bbc5144ee97db670cf3"
     },
     {
       "path": "modules/platform-identity/pollers/code-sweep.js",
@@ -6127,7 +6107,7 @@
     {
       "path": "modules/platform-identity/projects-feed.js",
       "mode": "0000644",
-      "sha256": "9a8a22d21089770ec80f709d27f798eab6101cfaead18942c439f7c8689ef041"
+      "sha256": "14166982e6306ff8dd63f476af582970634eb9c210e9afa76166668e351244c9"
     },
     {
       "path": "modules/platform-identity/publish-gate.js",
@@ -6187,7 +6167,7 @@
     {
       "path": "modules/platform-identity/tests/platform-identity.mjs",
       "mode": "0000644",
-      "sha256": "32e6d5edd5e058687a641265e78e319ab4e905a85298e76623826c384d0c6356"
+      "sha256": "da06ab89ee01bf3a704f677e7e50041220916f40cac23fa063c212dc9af2f56d"
     },
     {
       "path": "modules/platform-identity/ui/.gitkeep",
@@ -7632,12 +7612,12 @@
     {
       "path": "package-lock.json",
       "mode": "0000644",
-      "sha256": "620248e6545e156fd98d84b9dc29bdad59a77be39ba3e761a90d62d385255f4d"
+      "sha256": "73c88d2a70b9f77171344eb76f4c5c9f2ecbbc4d1a1b6b3008d636e974b01f9b"
     },
     {
       "path": "package.json",
       "mode": "0000644",
-      "sha256": "d4ebe23ce76cdf1091ce8ab656a5199df19fb171768a947ff7cad259f9262dfd"
+      "sha256": "4c30d22b31621113b656c60c5a7d71d70fc1544326be0d506ca16a242783defd"
     },
     {
       "path": "public-docs/index.html",
@@ -9497,7 +9477,7 @@
     {
       "path": "src/module-api.js",
       "mode": "0000644",
-      "sha256": "3791abffec940edb90c976525b388d122d16ff5613c1ee1a487d6e9f1ad1a1e0"
+      "sha256": "3a9d2a54bc76ea41d67b42be5f2c07da60fcdeec3bbed8f23111163dfa17f1ff"
     },
     {
       "path": "src/module-loader/catalog.js",
@@ -11312,7 +11292,7 @@
     {
       "path": "tests/hub_recent_ships.mjs",
       "mode": "0000644",
-      "sha256": "53c7c8ad2de098d29c9010ed37e43779e8ceda4790018527c7edf45d54e56e80"
+      "sha256": "0d8f07c64f4d17c8c894b2d6395281882efd4e186c5714fe9aab61e2808d4314"
     },
     {
       "path": "tests/idea_capture_grades.mjs",
@@ -12052,12 +12032,12 @@
     {
       "path": "tests/profile_rollup_consent.mjs",
       "mode": "0000644",
-      "sha256": "130672f5f844f2552f98bdc3e7b30fa9d49dd460e81c02a60c5684db6617f804"
+      "sha256": "d63e22b8ddbcbe7e21a59ee907e5a4261bebc067c52de111c32a88f97a172406"
     },
     {
       "path": "tests/profile_route.mjs",
       "mode": "0000644",
-      "sha256": "ef2a58d60f561da1e025cf0958bdcb66072545158a68f3e41b4bc683afbed9d6"
+      "sha256": "d70924dd2ddfc4e05c4b52d9763d76b0a68cf0ed16db6ffd1b07a1834bef0890"
     },
     {
       "path": "tests/profile_ui_cross_project.mjs",
@@ -13257,7 +13237,7 @@
     {
       "path": "tests/visible_projects_feed.mjs",
       "mode": "0000644",
-      "sha256": "a15bfe5f3b664a9daa4f45b80eb7a5bee2b2c630198439352c170fc44c4b2025"
+      "sha256": "8a8df7e2a025029ffe7e18b7c7b18c6bd92a256822609931f0cd88628e446041"
     },
     {
       "path": "tests/wandering_prefs.mjs",

package/.claude/skills/builder-end/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: builder-end
 description: >-
-  Close out this session: resolve the active claim, confirm the tree is clean, tear down the worktree, and on a dev box offer to shut it down. Own-scoped; /builder-exit offboards a whole builder. Triggers: "/builder-end", "end my session", "sign off", "wrap up and clean up".
+  Close out this session: resolve the active claim, confirm the tree is clean, and tear down the worktree. Own-scoped; /builder-exit offboards a whole builder. Triggers: "/builder-end", "end my session", "sign off", "wrap up and clean up".
 ---
 
 You are closing out the current Claude Code **session** safely: resolve the held claim, confirm no work is stranded uncommitted, and clean up the session's git worktree. It is the bookend to `/builder-start` — one command so a session ends in a known-clean state instead of leaving a half-shipped claim and an orphaned worktree behind.
@@ -15,9 +15,8 @@ Composes operations that already exist, in a safe order, with the destructive on
 1. **Resolve the claim** — `/builder-ship` when there's committed, shippable work; `/builder-release` when there isn't. (It calls the sibling skills; it does not re-implement shipping.)
 2. **Clean-git verify** — refuse to go further if any *tracked* file is uncommitted. This is the same guard `scripts/gds/ship.js` enforces (`trackedDirty` in [`src/bongos/ship-preflight.js`](../../../src/bongos/ship-preflight.js)): untracked scratch is ignored, but a modified/staged/deleted tracked file means real work isn't committed — stop before anything is lost.
 3. **Worktree teardown** — from the main checkout, remove this session's linked worktree via `node scripts/gds/worktree.js remove` (junction-aware), `prune`, and delete the now-merged `claude/<name>` branch.
-4. **Box close-out (dev box only)** — if running on a dev box (`/etc/otb/box.env` exists), offer to `close-box` so the box stops billing. Optional and gated on a yes; declining just lets the box idle-park. On a laptop this step is skipped — there's no box to close.
 
-It never pushes to `main`, never `ssh`-es, never runs a deploy — landing is `/builder-ship`'s job (server-mediated). It only ever touches the caller's **own** claim, **own** worktree, and **own** box.
+It never pushes to `main`, never `ssh`-es, never runs a deploy — landing is `/builder-ship`'s job (server-mediated). It only ever touches the caller's **own** claim and **own** worktree.
 
 ## How to use
 
@@ -25,7 +24,6 @@ It never pushes to `main`, never `ssh`-es, never runs a deploy — landing is `/
 
 - **Held claim(s):** `node scripts/gds/api.js GET /api/gds/me` → `active_claims`. (A builder can hold parallel claims across sessions; resolve only the one this session worked.)
 - **Are we in a linked worktree?** `git rev-parse --git-dir` differs from `git rev-parse --git-common-dir` ⇒ yes (`--git-dir` is the per-worktree `<main>/.git/worktrees/<name>`; `--git-common-dir` is the shared `<main>/.git`); they're equal ⇒ main checkout (skip step 3). Test `--git-dir`, **not** `--git-common-dir` — the latter always returns the shared `<main>/.git` even inside a worktree, so checking *it* for `/worktrees/` never matches.
-- **Are we on a dev box?** `/etc/otb/box.env` exists ⇒ yes. This is the codebase's canonical "am I on a box?" marker — written by `box.js provision`, the same presence-check `scripts/gds/sandbox-stage.js` (`isDevBox`) uses. On a box the close-out has an extra step: the box keeps billing until it's shut down or idle-parks (step 4). On a laptop there's no box — skip step 4.
 - **Working-tree state:** `git status --porcelain`.
 - **Commits ahead of main:** `git rev-list --count main..HEAD` (fall back to `origin/main..HEAD`). Real commits ⇒ likely shippable; zero ⇒ likely a release.
 
@@ -34,7 +32,7 @@ It never pushes to `main`, never `ssh`-es, never runs a deploy — landing is `/
 - **Commits ahead AND clean tree ⇒ shippable.** Confirm with the user, then run the **`builder-ship`** skill with honest handoff `--notes` and a one-line non-jargon `--summary`. Don't fabricate the summary — if you can't state the value plainly, it isn't shippable; release instead.
 - **No commits / no shippable progress ⇒** run the **`builder-release`** skill with a one-phrase reason.
 - **No active claim ⇒** nothing to resolve; go to step 2.
-- **Ship strands at `confirmed`** (merge conflict or a failing check — the box ships, the merge doesn't): **stop here.** The branch still needs to land via `/merge-mode`. Surface that and do NOT tear down the worktree — its branch isn't merged yet (step 3's `git branch -d` would correctly refuse it).
+- **Ship strands at `confirmed`** (merge conflict or a failing check — the ship lands, the merge doesn't): **stop here.** The branch still needs to land via `/merge-mode`. Surface that and do NOT tear down the worktree — its branch isn't merged yet (step 3's `git branch -d` would correctly refuse it).
 
 ### 2. Clean-git verify
 
@@ -52,31 +50,19 @@ git worktree prune
 git branch -d claude/<worktree-name>        # -d (not -D): git refuses an unmerged branch, by design
 ```
 
-Removing this session's worktree ends its filesystem — do it last, and tell the user the session is closed and they can start fresh from `/builder-start` anytime. **On a dev box, settle step 4 first:** if the builder is going to `close-box`, skip teardown entirely — deprovisioning destroys the whole `/workspace` disk, so removing one worktree first is wasted effort. Only tear the worktree down if they're keeping the box.
+Removing this session's worktree ends its filesystem — do it last, and tell the user the session is closed and they can start fresh from `/builder-start` anytime.
 
-**On the main checkout (not a worktree):** skip the teardown above — there's nothing to remove. On a **laptop** that means resolving the claim + clean-git verify is the whole close-out. On a **dev box** (step 0 found `/etc/otb/box.env`) the box itself is still up — continue to step 4.
-
-### 4. Box close-out — dev box only, gated, after the claim is resolved
-
-Skip this entirely if step 0 found no `/etc/otb/box.env` (a laptop — there's no box to close). On a box, resolving the claim does **not** stop the box billing; only closing it (or the idle-suspend sweep) does. Once the claim is resolved and the tree is clean, ask plainly:
-
-> *"Close the box down too? `close-box` deprovisions it — anything in `/workspace` you haven't shipped is gone. Or leave it: closing the tab keeps your session, and the box idle-parks on its own (cheap)."*
-
-- **Yes, shut it down** → run the **`close-box`** skill (`node scripts/gds/api.js POST /api/gds/box/close`). It enqueues a deprovision that runs within ~a minute. This **subsumes** worktree teardown — the whole box disk is going away, so step 3 was moot.
-- **No, keep the box** → leave it; it idle-parks automatically. The close-out is complete (claim resolved, worktree torn down in step 3 if applicable). Tell them they can reopen the terminal to resume, or `/builder-box` to check/wake it later.
-
-`close-box` is **own-scoped** — it only ever deprovisions the caller's own box. Never another builder's.
+**On the main checkout (not a worktree):** skip the teardown above — there's nothing to remove. Resolving the claim + the clean-git verify is then the whole close-out.
 
 ## Constraints
 
-- **Own-scoped.** Only this session's claim, this session's worktree, and the caller's own box — never another builder's claim, never another worktree, never `git worktree remove` a path you didn't create, never another builder's box.
+- **Own-scoped.** Only this session's claim and this session's worktree — never another builder's claim, never another worktree, never `git worktree remove` a path you didn't create.
 - **Never destroy uncommitted work.** The clean-git verify gates teardown; the dirty-tree refusal in `git worktree remove` and `git branch -d` (not `-D`) are the load-bearing safety nets — keep them as written. But note: that refusal does NOT protect a Windows worktree carrying a `node_modules` junction — node_modules is gitignored, so the clean check passes and `git worktree remove` (even without `--force`) follows the junction and deletes the SHARED node_modules (task 1002809). That is why teardown runs through `node scripts/gds/worktree.js remove`, which unlinks the junction first.
-- **Box close is opt-in and destructive.** On a box, never `close-box` without an explicit yes — it deprovisions the box and any unshipped `/workspace` work is gone. Declining is always fine; the box idle-parks on its own.
-- **Never push / ssh / deploy.** Landing goes through `/builder-ship` (server-mediated); this skill stays local to the builder's machine (its one possible API write is the opt-in own-scoped `close-box`).
-- **The destructive steps (teardown, box-close) never run unattended without a clear go.** Ship vs. release can be inferred from state (commits ⇒ ship, none ⇒ release) and proceed; removing the worktree ends the session and closing the box destroys it, so wait for an explicit yes before steps 3 and 4.
+- **Never push / ssh / deploy.** Landing goes through `/builder-ship` (server-mediated); this skill stays local to the builder's machine and makes no API writes of its own.
+- **Teardown never runs unattended without a clear go.** Ship vs. release can be inferred from state (commits ⇒ ship, none ⇒ release) and proceed; removing the worktree ends the session, so wait for an explicit yes before step 3.
 - **Don't tear down a branch that isn't merged.** A released task or a ship stuck at `confirmed` still has an un-landed `claude/*` branch — `git branch -d` will refuse it; respect that and leave the worktree for `/merge-mode`.
 
 ## Files this skill touches
 
-- Reads: `~/.config/otb/gds-session.json`; `/etc/otb/box.env` (presence check only — "am I on a box?")
-- Runs: the `builder-ship` / `builder-release` skills (`scripts/gds/ship.js` · `release.js`), `node scripts/gds/api.js GET /api/gds/me`, and local `git worktree` / `git status` / `git branch` commands. On a dev box, if the builder opts in, it runs the `close-box` skill (`POST /api/gds/box/close`) — the one own-scoped API write it can make; otherwise it makes no API writes of its own.
+- Reads: `~/.config/otb/gds-session.json`
+- Runs: the `builder-ship` / `builder-release` skills (`scripts/gds/ship.js` · `release.js`), `node scripts/gds/api.js GET /api/gds/me`, and local `git worktree` / `git status` / `git branch` commands. It makes no API writes of its own.

package/.claude/skills/builder-exit/SKILL.md

@@ -12,8 +12,8 @@ You are gracefully offboarding a builder from Bongos, or reactivating one who ha
 
 `/builder-exit` is **not** how you end a working session. It permanently **offboards an entire builder** — an Archon deactivating *someone else's* account (releases all their claims, drops them to Xenos, blocks new claims). "Exit" is the natural word for "log me off," so builders reach for this first ([#1448](https://example.com/builders#/task/1448)) — but it's the wrong, and gated, tool for the everyday close-out. Before touching anything, check intent:
 
-- **The caller wants to wrap up their *own* online-terminal / Claude Code session** — no builder id given, the id is their own, or they said "close out / end / sign off / I'm done" → **do not attempt an offboard.** Say plainly: *"`/builder-exit` offboards an entire builder (releases all their claims, drops them to Xenos) and is Archon-only — it isn't the session close-out. To close out your session, run **`/builder-end`**: it resolves your claim (ship or release) and, on a dev box, offers to shut the box down with `close-box`."* Then stop and hand off to `/builder-end`.
-- **The caller is not an Archon** (rank below `archon`, or you can't confirm Archon) → same redirect. The endpoint would 403 (`rank_forbidden`) anyway; don't dead-end them on the error — point them at `/builder-end` (+ `close-box` on a box).
+- **The caller wants to wrap up their *own* online-terminal / Claude Code session** — no builder id given, the id is their own, or they said "close out / end / sign off / I'm done" → **do not attempt an offboard.** Say plainly: *"`/builder-exit` offboards an entire builder (releases all their claims, drops them to Xenos) and is Archon-only — it isn't the session close-out. To close out your session, run **`/builder-end`**: it resolves your claim (ship or release) and tears down the session's worktree."* Then stop and hand off to `/builder-end`.
+- **The caller is not an Archon** (rank below `archon`, or you can't confirm Archon) → same redirect. The endpoint would 403 (`rank_forbidden`) anyway; don't dead-end them on the error — point them at `/builder-end`.
 - **An Archon is deliberately offboarding (or reactivating) *another* builder, by id** → this is the real operation. Proceed with the steps below.
 
 Never run the destructive offboard just because someone wanted to log off — the two are different operations.

package/.claude/skills/builder-ship/SKILL.md

@@ -25,15 +25,15 @@ The CLI drives a **three-state lifecycle** with a subagent grader between states
 - **`GRADER UNAVAILABLE`** (`panel_outcome='unavailable'`) — the grading panel could not run (worker infra outage or a pre-spawn bypass). This is **not a quality rejection**: no quality signal was produced, there are no findings to fix, and the task parks at `completed` ungraded (aggregates exclude these rounds as `n_unavailable` — an outage never counts as a zero). Recovery: when the grader is reachable again, re-run just the grade step — `node scripts/gds/ship.js <id> --regrade`.
 - **A genuine `FAIL`** — the panel ran and returned findings. Fix the real issues, commit on the claim branch (the grader reads committed history, not the working tree), then re-grade with the same command: `node scripts/gds/ship.js <id> --regrade`.
 
-(Dev-box game changes, `--approved`) Persists the builder's sandbox self-approval to `tasks.sandbox_review` — `{ by, at, stamp, url, method }`, with `by`/`at` stamped server-side ([#1048](https://example.com/builders#/task/1048), ADR 0046).
+(Game-surface changes, `--approved`) Persists the builder's sandbox self-approval to `tasks.sandbox_review` — `{ by, at, stamp, url, method }`, with `by`/`at` stamped server-side ([#1048](https://example.com/builders#/task/1048), ADR 0046).
 
 ## How to use
 
 1. **Confirm the task id** the user is shipping (it must match their currently-active claim).
 
-   **On a dev box with game-surface changes, stage first (#927, ADR 0046 + #1048).** If the diff touches the game (`public/`, `src/world/`, `src/rooms/`, `server.js`) and the session is on a dev box, the flow is: stage → the builder reviews the change at `https://sandbox-<login>.example.com` → approve → ship. `ship.js` enforces this before the claim resolves: un-staged game work gets staged to the sandbox and the ship **aborts with a `🔍 REVIEW REQUIRED` block** carrying the URL (claim intact, nothing lost).
+   **With game-surface changes, stage first (#927, ADR 0046 + #1048).** If the diff touches the game (`public/`, `src/world/`, `src/rooms/`, `server.js`), the flow is: stage → the builder reviews the change on their local sandbox preview → approve → ship. `ship.js` enforces this before the claim resolves: un-staged game work gets staged and the ship **aborts with a `🔍 REVIEW REQUIRED` block** carrying the URL (claim intact, nothing lost).
 
-   **When you see that block, position the sandbox link prominently for the builder.** `ship.js` also emits the deterministic lifecycle card for the `review` stage (an `[otb-card-html] <path>` marker) — if an in-feed visualization tool is available, render that card (its primary action is **Open in sandbox ↗**, the URL); it's the cleanest way to make the link impossible to miss. Either way, surface the URL as its own standalone, clickable line in chat — a clear callout, NOT buried inside a paragraph of command output — and say in one line what to look at. This is the moment the change is ready to review; the link must be impossible to miss. Let the builder open it, review, and suggest changes; iterate if needed. **Only once the builder explicitly approves, re-run with `node scripts/gds/ship.js <id> --approved`** — that records their sign-off as a durable `sandbox_review` fact on the task (who, when, and the content stamp of exactly what was reviewed). Never pass `--approved` yourself without a real human go; the pause + sign-off IS the feature. `--skip-stage` is the escape hatch (use sparingly — the gate exists so unreviewed game changes don't ride straight to prod). Laptop sessions and non-game diffs are unaffected.
+   **When you see that block, position the sandbox link prominently for the builder.** `ship.js` also emits the deterministic lifecycle card for the `review` stage (an `[otb-card-html] <path>` marker) — if an in-feed visualization tool is available, render that card (its primary action is **Open in sandbox ↗**, the URL); it's the cleanest way to make the link impossible to miss. Either way, surface the URL as its own standalone, clickable line in chat — a clear callout, NOT buried inside a paragraph of command output — and say in one line what to look at. This is the moment the change is ready to review; the link must be impossible to miss. Let the builder open it, review, and suggest changes; iterate if needed. **Only once the builder explicitly approves, re-run with `node scripts/gds/ship.js <id> --approved`** — that records their sign-off as a durable `sandbox_review` fact on the task (who, when, and the content stamp of exactly what was reviewed). Never pass `--approved` yourself without a real human go; the pause + sign-off IS the feature. `--skip-stage` is the escape hatch (use sparingly — the gate exists so unreviewed game changes don't ride straight to prod). Non-game diffs are unaffected.
 
 2. **Compose the handoff notes (`--notes-file`)** following the structure in `docs/handoff-template.md`:
    - What shipped (with confidence tags: verified-prod | verified-smoke | implemented-not-verified)

package/.claude/skills/builder-stage/SKILL.md

@@ -4,28 +4,24 @@ description: >-
   Stage the working tree on the builder's own live preview to see a change in a browser BEFORE shipping. Own-scoped and machine-local. Triggers: "/builder-stage", "stage my work", "let me see it before shipping", "preview this change".
 ---
 
-You are staging a builder's in-progress work on **their own** sandbox — the live game preview running on their dev box (ADR 0044) — so they can see the change in a browser, suggest fixes, and only then decide to ship it to the main game (ADR 0046).
+You are staging a builder's in-progress work on **their own** sandbox — the live game preview running on their own machine — so they can see the change in a browser, suggest fixes, and only then decide to ship it to the main game (ADR 0046).
 
 ## Background
 
-The script auto-detects where it's running and (re)starts the right preview — both serve the **game-only** entry (`src/preview-server.js`, ADR 0052), degraded-DB (fully playable, no saved state, isolated from prod, no `/api/gds`):
-
-- **Dev box:** `box-game-preview.service` serves the `/workspace` tree at `https://sandbox-<login>.example.com` (ADR 0044). Staging restarts that service.
-- **Local full clone (laptop):** a private detached process serves it at `http://localhost:<port>` (default 3100, `$OTB_PREVIEW_PORT` to override), managed by `scripts/gds/local-preview.js` (task 1056). Staging (re)starts that process. No tunnel, no public URL — it never leaves your machine.
-
-Either way staging = (re)start the preview, health-check it, and record a marker of exactly what tree state was staged. `/builder-ship` checks that marker: a game-surface diff that wasn't staged at its current state triggers the sandbox review gate before the claim resolves — on a box AND on a local clone.
+Staging (re)starts the preview, which serves the **game-only** entry (`src/preview-server.js`, ADR 0052), degraded-DB (fully playable, no saved state, isolated from prod, no `/api/gds`): a private detached process at `http://localhost:<port>` (default 3100, `$OTB_PREVIEW_PORT` to override), managed by `scripts/gds/local-preview.js` (task 1056). No tunnel, no public URL — it never leaves your machine.
+Staging = (re)start the preview, health-check it, and record a marker of exactly what tree state was staged. `/builder-ship` checks that marker: a game-surface diff that wasn't staged at its current state triggers the sandbox review gate before the claim resolves.
 
 ## How to use
 
-1. **Run the stage command** from the repo root (`/workspace` on a box; your clone root on a laptop):
+1. **Run the stage command** from your clone root:
    ```bash
    node scripts/gds/sandbox-stage.js
    ```
-   It (re)starts the preview, waits until the game answers, writes the staged marker, and prints the review URL (the `sandbox-<login>` host on a box, or `http://localhost:<port>` locally).
+   It (re)starts the preview, waits until the game answers, writes the staged marker, and prints the review URL (`http://localhost:<port>`).
 
-   > **Local setup (laptop):** the preview needs the game's dependencies, so run `npm install` once in your clone. You can also drive the preview directly: `npm run preview` (start), `node scripts/gds/local-preview.js {status|restart|stop|logs}`. Reviewing via the Claude Code preview tools? A `local-sandbox` server is pre-wired in `.claude/launch.json`.
+   > **First-time setup:** the preview needs the game's dependencies, so run `npm install` once in your clone. You can also drive the preview directly: `npm run preview` (start), `node scripts/gds/local-preview.js {status|restart|stop|logs}`. Reviewing via the Claude Code preview tools? A `local-sandbox` server is pre-wired in `.claude/launch.json`.
 
-2. **Hand the builder the URL** and tell them plainly: this is *their* private copy of the game running on *their* box — nothing has shipped. Ask them to open it, walk around, and check the change.
+2. **Hand the builder the URL** and tell them plainly: this is *their* private copy of the game running on *their own machine* — nothing has shipped. Ask them to open it, walk around, and check the change.
 
    > **Generated art?** If the change was a pixel-art tile, the builder can also see it at the **`/art`** path of the same sandbox URL (`…/art`) — the generated-art gallery (#1262), which shows every tile they've made *even when it isn't placed in the game world yet*. Point them there when the work is "I made a tile" rather than "I changed the map."
 
@@ -39,14 +35,12 @@ Either way staging = (re)start the preview, health-check it, and record a marker
 
 ## Constraints
 
-- **Box or local full clone.** A dev box stages to `sandbox-<login>`; a full local clone stages to `http://localhost:<port>`. The ONLY machine with no sandbox is a partial clone that lacks the game (`src/preview-server.js`) — there the script says so and exits.
-- **Named tunnel required (box only).** A quick-tunnel box has no sandbox hostname (ADR 0044); the script says so. The fix is operator-side (`BOX_NAMED_TUNNEL=1` + re-provision), not something to debug here. (Local previews have no tunnel and aren't affected.)
-- **On a dev box, the preview is the HOSTED `sandbox-<login>` URL — never localhost.** Get it from this skill (`node scripts/gds/sandbox-stage.js`) or `box-preview status`. Do **NOT** preview a box change with the Claude Code preview tools or `npm run preview`/`npm start`: those bind `http://localhost`, which the builder's own browser can't reach when the server is on a remote box — handing them a dead localhost link is the task-1443 footgun. (`sandbox-stage.js` now routes any box to the hosted URL and refuses to emit localhost; a box with no hostname gets a clear re-provision message, not a localhost link.) Localhost is correct ONLY on a laptop full clone.
-- **Never present the sandbox as prod.** No credits, no broadcast, nothing shipped — staging is review, `/builder-ship` is the decision. The local preview is private to the builder's own machine (not shareable).
-- If the preview won't come up healthy, point the builder at the logs — `box-preview logs` on a box, `node scripts/gds/local-preview.js logs` locally — rather than guessing.
+- **A full local clone.** The ONLY machine with no sandbox is a partial clone that lacks the game (`src/preview-server.js`) — there the script says so and exits.
+- **Never present the sandbox as prod.** No credits, no broadcast, nothing shipped — staging is review, `/builder-ship` is the decision. The preview is private to the builder's own machine (not shareable).
+- If the preview won't come up healthy, point the builder at the logs — `node scripts/gds/local-preview.js logs` — rather than guessing.
 
 ## Files this skill touches
 
-- Runs: `scripts/gds/sandbox-stage.js` (resolves box vs local; box → restarts `box-game-preview.service`; local → `scripts/gds/local-preview.js` + `local-preview-lib.js` (re)start `node src/preview-server.js`)
-- Reads: `/etc/otb/box.env` (a box's `BOX_PREVIEW_HOSTNAME`); `$OTB_PREVIEW_PORT` (local port, default 3100)
+- Runs: `scripts/gds/sandbox-stage.js`, which drives `scripts/gds/local-preview.js` + `local-preview-lib.js` to (re)start `node src/preview-server.js`
+- Reads: `$OTB_PREVIEW_PORT` (local port, default 3100)
 - Writes: the staged marker in the OS temp dir (`otb-sandbox-staged.json`); locally, the preview pid/log in the OS temp dir (`otb-local-preview.{pid,log}`)

package/.claude/skills/merge-mode/SKILL.md

@@ -29,10 +29,10 @@ If it exits non-zero, **stop**: this machine cannot finish the procedure, and th
 partial run is the dangerous outcome (it mutates the main worktree). The skill's
 `requires:` frontmatter is what it checks — `main-checkout`, `push-credential`,
 `gh`, `droplet-ssh`. This gate exists because the note below was prose only, and
-prose cannot refuse: merge-mode was run on a dev box that had none of them, while
-`ship.js` separately already knew (`strandNextStep` tells a box "/merge-mode is
-NOT available here"). The knowledge existed twice and neither copy stopped the run
-(task 1003167).
+prose cannot refuse: merge-mode was run on a machine that had none of them, while
+`ship.js` separately already knew (`strandNextStep` tells such a machine
+"/merge-mode is NOT available here"). The knowledge existed twice and neither copy
+stopped the run (task 1003167).
 
 > **Environment note:** merge-mode is an **ops procedure** — it mutates the single
 > main worktree and deploys to the Linux droplet (owner-gated SSH). The git /
@@ -120,7 +120,7 @@ This mirrors what `ship.js` does automatically; it's here because /merge-mode de
 
 > **Deploy mode (#679 / [ADR 0042](../../../docs/adr/0042-builder-self-deploy-ci-auto-merge.md)).** `config/deploy.json` is now `mode: ci` (CI cutover landed 2026-06-13), so the **`ci`** path is current: there is no laptop merge and no SSH at all — landing happens via PR auto-merge and [`.github/workflows/deploy-prod.yml`](../../../.github/workflows/deploy-prod.yml) deploys `main`→prod from Actions. In `ci` mode, do NOT run the `git push origin main` + `ssh … ~/deploy.sh` lines below — instead confirm the PR auto-merged and the `deploy-prod` Actions run went green. The block below is the **legacy `laptop`** deploy mode (the operator's machine pushes `main` and SSHes the droplet) — it is the fallback path and only applies if `config/deploy.json` is reverted to `mode: laptop`. Check the active mode with `node scripts/gds/ship.js --print-deploy-mode`.
 
-> **Do NOT probe `parseDeployMode` directly (task 1003221).** It reads only the env var and `config/deploy.json`, and **defaults to `laptop`** when neither is present — and `config/` is not in the dev-box sparse checkout (`BASE_SPARSE_PATHS`, ADR 0148), so on a box that probe answers `laptop` every time. It sent a builder down the laptop merge path — local merge, `push-main.js`, SSH deploy — on a machine with none of those credentials (2026-08-21, 163 minutes). `effectiveDeployMode` is the credential-aware answer and reroutes to `ci` when the machine cannot push locally; the flag above prints that one.
+> **Do NOT probe `parseDeployMode` directly (task 1003221).** It reads only the env var and `config/deploy.json`, and **defaults to `laptop`** when neither is present — so on any machine whose checkout does not carry `config/`, that probe answers `laptop` every time. It sent a builder down the laptop merge path — local merge, `push-main.js`, SSH deploy — on a machine with none of those credentials (2026-08-21, 163 minutes). `effectiveDeployMode` is the credential-aware answer and reroutes to `ci` when the machine cannot push locally; the flag above prints that one.
 
 ```bash
 node scripts/gds/smoke-gds.js    # 16/16 expected (cross-platform; replaces smoke-gds.sh)

package/docs/adr/0171-profile-rollup-join-and-consent.md

@@ -25,6 +25,8 @@ Five facts found during this spike shape the decisions:
 
 **2. One safe read path, enforced next to the data.** The port exposes `getPublicProfileExtras(githubId)`: `null` unless the account exists, is publicly addressable (Decision 3), and `hide_stats` is false — otherwise `{ totals: { projects, credits, works_shipped, karma }, disciplines, last_active, projects: [{ name, origin, rank_held }...], more_projects }`, whitelist-shaped **inside the module** (`client_id` and raw rows never cross the port; non-numeric `github_id` values like the `system:*` principals return `null` instead of hitting a bigint cast error). Every surface that shows cross-project numbers reads through the module's filtered functions at render time, never from a stored copy — and that includes the two that already exist: **`listScoutingRollup` itself gains the `profile_state = 'active' AND NOT hide_stats` predicate and a whitelisted projection**, so `/people` and `/scouting` (live today at Metic floor) honor hide by construction, not by memory. The hub hall profile, the `/u/<handle>` page, recruiting (R14/R15) and applications (R09) all sit on the same functions, which is what makes C2's "honored live everywhere, including pending applications" structural. Two deliberate side doors, both narrow: `getOwnProfileExtras(githubId)` serves the builder their own numbers regardless of flags (Settings), and spike 1002785's recruiter flow is expected to add a second **authorization-scoped** read for its opt-in discoverability sliver — `hide_stats` is the invariant every reader honors; public addressability is not.
 
+> **D2 amendment — which projects a profile may NAME (owner, 2026-09-16, task 1003558).** Until then a project was named only when `featured AND status = 'active'`, a predicate the public map dropped in R06 (ADR 0182 D3). It is now **on the map AND Public**: `onMapSql('p') AND p.visibility = 'public'`, where `onMapSql` is the feed's own fragment, so a profile and the map cannot disagree about who is on the map. `featured` gates no name. **Private is deliberately NOT named**, though its name is on the map: naming it on a profile publishes who works there, at what rank and on which works, which the map never says. Stealth stays unnamed (ADR 0182 D2a). Everything unnamed is counted in `more_projects`, and `recent_ships` follow the name.
+
 **3. Consent is a fail-closed `profile_state` on `platform_identity_accounts`, with one discriminator.** Migration `platform_identity_007_profile_consent.sql` (lands with R02) adds `profile_state text NOT NULL DEFAULT 'provisional' CHECK (profile_state IN ('provisional','active'))` and `hide_stats boolean NOT NULL DEFAULT false`. The single rule: **an account is `active` iff it was touched by a hub-session `/sso/authorize`** — the one path where a human is demonstrably at the hub (and where T&C acceptance can later be captured, task 1002913). Device-poll and check-in create `provisional`; the rollup endpoint creates nothing (orphan activity rows are never publicly addressable). Backfill: **all existing accounts start `provisional`** and lazily upgrade on their next hub-session authorize — no join to core `builders` (that join is type-unsafe against `system:*` text ids and would put a core-table read inside a module migration; the price is that existing hub builders' profiles publish on their next sign-in rather than immediately). Public surfaces read only `active` accounts. **R02 ships this fail-closed default without waiting on P03**, because the asymmetry only runs one way: P03 can then only ever *widen* exposure, never claw back something already published. This deliberately narrows the Phase-4 interview's "no extra consent gate" to the accounts whose consent premise actually holds; P03 is the owner either ratifying that boundary (recommended) or reverting to the interview decision verbatim — and the revert branch has a named precondition: check-in/device-created identities have **no self-serve hide path** (no hub builder session exists for them; hub admission is invite-gated), so rejecting P03 first requires an assertion-authenticated hide path or open hub enrollment. Task 1002799 carries this full decision payload.
 
 > **P03 outcome — RATIFIED (owner, 2026-08-16, task 1002799).** The fail-closed boundary stands: check-in/device-created accounts stay `provisional` (not publicly listed, not at `/u/<handle>`, not in the sitemap or hub search) until their human signs in at the hub at least once. The owner's rationale: in the intended product flow a builder passes through cloudbongos.com at least once anyway — to find or create the projects they join — so the activation gate is satisfied naturally and costs nothing; the cloudbongos builders hall predating the hub flow is a one-time bootstrap exception, and those accounts lazily activate on their next hub sign-in exactly as the backfill rule above already provides (no backfill activation). Tasks 1002913 (T&C artifact) and 1002914 (criterion text amendments) unblock on this ship.

package/docs/adr/0182-project-visibility-two-axes.md

@@ -169,7 +169,7 @@ The last sentence of this decision is therefore now spent — `stealth` unqualif
 - Anything reading `featured = true AND status = 'active'` as "is this public" is now wrong and must be found. `modules/platform-identity/routes/projects.js` is the known site.
 - **R16 makes D3's bound real, and D4's gate reach a second module.** Shipping R16 (task 1002335) surfaced one thing this ADR left implicit. D3 says `featured` may never put an unpublishable project on the map, so `PATCH /projects/:id/featured` now refuses a dark-matter row (409 `not_publishable`, `missing` in the details); un-featuring stays unconditional, since an already-featured husk must remain removable. And D4's "name what is missing" is owed to the owner *before* their project is ever catalogued on the hub — which is the `provisioning` plane, a different module that ADR 0083 forbids from importing `platform-identity`. Rather than let a two-field rule exist twice, the gate is published as a kernel seam port, `project.publishGate` (`modules/platform-identity/publish-gate.js`). `provisioning` resolves it **optionally** and declares no `consumes`: `platform-identity` is hub-only, the public map is a hub concept, and a platform without one must answer "no verdict" rather than invent a local rule — which is the same drift-avoidance argument that produced `publishableSql` in the first place.
 
-- **R06 landed the predicate swap and the redaction, and settled three things this ADR left to the implementer** (task 1002325, `modules/platform-identity/projects-feed.js`). (a) **A black hole carries no stable per-project key.** D2a lists `name`/`tagline`/`art_url`/`origin`, and an id looks harmless beside them — but any identifier that survives a state change lets an observer who kept yesterday's public feed diff it against today's and *name* the project that went stealth. So stealth rows are byte-identical to one another and the feed grew no public id at all; the orbs page keys by position. (b) **The redaction is an ALLOW-list, not a deny-list** — every key nulled except `state` and `orb` — so a column added to the feed later is anonymous without anyone remembering to come back to it, and it NULLS rather than deletes, keeping the feed's "never drop a key" contract. (c) **An unrecognised `visibility` draws as a black hole, not a planet**: this mapping is a privacy boundary, so a fourth enum value added without mapping it must fail closed. Two smaller notes: the route PATH keeps the word `featured` (it is rank:public and CORS-open, already fetched by a static site and other origins — renaming it would break them for nothing, and `ORDER BY featured DESC` is where the flag's D3 ranking job now lives); and `getRollupForBuilder`'s `is_public` was deliberately left on the OLD `featured AND active` predicate rather than widened with the feed, because a stealth project is on the map *anonymously* and naming it in a builder's profile would be the exact leak D2a forbids — how much of a cross-project record may be NAMED is ADR 0171 D2's question, and under-naming is the safe direction meanwhile.
+- **R06 landed the predicate swap and the redaction, and settled three things this ADR left to the implementer** (task 1002325, `modules/platform-identity/projects-feed.js`). (a) **A black hole carries no stable per-project key.** D2a lists `name`/`tagline`/`art_url`/`origin`, and an id looks harmless beside them — but any identifier that survives a state change lets an observer who kept yesterday's public feed diff it against today's and *name* the project that went stealth. So stealth rows are byte-identical to one another and the feed grew no public id at all; the orbs page keys by position. (b) **The redaction is an ALLOW-list, not a deny-list** — every key nulled except `state` and `orb` — so a column added to the feed later is anonymous without anyone remembering to come back to it, and it NULLS rather than deletes, keeping the feed's "never drop a key" contract. (c) **An unrecognised `visibility` draws as a black hole, not a planet**: this mapping is a privacy boundary, so a fourth enum value added without mapping it must fail closed. Two smaller notes: the route PATH keeps the word `featured` (it is rank:public and CORS-open, already fetched by a static site and other origins — renaming it would break them for nothing, and `ORDER BY featured DESC` is where the flag's D3 ranking job now lives); and `getRollupForBuilder`'s `is_public` was deliberately left on the OLD `featured AND active` predicate rather than widened with the feed, because a stealth project is on the map *anonymously* and naming it in a builder's profile would be the exact leak D2a forbids — how much of a cross-project record may be NAMED is ADR 0171 D2's question, and under-naming is the safe direction meanwhile. (Widened by task 1003558 to on-the-map AND Public; see the ADR 0171 D2 amendment.)
 
 ## Alternatives rejected
 

package/docs/file-map.md

@@ -393,11 +393,9 @@ tests/
 ├── blocker-solve/SKILL.md         ← /blocker-solve N — drive ONE blocker to done: do the doable parts, hand back owner-only steps, verify, auto-resolve (auto-promotes waiters); Metic+
 ├── bug-triage/SKILL.md            ← /bug-triage — daily walk through open kind=bug tasks (batch-cluster near-dups, merge / won't-fix); the idea-triage counterpart built on the new tasks.merge primitive (task 1001478); Metic+
 ├── builder-backup/SKILL.md        ← /builder-backup — check DB backup status or trigger a fresh local dump before risky changes (migrations, destructive SQL); no SSH required
-├── builder-box/SKILL.md           ← /builder-box — show the builder their own dev box (state, IP/host, cost, SSH keys) and help them (re)connect
 ├── builder-claim/SKILL.md         ← /builder-claim N — atomic claim; prints the claim-time context pack + discipline playbook routing
-├── builder-connect/SKILL.md       ← /builder-connect — one-command connect of the builder's Claude Desktop to their Example dev box (ADR 0031)
 ├── builder-cost/SKILL.md          ← /builder-cost — log a cost-ledger entry (api|compute|infra|domain|art|other)
-├── builder-end/SKILL.md           ← /builder-end — safely close out a session: resolve the claim (ship/release) + clean-git verify + worktree teardown + (on a dev box) offer to close the box; the bookend to /builder-start, and the own-scoped session close-out that /builder-exit redirects non-Archons to
+├── builder-end/SKILL.md           ← /builder-end — safely close out a session: resolve the claim (ship/release) + clean-git verify + worktree teardown; the bookend to /builder-start, and the own-scoped session close-out that /builder-exit redirects non-Archons to
 ├── builder-exit/SKILL.md          ← /builder-exit — gracefully offboard (or reactivate) a builder: release claims, seal session logs, drop rank to xenos
 ├── builder-key/SKILL.md           ← /builder-key — list API-key status, render the visual 'key needed' callout for anything missing, drive the UI-first Settings add-flow + re-sync/confirm; never accepts a key pasted in chat (task 1391)
 ├── builder-reauth/SKILL.md        ← /builder-reauth — refresh an expired Bongos CLI session the UI-first way (no terminal Device Flow)
@@ -405,11 +403,9 @@ tests/
 ├── builder-release/SKILL.md       ← /builder-release — abandon a claim (task returns to ready, no credits)
 ├── builder-sequence/SKILL.md      ← /builder-sequence N — walk a whole dependency chain from one kickoff (claim → build → ship → next), one claim at a time; halts and reports on migration/security/protected-path/thin-spec/judgement tasks (scripts/gds/sequence.js, task 1002484)
 ├── builder-setup/SKILL.md         ← /builder-setup — one-time GitHub Device Flow auth (Bongos); multi-builder-on-one-device gate
-├── builder-ship/SKILL.md          ← /builder-ship — record + award credits (runs touches[] scanner; warns on drift; sandbox-first review gate on dev boxes, ADR 0046)
-├── builder-stage/SKILL.md         ← /builder-stage — stage work on the builder's sandbox (sandbox-<login>) for browser review before shipping (#927, ADR 0046)
+├── builder-ship/SKILL.md          ← /builder-ship — record + award credits (runs touches[] scanner; warns on drift; sandbox-first review gate for game-surface changes, ADR 0046)
+├── builder-stage/SKILL.md         ← /builder-stage — stage work on the builder's own local sandbox preview (http://localhost:<port>) for browser review before shipping (#927, ADR 0046)
 ├── builder-start/SKILL.md         ← /builder-start — list claimable tasks (parallel-safe vs active claims)
-├── builder-sync/SKILL.md          ← /builder-sync — 'sync now': re-run the box source-fetch on demand so a freshly-claimed task's code lands within seconds, re-scoped to the active claim (BV1.R96, ADR 0148)
-├── close-box/SKILL.md             ← /close-box — tear down the dev box you're working on, from inside the box terminal (POST /box/close)
 ├── design/SKILL.md                ← /design — the UI design session: the operating playbook for ui-discipline work on ANY instance (load the instance's pack + DESIGN.md first, look before you ship, build inside the platform floors, ship the tests with the UI); routed from a `ui` claim via discipline-modes.json; shipped by the ui-design module (task 1003324, ADR 0197)
 ├── design-sync/SKILL.md           ← /design-sync — export repo design tokens + surfaces into Claude Design (token-preview bundle) and land generated UI code back as a Bongos task (ADR 0081)
 ├── feedback/SKILL.md              ← /feedback — pull the latest Bongos feedback bundle (prompt.md + screenshot file paths) into a Claude Code session; backed by scripts/gds/feedback-latest.js (BV1.R13, ADR 0087)

package/docs/module-api-changelog.md

@@ -2028,5 +2028,9 @@ is load-bearing: the script throws rather than guess if it is missing, and
         landed since 1.19.775 with no explicit bump. run 35135604764. (task 1002620)
   1.19.777 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
         landed since 1.19.776 with no explicit bump. run 35137334438. (task 1002620)
+  1.19.778 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.19.777 with no explicit bump. run 35139523999. (task 1002620)
+  1.19.779 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.19.778 with no explicit bump. run 35144678111. (task 1002620)
 ---------------------------------------------------------------------------
 ```

package/docs/onboarding/slash-commands.md

@@ -42,8 +42,6 @@ Every one of these talks to the build system. They're grouped by when you'd reac
 | `/builder-setup` | One-time enrolment — signs you in and registers you |
 | `/builder-reauth` | Refresh an expired session |
 | `/builder-key` | Check / set your own API key status |
-| `/builder-box` | Your dev box control panel — wake, create, check cost |
-| `/builder-connect` · `/builder-sync` · `/close-box` | Connect to, re-sync, and tear down that box |
 | `/builder-cost` | Log a cost entry against your claim |
 | `/builder-backup` | Check or trigger a database backup before risky work |
 | `/builder-exit` | Offboard or reactivate a builder *(Archon only)* |

package/modules/platform-identity/platform-identity.js

@@ -322,7 +322,7 @@ const {
 // D1/D2a/D3; R06, task 1002325). Its own file for the publish-gate.js reason: this
 // file is at the size ratchet. Re-exported below, so the surface is unchanged.
 const {
-  ORB_BY_STATE, orbForState, isStealthProject, feedShapeFor, listPublicProjects, PUBLIC_FEED_MAX_PAGE_SIZE,
+  ORB_BY_STATE, orbForState, isStealthProject, feedShapeFor, listPublicProjects, PUBLIC_FEED_MAX_PAGE_SIZE, onMapSql,
 } = require('./projects-feed');
 
 // Upsert a catalog row (keyed by origin). Called when a client registers (so every
@@ -753,17 +753,14 @@ function isNumericGithubId(githubId) {
 // listScoutingRollup's corrected shape: scalars over the UN-FANNED activity
 // table, the disciplines union computed separately (never a pre-GROUP-BY unnest
 // fan-out — bug task 1002911). Per-project rows join the module-internal
-// client_id → sso_clients.origin → projects.origin two-hop; a project is NAMED
-// only when its catalog row is publicly listed today (featured + active).
-// Everything else is counted in more_projects, never named ("the aggregate is
-// not the leak, the name is").
+// client_id → sso_clients.origin → projects.origin two-hop. Everything not
+// named is counted in more_projects ("the aggregate is not the leak, the name is").
 //
-// Deliberately NARROWER than the public feed since R06 (task 1002325), and left so
-// rather than widened here: a STEALTH project is on the map ANONYMOUSLY (ADR 0182
-// D2a), so naming it in a builder's profile would be the leak the feed exists to
-// prevent, and how much of a record may be NAMED is ADR 0171 D2's question, not
-// R06's. Narrower under-names, which is safe. The widening is its own task.
-// client_id never appears in the returned shape.
+// NAMED = on the map by the feed's own predicate (onMapSql) AND Public — the
+// owner's call on task 1003558 (ADR 0171 D2 amendment). A Private project is
+// named on the map but not here: who works there, their rank and their work
+// titles stay counted. Stealth is on the map anonymously (ADR 0182 D2a).
+// `featured` only ranks (D3), so it gates no name. client_id never crosses.
 async function getRollupForBuilder(githubId, { pool = defaultPool } = {}) {
   if (!isNumericGithubId(githubId)) return null;
   const { rows: aggRows } = await pool.query(
@@ -790,7 +787,7 @@ async function getRollupForBuilder(githubId, { pool = defaultPool } = {}) {
   const agg = aggRows[0];
   const { rows: projRows } = await pool.query(
     `SELECT p.name, p.origin, a.rank_held, a.recent_ships,
-            (p.id IS NOT NULL AND p.featured AND p.status = 'active') AS is_public
+            (p.id IS NOT NULL AND ${onMapSql('p')} AND p.visibility = 'public') AS is_public
        FROM platform_identity_builder_project_activity a
        LEFT JOIN platform_identity_sso_clients c ON c.client_id = a.client_id
        LEFT JOIN platform_identity_projects p ON p.origin = c.origin

package/modules/platform-identity/projects-feed.js

@@ -207,7 +207,20 @@ const PUBLIC_FEED_MAX_PAGE_SIZE = 500;
 // The same predicate written without the `visibility_source` half — or shipped without
 // migration 020's backfill, which stamps every pre-existing row 'control-plane' — would
 // empty the public map on deploy. Both halves are load-bearing.
-const DOOR_KNOWN_SQL = "(visibility_source = 'control-plane' OR visibility_reported_at IS NOT NULL)";
+function doorKnownSql(prefix = '') {
+  return `(${prefix}visibility_source = 'control-plane' OR ${prefix}visibility_reported_at IS NOT NULL)`;
+}
+const DOOR_KNOWN_SQL = doorKnownSql();
+
+// ON THE MAP, as one SQL fragment: active, publishable and door-known. The feed's WHERE
+// and a builder profile's naming rule (getRollupForBuilder, task 1003558) both read it,
+// so a profile can never name a project by a different idea of "on the map" than the map's.
+// publishableSql() refuses a non-identifier alias before this interpolates it too.
+function onMapSql(alias) {
+  const publishable = publishableSql(alias);
+  const prefix = alias ? `${alias}.` : '';
+  return `(${prefix}status = 'active' AND ${publishable} AND ${doorKnownSql(prefix)})`;
+}
 
 // Every project ON THE MAP, in the public projection (no owner_github_id, no status) — ONE
 // PAGE of it (task 1003561, which absorbed task 1003560). `visibility` is projected because
@@ -235,7 +248,7 @@ async function listPublicProjects({ pool = defaultPool, limit = PUBLIC_FEED_MAX_
   const { rows } = await pool.query(
     `SELECT origin, name, tagline, art_url, type, template, created_at, visibility
        FROM platform_identity_projects
-      WHERE status = 'active' AND ${publishableSql()} AND ${DOOR_KNOWN_SQL}
+      WHERE ${onMapSql()}
       ORDER BY ${IDENTIFIED_SQL} DESC,
                (${IDENTIFIED_SQL} AND featured) DESC,
                (CASE WHEN ${IDENTIFIED_SQL} THEN created_at END) DESC,
@@ -260,5 +273,6 @@ module.exports = {
   feedShapeFor,
   PUBLIC_FEED_MAX_PAGE_SIZE,
   DOOR_KNOWN_SQL,
+  onMapSql,
   listPublicProjects,
 };

package/modules/platform-identity/tests/platform-identity.mjs

@@ -18,6 +18,7 @@ import { readFileSync } from 'node:fs';
 
 const require = createRequire(import.meta.url);
 const P = require('../platform-identity.js');
+const { onMapSql } = require('../projects-feed.js');
 const terms = require('../terms-acceptance.js');
 
 let passed = 0, failed = 0;
@@ -287,7 +288,7 @@ await ta('listPublicProjects returns a PUBLIC projection (on-the-map only, no ow
   // R06 (task 1002325) replaced the `featured = true` gate with the derived publish
   // gate: a project is on the map iff it is active AND publishable (ADR 0182 D3).
   // The full predicate + the stealth redaction are pinned by tests/visible_projects_feed.mjs.
-  assert.match(c.text, /WHERE status = 'active' AND /);
+  assert.match(c.text, /WHERE \(status = 'active' AND /);
   assert.ok(c.text.includes(P.publishableSql()), 'the map predicate is the shared gate');
   // Pin the SELECT LIST itself, not the whole query — an ORDER BY mention must
   // not satisfy a projection guard, and SELECT * must never sneak owner/status
@@ -681,6 +682,11 @@ await ta('getRollupForBuilder aggregates un-fanned + names only publicly-catalog
   const aggCte = aggSql.slice(aggSql.indexOf('WITH agg AS'), aggSql.indexOf('disc AS'));
   assert.doesNotMatch(aggCte, /unnest/i, 'scalar CTE must not fan rows out');
   assert.match(aggSql.slice(aggSql.indexOf('disc AS')), /array_agg\(DISTINCT x\.d\)/);
+  // WHO is named (task 1003558): on the map by the feed's own predicate AND Public.
+  const isPublic = (pool.calls[1].text.match(/\(p\.id IS NOT NULL[\s\S]*?\) AS is_public/) || [''])[0];
+  assert.ok(isPublic.includes(onMapSql('p')), 'names read the feed\'s on-the-map predicate, not a restatement');
+  assert.match(isPublic, /AND p\.visibility = 'public'\) AS is_public$/, 'Private and Stealth are counted, never named');
+  assert.doesNotMatch(isPublic, /featured/, 'featured only ranks the feed (ADR 0182 D3); it gates no name');
 });
 
 await ta('getPublicProfileExtras is fail-closed: null for missing / provisional / hidden accounts', async () => {

package/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@bongos/core",
-  "version": "1.19.777",
+  "version": "1.19.779",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@bongos/core",
-      "version": "1.19.777",
+      "version": "1.19.779",
       "license": "AGPL-3.0-or-later",
       "dependencies": {
         "express": "^4.21.2",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bongos/core",
-  "version": "1.19.777",
+  "version": "1.19.779",
   "description": "Cloud Bongos — the AI-first build platform core (GDS + platform surfaces + module system), installed as a versioned dependency (ADR 0108).",
   "license": "AGPL-3.0-or-later",
   "main": "src/platform-server.js",

package/src/module-api.js

@@ -71,7 +71,7 @@ const { responsibilityFor, ROLE_RESPONSIBILITIES } = require('./role-responsibil
 // there. scripts/gds/bump-version.js still rewrites the literal below; it appends
 // the entry to that file. Look for a version's history there, not here.
 // ---------------------------------------------------------------------------
-const CORE_VERSION = '1.19.777'; // CI auto-patch carrier (ADR 0161); changelog: docs/module-api-changelog.md
+const CORE_VERSION = '1.19.779'; // CI auto-patch carrier (ADR 0161); changelog: docs/module-api-changelog.md
 
 // A namespaced logger so a module's log lines are attributable + consistent.
 // Usage: const log = api.logger('dev-box'); log.info('mounted');

package/tests/hub_recent_ships.mjs

@@ -237,6 +237,19 @@ await t('getRollupForBuilder attaches recent_ships to publicly-named projects on
   assert.ok(!serialized.includes('SECRET-PROJECT'), 'nor does its name (the pre-existing rule this one follows)');
 });
 
+await t('works follow the NAME: the one statement that reads recent_ships names Public projects only (task 1003558)', async () => {
+  // A second, wider read of the works would let a Private project's titles out while
+  // its name stayed counted. So the works and the naming verdict must share a row.
+  const pool = mockPool((sql) => (/WITH agg AS/.test(sql)
+    ? { rows: [{ projects: 0, credits: 0, works_shipped: 0, karma: 0, last_active: null, disciplines: null }] }
+    : { rows: [] }));
+  await pi.getRollupForBuilder(42, { pool });
+  const reads = pool.calls.filter((c) => /recent_ships/.test(c.text));
+  assert.equal(reads.length, 1, 'exactly one statement reads the works');
+  assert.match(reads[0].text, /AND p\.visibility = 'public'\) AS is_public/, 'and it decides the name on the same row');
+  assert.doesNotMatch(reads[0].text, /featured/, 'featured gates no name, so it gates no work either');
+});
+
 await t('a project that reported no works reads as an empty list, not null', async () => {
   const pool = mockPool((sql) => {
     if (/WITH agg AS/.test(sql)) return { rows: [{ projects: 1, credits: 0, works_shipped: 0, karma: 0, last_active: null, disciplines: null }] };

package/tests/profile_rollup_consent.mjs

@@ -8,9 +8,10 @@
 //      /scouting by construction. Consent is TWO columns since ADR 0213
 //      (profile_state='active' AND terms_accepted_at IS NOT NULL), and the
 //      LEGACY fixture is the pre-terms row that proves the second one.
-//   2. getRollupForBuilder aggregates un-fanned and names ONLY projects whose
-//      catalog row is publicly listed (featured + active); everything else is
-//      counted in more_projects, never named. client_id never crosses.
+//   2. getRollupForBuilder aggregates un-fanned and names ONLY projects that are
+//      on the map AND Public (task 1003558) — featured or not; Private, Stealth
+//      and door-unknown rows are counted in more_projects, never named.
+//      client_id never crosses.
 //   3. getPublicProfileExtras is fail-closed (missing/provisional/hidden/
 //      non-numeric → null); getOwnProfileExtras serves the self view anyway.
 //   4. upsertAccount's consent upgrade is one-way (activate flips provisional →
@@ -53,15 +54,18 @@ try {
 const ACTIVE = 90002278, HIDDEN = 90002279, PROV = 90002280, LAZY = 90002281, LEGACY = 90002283;
 const ALL_IDS = [ACTIVE, HIDDEN, PROV, LAZY, LEGACY];
 const PUB_CLIENT = 't1002278-pub', PRIV_CLIENT = 't1002278-priv', LOST_CLIENT = 't1002278-lost';
-const ALL_CLIENTS = [PUB_CLIENT, PRIV_CLIENT, LOST_CLIENT];
+const STEALTH_CLIENT = 't1003558-stealth', UNREAD_CLIENT = 't1003558-unread';
+const ALL_CLIENTS = [PUB_CLIENT, PRIV_CLIENT, LOST_CLIENT, STEALTH_CLIENT, UNREAD_CLIENT];
 const PUB_ORIGIN = 'https://t1002278-pub.example', PRIV_ORIGIN = 'https://t1002278-priv.example';
+const STEALTH_ORIGIN = 'https://t1003558-stealth.example', UNREAD_ORIGIN = 'https://t1003558-unread.example';
+const ALL_ORIGINS = [PUB_ORIGIN, PRIV_ORIGIN, STEALTH_ORIGIN, UNREAD_ORIGIN];
 const q = (sql, params) => pool.query(sql, params);
 
 async function cleanup() {
   await q(`DELETE FROM platform_identity_builder_project_activity WHERE github_id = ANY($1::bigint[])`, [ALL_IDS]).catch(() => {});
   await q(`DELETE FROM platform_identity_project_memberships WHERE github_id = ANY($1::bigint[])`, [ALL_IDS]).catch(() => {});
   await q(`DELETE FROM platform_identity_accounts WHERE github_id = ANY($1::bigint[])`, [ALL_IDS]).catch(() => {});
-  await q(`DELETE FROM platform_identity_projects WHERE origin = ANY($1::text[])`, [[PUB_ORIGIN, PRIV_ORIGIN]]).catch(() => {});
+  await q(`DELETE FROM platform_identity_projects WHERE origin = ANY($1::text[])`, [ALL_ORIGINS]).catch(() => {});
   await q(`DELETE FROM platform_identity_sso_clients WHERE client_id = ANY($1::text[])`, [ALL_CLIENTS]).catch(() => {});
 }
 
@@ -75,12 +79,20 @@ try {
   // (012), and the consent floor tests terms_accepted_at (019). Without them a
   // FRESH database answers 42703 "column does not exist" — an infrastructure
   // error dressed up as a boundary failure — instead of a clean assertion.
+  // 011 and 020 carry the columns the naming rule reads (description, visibility,
+  // the door-known pair); 012_recent_ships the column the rollup SELECTs; 008 and
+  // 009 the handle and display_name_source columns upsertAccount writes.
   await q(migrationSql('platform_identity_001_tables.sql'));
   await q(migrationSql('platform_identity_004_projects.sql'));
   await q(migrationSql('platform_identity_005_builder_activity.sql'));
   await q(migrationSql('platform_identity_007_profile_consent.sql'));
+  await q(migrationSql('platform_identity_008_handle.sql'));
+  await q(migrationSql('platform_identity_009_profile_fields.sql'));
+  await q(migrationSql('platform_identity_011_project_visibility.sql'));
   await q(migrationSql('platform_identity_012_account_privacy.sql'));
+  await q(migrationSql('platform_identity_012_recent_ships.sql'));
   await q(migrationSql('platform_identity_019_terms_acceptance.sql'));
+  await q(migrationSql('platform_identity_020_visibility_pull.sql'));
   await cleanup();
 
   // CONSENT IS TWO COLUMNS (ADR 0213, task 1002913): profile_state='active' AND
@@ -96,27 +108,39 @@ try {
             ($4, 'legacy-b', 'Legacy', 'active', false, NULL)`,
     [ACTIVE, HIDDEN, PROV, LEGACY],
   );
-  // Three reporting projects: one publicly catalogued (featured+active), one
-  // catalogued but NOT featured (→ never named), one with no catalog row at all.
+  // Five reporting projects (task 1003558). All but Lost are active and described;
+  // only Pub is on the map AND Public — and it is the one that is NOT featured, so
+  // the old `featured` gate would name exactly the wrong rows:
+  //   Pub     public,  unfeatured, door assigned  → named
+  //   Priv    private, featured,   door assigned  → counted
+  //   Stealth stealth, featured,   door assigned  → counted
+  //   Unread  public,  featured,   door never read → counted (dark matter)
+  //   Lost    no catalog row at all              → counted
   await q(
     `INSERT INTO platform_identity_sso_clients (client_id, secret_hash, name, origin)
-     VALUES ($1, 'x', 'Pub Proj', $4), ($2, 'x', 'Priv Proj', $5), ($3, 'x', 'Lost Proj', NULL)`,
-    [...ALL_CLIENTS, PUB_ORIGIN, PRIV_ORIGIN],
+     VALUES ($1, 'x', 'Pub Proj', $6), ($2, 'x', 'Priv Proj', $7), ($3, 'x', 'Lost Proj', NULL),
+            ($4, 'x', 'Stealth Proj', $8), ($5, 'x', 'Unread Proj', $9)`,
+    [...ALL_CLIENTS, ...ALL_ORIGINS],
   );
   await q(
-    `INSERT INTO platform_identity_projects (origin, name, featured, status)
-     VALUES ($1, 'Pub Proj', true, 'active'), ($2, 'Priv Proj', false, 'active')`,
-    [PUB_ORIGIN, PRIV_ORIGIN],
+    `INSERT INTO platform_identity_projects (origin, name, description, featured, status, visibility, visibility_source)
+     VALUES ($1, 'Pub Proj',     'described', false, 'active', 'public',  'control-plane'),
+            ($2, 'Priv Proj',    'described', true,  'active', 'private', 'control-plane'),
+            ($3, 'Stealth Proj', 'described', true,  'active', 'stealth', 'control-plane'),
+            ($4, 'Unread Proj',  'described', true,  'active', 'public',  NULL)`,
+    ALL_ORIGINS,
   );
   await q(
     `INSERT INTO platform_identity_builder_project_activity
        (client_id, github_id, credits, tasks_shipped, karma, rank_held, disciplines, last_active)
-     VALUES ($1, $4, 100, 5, 3, 'metic',  '{engineer,ui}', '2026-01-01T00:00:00Z'),
-            ($2, $4,  50, 2, 1, 'archon', '{artist}',      '2026-02-01T00:00:00Z'),
-            ($3, $4,  25, 1, 0, NULL,     '{}',            '2026-03-01T00:00:00Z'),
-            ($1, $5,  60, 4, 2, 'metic',  '{engineer}',    '2026-01-01T00:00:00Z'),
-            ($1, $6,  10, 1, 0, 'xenos',  '{engineer}',    '2026-01-01T00:00:00Z'),
-            ($1, $7,  90, 3, 1, 'metic',  '{engineer}',    '2026-01-01T00:00:00Z')`,
+     VALUES ($1, $6, 100, 5, 3, 'metic',  '{engineer,ui}', '2026-01-01T00:00:00Z'),
+            ($2, $6,  50, 2, 1, 'archon', '{artist}',      '2026-02-01T00:00:00Z'),
+            ($3, $6,  25, 1, 0, NULL,     '{}',            '2026-03-01T00:00:00Z'),
+            ($4, $6,   0, 0, 0, 'thetes', '{}',            '2025-12-01T00:00:00Z'),
+            ($5, $6,   0, 0, 0, 'thetes', '{}',            '2025-12-01T00:00:00Z'),
+            ($1, $7,  60, 4, 2, 'metic',  '{engineer}',    '2026-01-01T00:00:00Z'),
+            ($1, $8,  10, 1, 0, 'xenos',  '{engineer}',    '2026-01-01T00:00:00Z'),
+            ($1, $9,  90, 3, 1, 'metic',  '{engineer}',    '2026-01-01T00:00:00Z')`,
     [...ALL_CLIENTS, ACTIVE, HIDDEN, PROV, LEGACY],
   );
 
@@ -133,18 +157,20 @@ try {
 
   // 2 — getRollupForBuilder semantics.
   const r = await pi.getRollupForBuilder(ACTIVE, { pool });
-  assert.deepEqual(r.totals, { projects: 3, credits: 175, works_shipped: 8, karma: 4 });
+  assert.deepEqual(r.totals, { projects: 5, credits: 175, works_shipped: 8, karma: 4 });
   pass++; console.log('  ok - totals aggregate un-fanned across the builder\'s projects');
   assert.deepEqual([...r.disciplines].sort(), ['artist', 'engineer', 'ui']);
   pass++; console.log('  ok - disciplines are the deduped union');
   ok(new Date(r.last_active).toISOString() === '2026-03-01T00:00:00.000Z', 'last_active is the max');
-  ok(r.projects.length === 1 && r.projects[0].name === 'Pub Proj', 'only the publicly-catalogued project is named');
-  assert.deepEqual(Object.keys(r.projects[0]).sort(), ['name', 'origin', 'rank_held']);
-  pass++; console.log('  ok - named rows carry exactly name/origin/rank_held');
+  ok(r.projects.length === 1 && r.projects[0].name === 'Pub Proj', 'only the on-the-map Public project is named — unfeatured, and named anyway');
+  assert.deepEqual(Object.keys(r.projects[0]).sort(), ['name', 'origin', 'rank_held', 'recent_ships']);
+  pass++; console.log('  ok - named rows carry exactly name/origin/rank_held/recent_ships');
   ok(r.projects[0].rank_held === 'metic', 'rank_held is that project\'s reported standing');
-  ok(r.more_projects === 2, 'unfeatured + uncatalogued projects are counted, never named');
+  ok(r.more_projects === 4, 'Private, Stealth, door-unknown and uncatalogued projects are counted, never named');
   ok(!JSON.stringify(r).includes('client_id'), 'client_id never crosses the shape');
-  ok(!JSON.stringify(r).includes('Priv Proj'), 'a non-public project name never crosses');
+  for (const unnamed of ['Priv Proj', 'Stealth Proj', 'Unread Proj', PRIV_ORIGIN, STEALTH_ORIGIN, UNREAD_ORIGIN]) {
+    ok(!JSON.stringify(r).includes(unnamed), `"${unnamed}" never crosses`);
+  }
 
   // 3 — the port reads.
   ok(await pi.getPublicProfileExtras(HIDDEN, { pool }) === null, 'public read → null for a hidden builder');

package/tests/profile_route.mjs

@@ -345,16 +345,37 @@ const HIDDEN_LOGIN = 'hidden-DO-NOT-LEAK-r06';
 const PROV_LOGIN = 'provisional-DO-NOT-LEAK-r06';
 const PRIVATE_LOGIN = 'private-DO-NOT-LEAK-r06';
 
-// TWO projects — one publicly catalogued, one not. Distinctive digits so the
-// "no partial numbers" scan below cannot pass by coincidence.
+// TWO projects, both on the map — one Public and UNFEATURED, one Private and
+// FEATURED — so neither the old `featured` gate nor a door-blind one passes
+// (task 1003558). Distinctive digits so the "no partial numbers" scan below
+// cannot pass by coincidence.
+const ON_MAP = { status: 'active', description: 'described', visibility_source: 'control-plane', visibility_reported_at: null };
 const PROOF_PROJECTS = [
   { name: 'R06 Public Proj', origin: 'https://r06-pub.example', rank_held: 'metic',
-    credits: 60271, tasks_shipped: 4103, karma: 9021, is_public: true },
+    credits: 60271, tasks_shipped: 4103, karma: 9021, catalog: { ...ON_MAP, visibility: 'public', featured: false } },
   { name: SECRET_PROJECT_NAME, origin: 'https://r06-priv.example', rank_held: 'archon',
-    credits: 40129, tasks_shipped: 2011, karma: 3007, is_public: false },
+    credits: 40129, tasks_shipped: 2011, karma: 3007, catalog: { ...ON_MAP, visibility: 'private', featured: true } },
 ];
 const sumOf = (k) => PROOF_PROJECTS.reduce((n, p) => n + p[k], 0);
 
+// getRollupForBuilder's `is_public`, evaluated the scouting engine's way: a catalog
+// row is named unless a predicate the SQL actually DECLARES refuses it. Drop
+// `p.visibility = 'public'` from the module and the Private project gets named here.
+function namedByDeclaredSql(sql, project) {
+  const expr = (sql.match(/\(p\.id IS NOT NULL[\s\S]*?\) AS is_public/) || [''])[0];
+  const c = { name: project.name, ...project.catalog };
+  const declared = [
+    [/p\.featured/, c.featured === true],
+    [/p\.status = 'active'/, c.status === 'active'],
+    [/coalesce\(p\.name, ''\)\) <> ''/, String(c.name ?? '').trim() !== ''],
+    [/coalesce\(p\.description, ''\)\) <> ''/, String(c.description ?? '').trim() !== ''],
+    [/p\.visibility_source = 'control-plane' OR p\.visibility_reported_at IS NOT NULL/,
+      c.visibility_source === 'control-plane' || c.visibility_reported_at != null],
+    [/p\.visibility = 'public'/, c.visibility === 'public'],
+  ];
+  return expr !== '' && declared.every(([re, holds]) => !re.test(expr) || holds);
+}
+
 // The one account row the reads consult. setAccountHideStats mutates it.
 // ADR 0213 (task 1002913): consent is profile_state AND an acceptance of the
 // platform terms, both stamped by the same upsertAccount branch.
@@ -415,7 +436,8 @@ const engine = {
     }
     // getRollupForBuilder's per-project rows (the client_id → origin two-hop).
     if (/platform_identity_sso_clients/.test(sql)) {
-      return { rows: PROOF_PROJECTS.map((p) => ({ name: p.name, origin: p.origin, rank_held: p.rank_held, is_public: p.is_public, recent_ships: [] })) };
+      return { rows: PROOF_PROJECTS.map((p) => ({ name: p.name, origin: p.origin, rank_held: p.rank_held,
+        is_public: namedByDeclaredSql(sql, p), recent_ships: [] })) };
     }
     // getRollupForBuilder's un-fanned aggregate — summed ACROSS both projects.
     if (/AS works_shipped/.test(sql)) {
@@ -460,9 +482,38 @@ await t('R06.1 a two-project builder\'s COMBINED record shows to another account
   assert.equal(cp.totals.works_shipped, sumOf('tasks_shipped'), 'ships are summed across both');
   assert.equal(cp.totals.karma, sumOf('karma'), 'karma is summed across both');
   assert.deepEqual(cp.disciplines, ['engineer', 'ui'], 'the disciplines union spans both projects');
-  assert.equal(cp.projects.length, 1, 'only the publicly-catalogued project is NAMED');
+  assert.equal(cp.projects.length, 1, 'only the Public project is NAMED — unfeatured, and named anyway');
   assert.equal(cp.projects[0].name, PROOF_PROJECTS[0].name);
-  assert.equal(cp.more_projects, 1, 'the other is counted, never named');
+  assert.equal(cp.more_projects, 1, 'the Private one is counted, never named — featured, and unnamed anyway');
+});
+
+await t('R06.1 a name needs the map AND the Public door — every other shape is counted, never named (task 1003558)', async () => {
+  const [pub, other] = PROOF_PROJECTS;
+  const original = other.catalog;
+  const unnamed = {
+    private: { ...original, visibility: 'private' },
+    stealth: { ...original, visibility: 'stealth' },
+    'public, door never read': { ...original, visibility: 'public', visibility_source: null, visibility_reported_at: null },
+    'public, no description (dark matter)': { ...original, visibility: 'public', description: '  ' },
+    'public, hidden from the catalog': { ...original, visibility: 'public', status: 'hidden' },
+  };
+  try {
+    for (const [label, catalog] of Object.entries(unnamed)) {
+      other.catalog = catalog;
+      const r = await get(port, '/api/gds/builders/95/profile');
+      const cp = r.json.cross_project;
+      assert.deepEqual(cp.projects.map((p) => p.name), [pub.name], `${label}: only the Public project is named`);
+      assert.equal(cp.more_projects, 1, `${label}: counted`);
+      assert.ok(!r.text.includes(SECRET_PROJECT_NAME) && !r.text.includes(other.origin), `${label}: neither its name nor its origin crosses`);
+    }
+    // The positive control: the same row IS named once Public and on the map, so the
+    // refusals above are the door, not a fixture nothing could ever name.
+    other.catalog = { ...original, visibility: 'public' };
+    const r = await get(port, '/api/gds/builders/95/profile');
+    assert.deepEqual(r.json.cross_project.projects.map((p) => p.name), [pub.name, SECRET_PROJECT_NAME]);
+  } finally {
+    other.catalog = original;
+  }
 });
 
 await t('R06.1 the record is viewer-INDEPENDENT — another account sees the same body', async () => {

package/tests/visible_projects_feed.mjs

@@ -463,7 +463,9 @@ test('dark matter never reaches the route at all — the exclusion is in SQL', a
   const src = require('node:fs').readFileSync(
     new URL('../modules/platform-identity/projects-feed.js', import.meta.url), 'utf8');
   const fn = (src.match(/async function listPublicProjects[\s\S]*?\n\}/) || [''])[0];
-  assert.ok(fn.includes('publishableSql()'), 'the gate is applied in the query, not after it');
+  assert.ok(fn.includes('onMapSql()'), 'the gate is applied in the query, not after it');
+  const feed = require('../modules/platform-identity/projects-feed.js');
+  assert.ok(feed.onMapSql().includes(pi.publishableSql()), 'and on-the-map carries the publish gate');
 });
 
 // ── the route's half of the page window (task 1003560 → 1003561) ─────────────

package/.claude/skills/builder-box/SKILL.md

@@ -1,59 +0,0 @@
----
-name: builder-box
-description: >-
-  Show the builder their OWN dev box — state, address, cost, keys — and get them back on it. Own-scoped; never parks or destroys a box. Triggers: "/builder-box", "is my box up", "wake my box", "what's my sandbox URL".
----
-
-You are showing a builder the status of **their own** dev box and helping them get (back) onto it. This is a read-only, own-scoped helper — it never mutates infrastructure (provision / park / wake / deprovision live on the operator control plane, `node scripts/gds/box.js`, gated by rank).
-
-## Background
-
-The per-builder box lifecycle (ADR 0031 §2) auto-suspends when idle (snapshot-and-park) and recreates on demand, so a builder's box is often `parked` between sessions — that's normal and cheap, not a problem. **The idle sweep parks; it does not destroy** (task 1002726 — it *did* destroy droplet and snapshot for a long stretch, so a builder who remembers losing work that way is remembering something real that is now fixed). Full reclaim happens only after `BOX_DORMANT_DAYS` (14) parked, and **only after a warning was actually delivered** — an unwarned box is deferred, not reclaimed (task 1002727). The read API:
-- `GET /api/gds/box/me` → the caller's box: `state`, `scope`, `ip`, `hostname`, cost, activity timestamps.
-- `GET /api/gds/box/ssh-key` → the caller's registered SSH keys (fingerprints + labels).
-- `GET /api/gds/box/terminal` → the caller's active box's browser-terminal `url` + basic-auth `credential` (the Chromebook/browser on-ramp, ADR 0038), once the box has published them.
-
-**The hands-off on-ramp (#701).** A builder no longer needs an operator to get or wake a box. `POST /api/gds/box/ensure` is the "make my box ready" button: it **auto-provisions** if they have no box, or **wakes** a parked one — by queuing a request the control plane runs within ~1 min (the web server never touches DigitalOcean directly). For a Chromebook, after `ensure` reports `active`, `GET /box/terminal` returns the terminal `url` + `credential` (ADR 0038) to open in the browser.
-
-## How to use
-
-1. **Fetch the box + keys + the resolved scope** (own-scoped; uses the builder's session token):
-   ```bash
-   node -e 'const{apiCall}=require("./scripts/gds/cli-lib");(async()=>{for(const p of ["/api/gds/box/me","/api/gds/box/ssh-key","/api/gds/box/scope"]){const r=await apiCall("GET",p);console.log(p,r.status,JSON.stringify(r.data));}})()'
-   ```
-   (If the script returns "no Bongos session", run `/builder-setup` first.)
-
-   **Always report the scope, not just the state** (task 1002731). `/box/scope` returns `{scope, modules, sparse_paths, task_scope}`, and a too-narrow box is otherwise a *silent* failure — the builder sees a working box that is quietly missing the code they need. Read it out:
-   - `scope: 'task'` → name the modules: *"your box holds dev-box, hall-ui — and nothing else."*
-   - `scope: 'base'` → **say plainly that the box has no `modules/` code at all.** With no active claim that is expected; claiming a task and running `/builder-sync` fixes it.
-   - `scope: 'full'` with `modules: []` → the task-1002729 fallback fired: they hold claims, but those claims' goals declare no `scope_modules`, so the box fell back to their rank. Usable, but task-scoping is not actually doing anything — setting the goal's wall would give a tighter box.
-   - `scope: 'starter'` → the fixed newcomer slice, not scoped to their claim.
-
-2. **Relay it in plain language:**
-   - **state = `none`** → they have no box yet. On a Mac/Windows: run `/builder-connect` (registers their SSH key + installs the Desktop file). To actually create the box hands-off, `POST /api/gds/box/ensure` queues the auto-provision (no operator CLI needed). *(The old path — ask an operator to `box.js onboard <login>` — still works but is no longer required.)*
-   - **state = `active`** → box is up at `hostname` (`ip`). They can connect from Claude Desktop → Code → Environment → "Example Dev Box". For a browser/Chromebook (ADR 0038), the terminal comes from the web: `GET /api/gds/box/terminal` returns a `url` + a basic-auth `credential` (username `otb`, password = <redacted>; open the url, enter them, then type `claude` in the terminal. No SSH needed.
-     - **Live game preview — the sandbox (ADR 0044).** If `/box/terminal` returns a `url` (i.e. the box is on the named tunnel), the builder also has a private live preview of the game running on their own box, at the **same hostname with `term-` swapped for `sandbox-`** — e.g. terminal `https://term-<login>.example.com` → preview `https://sandbox-<login>.example.com`. It serves their working copy of the game (degraded — fully playable, no saved state), so they can review changes in a browser **without shipping to prod**. The loop: edit in the terminal → run **`/builder-stage`** (or `box-preview restart`) → refresh the preview tab. Staging via `/builder-stage` also records the review marker that `/builder-ship`'s sandbox-first gate checks (#927, ADR 0046) — on a dev box, game changes are staged + reviewed on the sandbox before they ship to the main game. `box-preview status` shows whether it's up + the URL; `box-preview logs` tails the server. (No preview on a quick-tunnel box — that path can't carry the game port; it needs the named tunnel.)
-   - **state = `parked`** → idle-suspended (cheap, expected). It wakes on demand: `POST /api/gds/box/ensure` queues the wake and it's back in ~1 min (no operator needed). Their data IS safe in the snapshot — say so plainly, and mean it: the idle path preserves the filesystem, and the only thing that deletes the snapshot warns them first with days of lead time.
-   - **state = `destroyed`** → the box is genuinely gone, and so is anything uncommitted on it. This is NOT the idle path — it means they closed it themselves, an operator deprovisioned it, or it sat parked past the dormancy window after being warned. `POST /box/ensure` gives them a **fresh** box, not their old one; don't imply otherwise.
-   - **state = `provisioning` / `waking`** → in flight; check back in a minute.
-   - **state = `error`** → flag it to an operator (don't try to fix infra from here).
-   - **SSH keys** → list the fingerprints + labels. If empty, they haven't connected yet → `/builder-connect`. They can remove a stale key with `DELETE /api/gds/box/ssh-key/:id` (own-scoped).
-
-3. **Cost framing (if asked):** a box only bills compute while `active`; parked costs ~$0.30/mo (just the snapshot). The number in `compute_cost_usd` is their box's running total.
-
-## Constraints
-
-- **`POST /box/ensure` is the only mutation a builder may trigger** — and it only *queues* an auto-provision/wake of their **own** box (rank-gated, one open request at a time); the web server never touches DigitalOcean. Never call provision/park/wake/**deprovision** directly — those are operator control-plane commands (`node scripts/gds/box.js`), rank-gated. If the builder wants their box destroyed, that's an operator action.
-- **Own resource only.** `/box/me` and `/box/ssh-key` are scoped to the caller. The full roster (`GET /api/gds/boxes`) is Metic+ (`box.fleet.manage`, metic-floored since ADR 0157) — don't try it for a sub-Metic builder.
-- **Don't print the SSH private key** — these endpoints only ever return public fingerprints, never private material. Keep it that way.
-
-## Quirks on the box (verified from ssh sessions)
-
-- **`sharp` resolves only from `/workspace`.** Run image-pipeline tooling (art gen, thumbnailing) from `/workspace` — invoking it from another cwd on the box fails to resolve the native binding.
-- **Playwright MCP writes screenshots to `.playwright-mcp/` relative to the server's cwd**, not the caller's — look there first when a screenshot path seems to have gone missing.
-- **The Bash tool's cwd persists between calls on the box.** A bare `cd x` silently shifts every later command in the session; prefer absolute paths over `cd`-then-relative sequences.
-
-## Files this skill touches
-
-- Calls: `/api/gds/box/me`, `/api/gds/box/ssh-key` (read), `/api/gds/box/terminal` (read), optionally `POST /api/gds/box/ensure` (queue auto-provision/wake) or `DELETE /api/gds/box/ssh-key/:id`
-- Reads: `~/.config/otb/gds-session.json` (the session token, via cli-lib)

package/.claude/skills/builder-connect/SKILL.md

@@ -1,60 +0,0 @@
----
-name: builder-connect
-description: >-
-  Connect Claude Desktop to the builder's dev box: GitHub sign-in, SSH key, connection file, then restart Desktop. Builder side only. Triggers: "/builder-connect", "connect me to the dev box", "set up my dev box", "onboard me to the box".
----
-
-You are guiding a builder through connecting their **own machine's** Claude Desktop to their org dev box. The audience is often non-technical — narrate each step in plain language, and never make them hand-edit files or paste keys around. One command does everything.
-
-## Background (the mental model — ADR 0031)
-
-Claude Code is three pieces: the **screen** (their device — always local), the **worker** (the dev box — where the repo + work live), and the **brain** (Anthropic's servers). This skill wires the screen to the box. The box itself is provisioned by an operator with `node scripts/gds/box.js onboard <login>`; this skill is the builder's half — it registers their SSH key and installs the Desktop connection file so the box shows up as a one-click "Environment".
-
-What the bootstrap does, in order:
-1. **GitHub sign-in** (device flow against Bongos — it prints a short code + a URL to open).
-2. **Creates an SSH key** at `~/.ssh/otb_builder` if absent (the private half never leaves their machine).
-3. **Registers the public key** with Bongos (`POST /box/ssh-key`). The box pulls it into `authorized_keys` itself — no operator SSH round-trip.
-4. **Downloads + installs** the Claude Desktop connection file (`managed-settings.json`) at the OS path.
-
-## How to use
-
-1. **Decide which command to run.** Both do the same thing; pick by where you're running:
-   - **Repo is present locally** (you can see `infra/box-connect.sh`): run the local copy —
-     ```bash
-     bash infra/box-connect.sh
-     ```
-   - **No repo** (a bare laptop with only Claude Desktop): run the hosted bootstrap —
-     - macOS / Linux:
-       ```bash
-       curl -fsSL https://example.com/api/gds/box/connect.sh | bash
-       ```
-     - Windows (PowerShell):
-       ```powershell
-       irm https://example.com/api/gds/box/connect.ps1 | iex
-       ```
-   (For staging, swap the host — or set `GDS_API_BASE` before the local script.)
-
-2. **Relay the GitHub code + URL verbatim.** The script prints a short user code and a `https://github.com/login/device` URL. The builder must open the URL and enter the code. Do not summarize — they need the literal values. The script also tries to pop the URL open automatically.
-
-3. **Wait while it polls.** After they approve in the browser, the script registers the key and installs the connection file. On macOS the install step needs **one `sudo` prompt** (the file lives under `/Library/Application Support/ClaudeCode` — the dir Claude Code actually reads managed settings from; `…/Claude/` is silently ignored).
-
-4. **Confirm the finish state and give the next steps:**
-   - Tell their operator they're registered (so the operator runs `box.js onboard <login>` to provision the box, if not already done).
-   - **Restart Claude Desktop.**
-   - Open **Code → Environment → "Example Dev Box"** to connect.
-
-5. **Once they're on the box**, the first thing to do there is authenticate the Bongos CLI (`/builder-setup` or `node scripts/gds/setup.js`) so the box can pull rank-scoped source and keep their SSH keys in sync.
-
-## Constraints
-
-- **Never print or save the SSH private key or Bongos token anywhere except where the script puts them.** The private key stays at `~/.ssh/otb_builder`; the token is held only in memory on the laptop for the two authenticated calls (it is NOT persisted there — the box gets its own session when they authenticate Claude Code on it).
-- **Don't re-generate a key if `~/.ssh/otb_builder` already exists** — the script reuses it. Overwriting would break an existing box connection. (The script handles this; don't override it.)
-- **If `auth_not_configured` comes back**, Bongos has no GitHub OAuth app — stop and point them to an Archon (`blockers/blockers.md#github-oauth-app`). Don't loop.
-- **Memory + credits are server-side** (ADR 0024) — reassure the builder that nothing about which box they land on affects their history.
-
-## Files this skill touches
-
-- Runs: `infra/box-connect.sh` (or the hosted `GET /api/gds/box/connect.sh` / `.ps1`)
-- Reads/creates: `~/.ssh/otb_builder` (+ `.pub`)
-- Writes (macOS): `/Library/Application Support/ClaudeCode/managed-settings.json`; (Windows): `%ProgramFiles%\ClaudeCode\managed-settings.json` — the dir Claude Code reads managed settings from. **Not** `…/Claude/` or `%ProgramData%\Claude\`, which the app ignores (the box then never appears in the Environment picker).
-- Calls: `/api/gds/auth/device/{start,poll}`, `/api/gds/box/ssh-key`, `/api/gds/box/managed-settings`

package/.claude/skills/builder-sync/SKILL.md

@@ -1,42 +0,0 @@
----
-name: builder-sync
-description: >-
-  Re-fetch the dev box's source now instead of waiting for the ~10-min cron. Runs ON the box. Triggers: "/builder-sync", "sync my box", "re-scope my box", "pull my task's code now", or right after "/builder-claim N".
----
-
-**Script skill (authoritative).** The core action is `node scripts/gds/box-sync.js`. Run it and relay its output verbatim.
-
-You are re-running the dev box's source-fetch **on demand** (BV1.R96, goal 1000051 — task-scoped dev box). The box normally re-fetches on a ~10-min cron; this makes it instant.
-
-## Why this exists
-
-A builder's box holds only the code for their **active claim** (ADR 0148 task-scoping): `GET /box/source-access` returns the sparse-checkout set for the modules the claimed task's goal scopes. The box applies that via `infra/box-source-fetch.sh`, on a cron every ~10 min. So right after `/builder-claim N`, the *new* task's code isn't on the box yet — until the next cron tick.
-
-`box-sync.js` re-runs that fetch **now**. Because the fetch re-reads `/box/source-access`, it **re-scopes the box in place** to whatever the builder currently holds a claim on — seconds after claiming, not ~10 minutes later. The cron stays the backstop.
-
-## How to use
-
-1. **Run it** (on the box):
-   ```
-   node scripts/gds/box-sync.js
-   ```
-   Add `--dry-run` to print what it would run without fetching.
-
-2. **Relay the output.** On success it prints `sync: done — your box now holds the code for your active claim.` The sparse-checkout is now scoped to the active claim's modules (plus the base instance).
-
-3. **Typical flow:** `/builder-claim N` → `/builder-sync` → the box now has task N's module code; open the working folder and start.
-
-## Failure modes
-
-- **`no infra/box-source-fetch.sh found`** — you are **not on a dev box** (off a box your source *is* your local checkout, so there's nothing to sync). This is expected on a laptop; the skill exits non-zero and says so.
-- **The fetch itself errors** — the underlying `box-source-fetch.sh` output is passed through verbatim (e.g. a credential/rank issue surfaces there); relay it and, if it's a rank/claim problem, check the active claim with `/builder-start`.
-
-## Constraints
-
-- **Runs on the box only.** It re-runs the box-side fetch; it does not push, claim, or change scope by itself — scope follows the builder's active claim (change scope by claiming a different task, then sync).
-- **Idempotent + safe.** Re-running is harmless; the cron does the same thing on its own schedule.
-
-## Files this skill touches
-
-- Runs: `scripts/gds/box-sync.js` → `infra/box-source-fetch.sh` (on the box)
-- Reads (indirectly, via the fetch): `GET /box/source-access`

package/.claude/skills/close-box/SKILL.md

@@ -1,44 +0,0 @@
----
-name: close-box
-description: >-
-  Tear down the dev box you are working on, from inside its terminal. Own-scoped — never another builder's box and never any other infrastructure. Triggers: "/close-box", "close my box", "shut down this box", "I'm done with this box", "tear down my dev box".
----
-
-You are closing (deprovisioning) the dev box the builder is currently working on. This is the Claude-side twin of the `close-box` shell command (`infra/close-box.sh`) — same endpoint, for builders who'd rather say "/close-box" inside `claude` than drop to the shell. It is own-scoped and destructive (the box is destroyed), so confirm before firing.
-
-## Background
-
-A per-builder dev box (ADR 0031 §2) is a DigitalOcean droplet. Closing it enqueues a `deprovision` intent that the control-plane runner executes within ~a minute. The box's disk is gone after that — anything in `/workspace` that was not pushed to its remote is lost. The box is cheap to recreate from the builders' hall ("Request dev box" / `/builder-box`), so closing when done is the right cost hygiene; the idle-suspend sweep would otherwise park it automatically after the idle window.
-
-The endpoint:
-- `POST /api/gds/box/close` → enqueues `deprovision` for the **caller's own** box (`auth.requireBuilder`, own resource). Idempotent-ish: if there's no active box it just no-ops.
-
-## What this skill does
-
-Calls `POST /api/gds/box/close` via the cross-platform helper, after confirming with the builder.
-
-## How to use
-
-1. **Confirm intent.** Ask plainly: "Close (deprovision) your dev box? Any work in `/workspace` you haven't pushed will be lost." Proceed only on a clear yes. If the builder only wants to stop *using* it for now (not destroy it), tell them they can just close the tab — with session persistence (#893) their work survives and the box auto-parks when idle — and do NOT close it.
-
-2. **Fire the close:**
-   ```
-   node scripts/gds/api.js POST /api/gds/box/close
-   ```
-   (The helper resolves the Bongos session token + API base itself; no manual token handling.)
-
-3. **Relay the outcome.** On success tell the builder:
-   - The box is closing now (a few seconds).
-   - They can close the browser tab — and if the builders'-hall tab is still open in the background, it auto-closes the terminal tab for them when it sees the box shut down (`modules/hall-ui/public/box-panel.js`). This skill cannot close the tab itself (it has no browser control).
-   - They can provision a fresh box anytime from the hall or with `/builder-box`.
-
-## Constraints
-
-- **Own box only.** This never deprovisions another builder's box. Operator-scoped lifecycle (provision / park / wake / destroy-any) lives in `node scripts/gds/box.js`, gated by rank — not here.
-- **Don't auto-close without a yes.** It is destructive.
-- **It cannot close the browser tab.** Be honest about that — see the relay step.
-
-## Files this skill touches
-
-- Reads: `~/.config/otb/gds-session.json`
-- Calls: `POST /api/gds/box/close`