@bongos/core 1.21.5 → 1.21.7

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

@@ -460,7 +460,7 @@ export interface PostSpecialitiesIdOfferResponse { speciality: unknown }
 export interface PostSpecialitiesIdUnofferResponse { speciality: unknown }
 export interface PostSpecialitiesRequest { name: string; discipline: string; summary?: string; contract_md?: string; visibility?: string; sellable?: boolean; skills?: string[] }
 export interface PostSpecialitiesResponse { speciality: unknown }
-export interface PostSsoActivityRollupRequest { client_id: string; client_secret: string; github_id: StringifiableId; credits?: number; tasks_shipped?: number; karma?: number; rank?: string; disciplines?: unknown; recent_ships?: unknown }
+export interface PostSsoActivityRollupRequest { client_id: string; client_secret: string; github_id: StringifiableId; credits?: number; tasks_shipped?: number; karma?: number; rank?: string; disciplines?: unknown; recent_ships?: unknown; crafts?: unknown }
 export interface PostSsoActivityRollupResponse { ok: boolean }
 export interface PostSsoApplicantProfileRequest { client_id: string; client_secret: string; github_id: StringifiableId }
 export interface PostSsoApplicantProfileResponse { profile: unknown }

package/docs/adr/0361-merges-publish-as-candidates-release-decides-what-others-are-offered.md

@@ -40,6 +40,7 @@ The deploy page's **Release** section lists the versions this hall runs that are
 - The update sweep (ADR 0360) already follows `released` by default.
 - The "update available" banner (`src/bongos/core-update.js`) offers versions at or below `latest`, read from the same packument. With no readable label it has no answer.
 - The platform's upgrade runner for hosted projects (`scripts/gds/provision-core-upgrade.js`) offers a project the versions its follow admits. The follow comes from its hosting shape: the `control-plane` row is the platform hall and takes candidates; every other shape takes releases (`followForShape`). It is derived, not a column, because there is exactly one platform hall. A column someone could set on a tenant would be one more way to hand a project an unreleased version.
+- **A new project is born on the release** ([task 1004299](https://cloudbongos.com/builders#/task/1004299)). The wizard vendors the core this hall runs (ADR 0292), which is a candidate once D1 is on. `projectCoreDecision` (`scripts/gds/provision-repo.js`) gives the project the `latest` version instead whenever the hall runs ahead of it, packed from the registry; the core-pin refresh that runs in the same provisioning pass uses the same target, so it cannot bump the new pin straight back. Level, or no readable label, keeps the byte-exact running core.
 
 ## Arming (owner steps, in this order)
 

package/docs/api/openapi.json

@@ -30413,7 +30413,8 @@
             "maxLength": 32
           },
           "disciplines": {},
-          "recent_ships": {}
+          "recent_ships": {},
+          "crafts": {}
         },
         "required": [
           "client_id",

package/docs/api-reference.md

@@ -767,7 +767,7 @@ Base path: `/api/bongos`. Ranks (enforced server-side, [ADR 0016](adr/0016-trust
 
 | Method | Path | Rank | Body | Description |
 |---|---|---|---|---|
-| POST | `/api/bongos/sso/activity/rollup` | `public` | `client_id`, `client_secret`, `github_id`, `credits`, `tasks_shipped`, `karma`, `rank`, `disciplines`, `recent_ships` | POST /sso/activity/rollup — a federated instance reports a builder's activity snapshot (ADR 0141 §4). |
+| POST | `/api/bongos/sso/activity/rollup` | `public` | `client_id`, `client_secret`, `github_id`, `credits`, `tasks_shipped`, `karma`, `rank`, `disciplines`, `recent_ships`, `crafts` | POST /sso/activity/rollup — a federated instance reports a builder's activity snapshot (ADR 0141 §4). |
 | POST | `/api/bongos/sso/applicant-profile` | `public` | `client_id`, `client_secret`, `github_id` | POST /sso/applicant-profile — a federated instance resolves ONE applicant's profile view for its own reviewer queue, LIVE at render (priv… |
 | GET | `/api/bongos/sso/authorize` | `public` | — | GET /sso/authorize?client_id=&redirect_uri=&state= — the browser authorize leg. |
 | POST | `/api/bongos/sso/device/poll` | `public` | `device_code` | POST /sso/device/poll — poll the hub device flow. |