@bongos/core 1.20.49 → 1.20.51

package/.claude/skills/new-project/SKILL.md

@@ -21,6 +21,10 @@ Six steps are **irreducibly human** and must be rendered as **precise, UI-first,
 
 ## The canonical sequence
 
+### 0. Before the rail — the front door (task 1004417)
+
+The hub's wizard opens on two screens before step 1, after sign-in. **The terms:** the owner ticks that they can sign legally (or get a signature) for the platform's use and acknowledge the terms. The create request carries only `terms_acknowledged: true`; the server records WHICH terms version on the project (`provisioning_instances.terms_ack_at` / `terms_ack_version`, read from the platform's own `TERMS_VERSION`, never from the body). **Demo or create:** two equal doors. The demo route is not built yet (BV2.PS09), so walk the create door. When you guide an owner through the CLI or by hand, send the owner to `/terms` and get the same acknowledgement from them in words before you file anything. The CLI does not record it yet, so a project filed that way stores none.
+
 ### 1. Decide name + address
 
 Interview the owner for: product name, world name, company; the **GitHub repo** (`owner/name`); the **domain** they will use (bring-your-own — ADR 0111 §4); and a DNS/db-safe **instance slug** (lowercase `[a-z0-9-]`, e.g. `mercury`).
@@ -183,6 +187,7 @@ Steps 12 and 13 are **not** part of that criterion and must never gate it. They
 ## Constraints
 
 - **This skill is the source of truth for the sequence.** If a step changes, change it here; `bongos onboard` (task 1982) and the hall wizard (task 1983) must render the same sequence. The machine-readable twin is [`modules/provisioning/onboard-plan.js`](../../../modules/provisioning/onboard-plan.js), served at `GET /provisioning/onboard-plan` — a **rail** step added here gets a step there in the same change, or the two drift and each claims to be canonical.
+- **Step 0 (the front door) is not in that plan either**, for the opposite reason: it comes before the rail, is a hub-screen acknowledgement rather than a creation step, and carries no step of the machine setup. Its record is the project's terms columns, not a rail key.
 - **Steps 12 and 13 are deliberately NOT in that plan**, and that is the distinction to keep: the plan is the creation rail, and both of those run only once the project exists. A step that can only run after the terminal step is not a step in the rail ([ADR 0249](../../../docs/adr/0249-the-invite-step-is-the-done-panel-s-first-act-not-a-rail-step.md)) — it belongs to the done panel and the project's own page, each of which carries its own way back.
 - **Standalone only** (ADR 0108) — do not fall back to editing this monorepo's checkout for a new project.
 - **Never weaken the trust boundary** — the web tier enqueues; only the control-plane runner (`provision.js`) touches cloud tokens (ADR 0016 / 0111 §2).

package/clients/bongos-client/index.d.ts

@@ -412,7 +412,7 @@ export interface PostProvisioningInstancesIdRenderResponse { ok: boolean; queued
 export interface PostProvisioningInstancesIdRepoPrivateResponse { ok: boolean; queued: unknown; action: unknown; status: unknown; message: unknown }
 export interface PostProvisioningInstancesIdRestartResponse { ok: boolean; queued: unknown; action: unknown; status: unknown; message: unknown }
 export interface PostProvisioningInstancesIdTeardownResponse { ok: boolean; queued: unknown; action: unknown; status: unknown; superseded: unknown; message: unknown }
-export interface PostProvisioningInstancesRequest { slug: string; target_ref?: string; hosting_shape?: string; domain?: string; no_address?: boolean; tier?: string; onboard_mode?: string; type?: string; description?: string; detail?: Record<string, unknown>; modules?: string[] }
+export interface PostProvisioningInstancesRequest { slug: string; target_ref?: string; hosting_shape?: string; domain?: string; no_address?: boolean; tier?: string; onboard_mode?: string; type?: string; description?: string; detail?: Record<string, unknown>; modules?: string[]; terms_acknowledged?: boolean }
 export interface PostProvisioningRenderLookupRequest { key: string; owner_id?: string }
 export interface PostRemovalProposalsIdDecideRequest { verdict: string; note?: string }
 export interface PostRenderDeployActRequest { action?: string; deployId?: string; confirm?: unknown; expectLiveDeployId?: unknown }

package/docs/api/openapi.json

@@ -28310,6 +28310,9 @@
               "type": "string"
             },
             "maxItems": 50
+          },
+          "terms_acknowledged": {
+            "type": "boolean"
           }
         },
         "required": [

package/docs/api-reference.md

@@ -586,7 +586,7 @@ Base path: `/api/bongos`. Ranks (enforced server-side, [ADR 0016](adr/0016-trust
 | GET | `/api/bongos/provisioning/github-app/status` | `public` | — | GET /provisioning/github-app/status?state=<> — the PUBLIC progress read the onboarding callback page polls (task 2096) to know when setup… |
 | GET | `/api/bongos/provisioning/health` | `public` | — | GET /provisioning/health — liveness + the core version this module mounted against. |
 | GET | `/api/bongos/provisioning/instances` | `any-builder` | — | GET /provisioning/instances — the caller's own instances + each open intent. |
-| POST | `/api/bongos/provisioning/instances` | `any-builder` | `slug`, `target_ref`, `hosting_shape`, `domain`, `no_address`, `tier`, `onboard_mode`, `type`, `description`, `detail`, `modules` | POST /provisioning/instances — request a new instance. |
+| POST | `/api/bongos/provisioning/instances` | `any-builder` | `slug`, `target_ref`, `hosting_shape`, `domain`, `no_address`, `tier`, `onboard_mode`, `type`, `description`, `detail`, `modules`, `terms_acknowledged` | POST /provisioning/instances — request a new instance. |
 | GET | `/api/bongos/provisioning/instances/:id` | `any-builder` | — | GET /provisioning/instances/:id — read one instance (the manage page's read). |
 | GET | `/api/bongos/provisioning/instances/:id/core-upgrade` | `archon` | — | GET the same path — step ONE of the two-step (ADR 0293 D4): what a move would do. |
 | POST | `/api/bongos/provisioning/instances/:id/core-upgrade` | `archon` | — | POST /provisioning/instances/:id/core-upgrade — move the core pin. |