@bongos/core 1.20.44 → 1.20.45

package/docs/onboarding/slash-commands.md

@@ -12,7 +12,7 @@ When you type `/` in Claude Code you get one list, but the commands in it come f
 | Where it lives | Inside the app — nothing in this repo | [`.claude/skills/<name>/`](../../.claude/skills/) |
 | What it acts on | Your *session* — context, model, config, account | The *build system* — tasks, claims, ships, ideas |
 | Works in any repo? | Yes, everywhere | No — only in a folder that holds this code |
-| Authoritative list | Type `/help` | The folder listing linked above |
+| Authoritative list | Type `/help` | The hall's [Commands](https://example.com/builders/commands) page |
 
 **The short version:** if it changes your Claude session, it's Claude's. If it changes project state — a task, a claim, a ship — it's ours. If you can run it in an unrelated repo, it's Claude's.
 
@@ -20,67 +20,23 @@ When you type `/` in Claude Code you get one list, but the commands in it come f
 
 ## This project's commands
 
-Every one of these talks to the build system. They're grouped by when you'd reach for them, not alphabetically.
+**The full list lives in the Builders Hall, on the [Commands](https://example.com/builders/commands) page** (Docs → Commands in the hall's sidebar). It shows every slash command this project has and every `bongos` terminal command, with what each does, when to reach for it and what it costs, grouped by when you'd reach for them. The page reads the list from the project itself — the `SKILL.md` files a session on this project is actually given, and the CLI's own command table — so it is always current; this file deliberately keeps no second copy that could drift (task 1004473).
 
-### The work loop — the ones you'll use every session
+The ones you'll use every session are the work loop: `/builder-start` → `/builder-claim N` → the work → `/builder-ship` (or `/builder-release` to give a task back), with `/status` and `/recall` to find things out on the way.
 
-| Command | What it does |
-|---|---|
-| `/builder-start` | List the tasks you can claim right now, filtered for parallel-safety |
-| `/builder-claim N` | Lock task N to your session |
-| `/builder-ship` | Grade, merge, and deploy your claimed task (credits land here) |
-| `/builder-release` | Cancel a claim — the task returns to `ready`, no credits |
-| `/builder-stage` | Preview your work-in-progress on your own sandbox before shipping |
-| `/builder-end` | Close out the session safely — resolve the claim, seal the log |
-| `/status` | Version / criterion progress — "what's left for `wa6-kernel-and-packs`?" (a criterion's slug is its name; `C8` is its current position and moves) |
-| `/recall` | Search the docs + project knowledge before re-solving something |
-
-### Your account and your machine
-
-| Command | What it does |
-|---|---|
-| `/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-cost` † | Log or read project spend |
-| `/builder-backup` † | Check or trigger a database backup before risky work |
-| `/builder-exit` † | Offboard or reactivate a builder *(Archon only)* |
+### Typed-only commands
 
-### Triage and planning *(Metic and above)*
+On the Commands page some rows are marked **Type it yourself**. Those are **hidden from Claude's own menu but still work when you type them**. Every listed command's description sits in every session's context whether it is used or not, so the rarely used admin ones carry `disable-model-invocation: true` in their `SKILL.md`: Claude Code leaves them out of what the model sees, and only a person typing `/name` runs them (task 1004471). The catch: plain English will not reach them, and Claude will not start one on its own — type the slash form.
 
-| Command | What it does |
-|---|---|
-| `/owner-review` | One walk through everything waiting on a decision: backlog → bugs → ideas → priorities. Say *"triage ideas"* or *"review the backlog"* and it opens at that step |
-| `/blocker-review` · `/blocker-solve` | Walk open blockers, or drive one to done |
-| `/goal-create` | Plan and create one goal — scope wall, criteria, seed tasks |
-| `/goal-close` † | Close a goal's criteria: test them on the live site and sign off, then decide the ones nothing was delivered for |
-| `/planning-session` † | Scope an upcoming version and seed its task list |
-| `/grade-sweep` † | Check the grader is healthy, then audit what shipped past it |
-| `/merge-mode` | Manual fallback when a confirmed task didn't land |
-
-The four steps of `/owner-review` still answer to their old names — `/backlog-review`, `/bug-triage`, `/idea-triage`, `/priority-session` — and so do `/goal-uat` · `/goal-review` (now the two parts of `/goal-close`) and `/grader-health` · `/grade-audit` (now the two parts of `/grade-sweep`). All of those are typed-only (†).
+The four steps of `/owner-review` still answer to their old names — `/backlog-review`, `/bug-triage`, `/idea-triage`, `/priority-session` — and `/goal-close` and `/grade-sweep` each bundle two older commands that still work on their own (`/goal-uat` · `/goal-review`, and `/grader-health` · `/grade-audit`).
 
 ### Discipline modes — not slash commands any more
 
-The three core crafts no longer have a slash command. `/dev`, `/paint` and `/ideate` were **deleted** when the root instructions split into a role-neutral kernel (`CLAUDE.md`) plus one **role pack** per craft: `docs/packs/engineer.md`, `docs/packs/artist.md`, `docs/packs/ideator.md`. A claimed task's discipline routes you to your pack — the Conductor injects its path into your session on the next prompt, and `claim.js` prints a one-line reminder — and you read it. A module-contributed discipline can still ship a skill, which is how `ui` → `/design` below works.
-
-### Design and art pipeline
-
-`/design` is the ui-discipline playbook (world-first, show-first — shipped by the `ui-design` module, ADR 0197); `/design-sync` † and `/figma-design-sync` † round-trip the UI design system. `/tweak` † applies the next page an artist rewrote in the studio; it ships in the `copy-desk` module, where the studio lives. The `/otb-*` family — `otb-tile-generate`, `otb-design-review`, `otb-character-review`, `otb-feedback-capture`, `otb-figma-sync` — is the reference instance's pixel-art pipeline; it's only meaningful on an instance that runs that pipeline, so it ships in the `pixel-art` module, which is off unless the project turns it on. The design-style skills (`/impeccable`, `/style`, the taste and look skills) are the same: the `design-styles` module, off unless turned on — `/design` tells you which.
-
-### Session and meta
-
-| Command | What it does |
-|---|---|
-| `/session-handoff` | Emit a paste-ready prompt to start a fresh session with |
-| `/read-session-export` | Read a past session's `/export` zip |
-| `/feedback` | Pull in the latest recorded walkthrough bundle |
-| `/new-project` † | Zero-to-live runbook for a brand-new instance |
-| `/builder-redteam` | File a security / vulnerability report |
+The three core crafts no longer have a slash command. `/dev`, `/paint` and `/ideate` were **deleted** when the root instructions split into a role-neutral kernel (`CLAUDE.md`) plus one **role pack** per craft: `docs/packs/engineer.md`, `docs/packs/artist.md`, `docs/packs/ideator.md`. A claimed task's discipline routes you to your pack — the Conductor injects its path into your session on the next prompt, and `claim.js` prints a one-line reminder — and you read it. A module-contributed discipline can still ship a skill, which is how `ui` → `/design` works.
 
-### † Typed-only commands
+### Commands that come with a module
 
-A command marked † is **hidden from Claude's own menu but still works when you type it**. Every listed command's description sits in every session's context whether it is used or not, so the rarely-used admin ones carry `disable-model-invocation: true` in their `SKILL.md`: Claude Code leaves them out of what the model sees, and only a person typing `/name` runs them (task 1004471). The catch: plain English will not reach them, and Claude will not start one on its own — type the slash form.
+Some commands ship inside an optional module and only exist on a project that turns it on — the `/otb-*` pixel-art pipeline (the `pixel-art` module) and the design-style skills such as `/impeccable` and `/style` (the `design-styles` module) are off unless the project enables them. The Commands page lists a module's commands only where that module is on, and names the module beside each one.
 
 ## Claude Code's own commands
 
@@ -121,8 +77,8 @@ These are the ones that actually cause confusion.
 
 ## Two more things worth knowing
 
-**Every listed command has a plain-English twin.** Each skill lists trigger phrases, so *"what can I work on"* reaches `/builder-start` and *"ship it"* reaches `/builder-ship`. You never have to memorise the slash form — except for the typed-only † commands above.
+**Every listed command has a plain-English twin.** Each skill lists trigger phrases, so *"what can I work on"* reaches `/builder-start` and *"ship it"* reaches `/builder-ship`. You never have to memorise the slash form — except for the typed-only commands above.
 
-**Same commands, outside Claude.** The work-loop commands are also a terminal CLI: `bongos start`, `bongos claim N`, `bongos ship`. Same actions, same API — usable from any terminal, a Chromebook, or CI. Run `bongos help` for the verb list.
+**Same commands, outside Claude.** The work-loop commands are also a terminal CLI: `bongos start`, `bongos claim N`, `bongos ship`. Same actions, same API — usable from any terminal, a Chromebook, or CI. Run `bongos help` for the verb list; the hall's Commands page lists them too.
 
-**Rank gates are real.** Some commands above refuse below a certain rank — that's enforced by the server on every request, not by the presence of the file on your disk. See [`canonical-permissions.md`](../canonical-permissions.md).
+**Rank gates are real.** Some of this project's commands refuse below a certain rank — that's enforced by the server on every request, not by the presence of the file on your disk. See [`canonical-permissions.md`](../canonical-permissions.md).

package/docs/page-inventory.json

@@ -10,10 +10,10 @@
     "An id changes only when the host prefix, the data-page value or the file name changes; that is a rename, and records keyed on the old id move with it."
   ],
   "counts": {
-    "pages": 39,
+    "pages": 40,
     "surfaces": 3,
-    "with_states": 32,
-    "states": 182
+    "with_states": 33,
+    "states": 184
   },
   "surfaces": [
     {
@@ -22,7 +22,7 @@
       "at": "modules/hall-ui/public",
       "answers_at": "host prefix builders.",
       "origin": "https://builders.{apex}",
-      "pages": 31
+      "pages": 32
     },
     {
       "id": "landing",
@@ -159,6 +159,35 @@
         "out"
       ]
     },
+    {
+      "id": "builders:commands",
+      "surface": "builders",
+      "module": "hall-ui",
+      "page": "commands",
+      "id_from": "data-page",
+      "title": "Commands",
+      "document_title": "Commands — {{worldName}}",
+      "path": "/commands",
+      "url": "https://builders.{apex}/commands",
+      "files": [
+        "modules/hall-ui/public/commands.html",
+        "modules/hall-ui/public/style.css",
+        "modules/hall-ui/public/commands.css",
+        "modules/hall-ui/public/shell.js",
+        "modules/hall-ui/public/palette.js",
+        "modules/hall-ui/public/dom-utils.js",
+        "modules/hall-ui/public/hall-kit.js",
+        "modules/hall-ui/public/commands-lib.js",
+        "modules/hall-ui/public/commands.js"
+      ],
+      "states_files": [
+        "modules/hall-ui/public/commands.states.json"
+      ],
+      "states": [
+        "in",
+        "out"
+      ]
+    },
     {
       "id": "builders:copy-desk",
       "surface": "builders",