@bongos/core 1.19.188 → 1.19.189

package/.bongos-core.json

@@ -2,22 +2,22 @@
   "artifact": "bongos-core",
   "manifest_schema": 1,
   "generator": "scripts/gds/package-core.js",
-  "core_version": "1.19.188",
-  "core_contract": "1.19.188",
-  "source_commit": "d007613318330a2803d0a0fc1d6111d6e68edd49",
+  "core_version": "1.19.189",
+  "core_contract": "1.19.189",
+  "source_commit": "106408b1519091ef056ef82d9bd542a68308e363",
   "source_ref": "HEAD",
-  "built_at": "2026-08-16T23:22:52.135Z",
+  "built_at": "2026-08-17T00:49:35.464Z",
   "redaction": {
     "model": "docs-redacted+functional-verbatim",
-    "docs_redacted": 308,
+    "docs_redacted": 309,
     "agent_docs_stubbed": 21,
     "functional_verbatim": 1282,
     "rules": 3,
     "gate_literals": 3,
     "gate": "passed"
   },
-  "file_count": 1611,
-  "tree_sha256": "67d041849002f213d0fe7900fc4ffd31daa363a1ebb8e4c79c8dc18a1e8f1c50",
+  "file_count": 1612,
+  "tree_sha256": "386f81ead8236148579f8ab7743305bf0e2edbd8d0349ad9125e23d90eba84fe",
   "files": [
     {
       "path": ".claude/skills/blocker-review/SKILL.md",
@@ -1354,10 +1354,15 @@
       "mode": "0000644",
       "sha256": "c645ce8202fa8e8faa59d3aa00a8167477b5223817b760a733b38864d7625c1d"
     },
+    {
+      "path": "docs/adr/0175-the-board-room-full-idea-ratification.md",
+      "mode": "0000644",
+      "sha256": "aaff11b955bcbacaebf2475d01034dce1c47c70c22534195aebbf90767b025f6"
+    },
     {
       "path": "docs/adr/README.md",
       "mode": "0000644",
-      "sha256": "68c676272ad284adc2dd0c9c05b0c6eb0198577a27dd5f2468257eec9d87faf7"
+      "sha256": "6748701da2559d6019116eb00e9aeeaad947e08d17f9c9cf77e8f45c19e2c69f"
     },
     {
       "path": "docs/api-reference.md",
@@ -4257,12 +4262,12 @@
     {
       "path": "package-lock.json",
       "mode": "0000644",
-      "sha256": "c9866e8f3a03bb27a37058828216a3417a9801d563f2ba225f0789e4c744faf3"
+      "sha256": "15ace363831ad92eff83b61408618af68029feb1701bc757dc007390cfbc13f7"
     },
     {
       "path": "package.json",
       "mode": "0000644",
-      "sha256": "c320b8445c25728e9a37ef01af92966969f35efdd5758782245b108fc2badef7"
+      "sha256": "31315335f0107717d68755300632cd57b25f62b6d58a6b5309ba82030bf894ce"
     },
     {
       "path": "public-docs/index.html",
@@ -5867,7 +5872,7 @@
     {
       "path": "src/module-api.js",
       "mode": "0000644",
-      "sha256": "ba52655bc052427326c93c2501bf8916161d7b81617132f76c973c82b67ff1e0"
+      "sha256": "a47c1e24a6e69d6b109956b1fe0e9acc34905fc148de1199a132301d66e3d597"
     },
     {
       "path": "src/module-loader/catalog.js",

package/docs/adr/0175-the-board-room-full-idea-ratification.md

@@ -0,0 +1,243 @@
+# 0175 — The Board Room: Full Idea ratification as the first upward-pointing gate
+
+- **Status:** Accepted
+- **Date:** 2026-08-17
+- **Task:** [#1003014](https://cloudbongos.com/builders#/task/1003014) (R01 of goal 1000069 — the Board Room)
+- **Related:** ADR 0151 (permissions-as-atoms), 0157 (Archon is rank and identity only), 0162 (verdicts advisory, never self-executing), 0172-per-craft (the ideator credit lane — stream 3), 0174 (government, not governance; "role" means a craft), 0037 (Discord channel layout), 0016 (trust boundary), 0086 (goals + scope walls)
+- **Spec:** [`docs/specs/bongos-v1-board-room.md`](../specs/bongos-v1-board-room.md) — the planning session that produced this decision, with the full interview record
+- **Source ideas:** 1000738 (the Board Room), 1000754 (scoping brief)
+
+## Context
+
+**Every gate in this system points down the rank ladder.** Rank floors, protected paths,
+the grader, Archon approvals — each one constrains someone below the person who set it.
+Nothing points up. An Archon can ship whatever they want, and on 2026-08-16 the owner named
+that as a loophole they can walk through at will:
+
+> *"I am a little unsure about just implementing without team buy-in… Otherwise I can just
+> ship and build as I want, finding loopholes."*
+
+The most senior person on the project asked for a structure that can slow **them** down. That
+framing is the specification, and it is why the decision below is about *legitimacy* rather
+than about permissions — the permission system (ADR 0151) already works, and adding a rank
+floor would only point the gate downward again.
+
+Three constraints shaped what could actually be built.
+
+**1. The ADR 0162 discipline.** Verdicts are advisory and never self-executing. A gate that
+blocks a seeding until a quorum is reached would violate that; a gate that merely records an
+opinion would be theatre. The resolution turned out not to be a compromise between them —
+see Decision 1.
+
+**2. Franchise cannot be role-derived.** ADR 0174 §5 freed the word "role" for the three
+crafts (Artist, Ideator, Builder), which makes a craft-scoped voting chamber superficially
+attractive: an Ideator chamber for ideas, a Builder chamber for seedings. It is not viable.
+`PATCH /me/disciplines` is deliberately ungated — *"a builder owns their own profile"*
+(`src/bongos/routes/me.js`) — so self-selecting into a chamber would be a one-request
+privilege escalation. Role also gates nothing anywhere in the codebase today; authority runs
+rank → rank-role → permission, end to end. **Franchise therefore derives from rank**, and the
+role-chamber model is rejected.
+
+**3. The scale is the "circle" rung.** The governance synthesis this session worked from
+(*The Six Variables of Governance*, Verro Labs, Aug 2026) argues that formality is adopted
+only where informal coordination breaks, and that the thresholds are set by human cognitive
+constants: an executive differentiates around 9 people, written law separates around 50,
+adjudication separates around 150. This project sits at 3–8. A seven-preset Charter Builder
+is a 150-rung constitution, and shipping one now would be building the wrong rung.
+
+## Decision
+
+### 1. The board's subjects are exactly two, and both are rare by construction
+
+The board votes on a **Full Idea** (`modules/ideas`, goal 1000062 — the five-field graded
+deliverable), and on a **change to the constitution itself**. Nothing else. Claims, seedings,
+promotes, ships and grades behave exactly as they do today; Quick Ideas and Sparks keep
+promoting straight to a task, untouched.
+
+Idea 1000738 also wanted votes on task-set seedings and *"anything a member puts up"*. The
+owner narrowed it — *"only Full Detail Ideas (E.g. new goals) should need ratification,
+everything else should function as is"* — and then re-widened it by exactly one subject, so
+that the rule constraining the owner cannot be weakened by the owner alone.
+
+**This is what dissolves the ADR 0162 tension rather than compromising on it.** A board vote
+gates no build path, so nothing self-executes because there is nothing downstream to execute.
+Ratification confers legitimacy and triggers a credit award; it does **not** auto-create the
+goal (goal 1000062 already settled that a Full Idea is not auto-converted — the conversion
+recommendation stays a human step).
+
+Board items carry a `subject_type` (`full_idea` | `constitutional_amendment`) **from day one**.
+A third subject should be a row, not a migration.
+
+### 2. A vote is a timed sitting, not a quorum
+
+Asking *"how many votes must we collect"* produces deadlock — Linz's problem, no
+constitutional exit. We invert it: members are notified that a vote is wanted within a window,
+and **an unvoted window nulls that member's vote** — they drop out of the denominator. They
+are never counted as a no.
+
+**The clock is the deadlock exit.** This is why no shotgun buy-sell or fork-with-treasury-split
+clause is needed at this scale: absence cannot stall anything, so there is no state for such a
+clause to resolve.
+
+Default window: **90 minutes**, closing early the moment every member has voted, so latency is
+`min(full turnout, window)`. Stored in minutes and set per project.
+
+Stated plainly because it is the owner's explicit intent, not an accident: **a short window
+means whoever is awake governs.** Standing accrues to those actively governing. The window
+length is a governance lever, not a UX detail.
+
+### 3. Consent, not majority — and a zero-vote close passes
+
+Silence is consent. A **single reasoned objection** returns the idea to its author. A window
+that closes with **no votes at all passes** — the idea already cleared the completeness gate to
+reach the board, and absence never blocks.
+
+This makes both halves of the owner's intent true at once: pace is never obstructed, and only
+an active participant can change an outcome. It also makes the feedback mechanism in Decision 4
+load-bearing rather than decorative — an objection must carry a reason and a section flag to
+count at all.
+
+Trade-off recorded deliberately: with five members, 4-yes/1-no returns the idea. That is real
+minority-block power. The cost of a wrong objection is one revision cycle, not a kill.
+
+### 4. A rejection carries a reason and one of the five sections — and that forces the surface
+
+A Full Idea that fails, **whether on completeness grade or on the vote**, returns to its
+originator rather than dying or stalling. Every rejection carries free text **plus exactly one
+of the five Full Idea sections** flagged as the cause. A sub-bar grade flags its weakest
+section automatically, using the per-field scores `completeness.js` already computes — which
+also means a resubmission can be checked against the flagged section.
+
+**This requirement is what makes the hall the only possible voting surface.** A Discord
+reaction can express yes or no and nothing else, so reaction-voting would make every
+Discord-cast rejection feedback-free — precisely what this decision exists to prevent. The hall
+is not the *richer* surface; it is the only one that satisfies the rule.
+
+Resubmission is unbounded in v1 — the grade gate already bounds spam — and every past rejection
+stays visible on the item's history.
+
+### 5. The completeness grade is the floor; the vote is the merit
+
+A Full Idea must clear the completeness pass bar (60, ADR 0172-per-craft) before a window can
+open, and a window opens **automatically** on that pass.
+
+Two gates doing two jobs: the deterministic scorer asks *is the thought fully expressed*, the
+board asks *is it worth doing*. Board time is never spent on what a free, reproducible check
+could bounce.
+
+Consequence to design for, and a direct result of automatic opening at a 90-minute default:
+**concurrent windows are normal.**
+
+### 6. Who governs is configuration, and day one is monarchy
+
+The membership predicate, the pass rule, and the window live in `config/government.json`,
+resolved **per request and uncached** so the ADR 0016 instant-demotion property survives.
+
+Day one this instance runs `membership: rank:archon`, `pass_rule: first_ratifier`, no clock —
+**monarchy, expressed as configuration on the real machinery rather than as a separate code
+path.** The board path therefore executes from the first ratification, and flipping the switch
+later changes numbers, not a code path that has never run. The documented recommended starting
+point for a new project is: all Archons, one vote each, consent, 90-minute window.
+
+### 7. Amendments are decided under whatever rule the current constitution names
+
+Changing the constitution is a board subject (Decision 1). It is decided by **whatever rule is
+currently in force** — so under monarchy, "the board must ratify" resolves to "the Archon
+ratifies", and flipping *out* of monarchy is a legal act of the monarchy. Every change after
+that belongs to the board.
+
+**No bootstrap special case is required**, and none should be added. This is how a
+constitution's own amendment procedure normally works, and inventing an exception here would
+create exactly the loophole this ADR exists to close.
+
+### 8. Discord is an outbound notification mirror that casts nothing
+
+On window open, the board channel receives an announcement mentioning the members whose vote is
+wanted, carrying a deep link to that item in the hall. State changes — closed, outcome — are
+mirrored. **Discord reads nothing inbound and casts no vote.**
+
+The mention *is* the "vote within X" notice, and Discord's own mobile app *is* the mobile push
+— **no mobile surface needs to be built.** The bot has no DM capability today, and a channel is
+the better shape regardless: it is a room, it is auditable, and deliberation sits beside the
+vote. Per-rank view access follows ADR 0037.
+
+`modules/discord/discord-approvals.js` (task 1100) is the precedent for **how to broadcast and
+how to re-check a live rank** — *"the bot asserts only who reacted; the GDS decides what they
+may do"* — and explicitly **not** for how to vote, per Decision 4.
+
+### 9. Open ballot
+
+Member, direction, timestamp, and objection reason are visible to all members. A board whose
+votes are invisible cannot constrain anyone, which is the entire purpose of an upward-pointing
+gate. It also makes the vote-karma in Decision 10 auditable.
+
+### 10. Voting earns karma
+
+A small award per vote cast in-window (proposed `+1`); the Full Idea's author earns karma on
+ratification, mirroring `KARMA_RATIFY_DELTA` (`+3` — tuned down from `+5` in V3.R28 / task 248;
+do not copy the stale `+5` still printed in `planning-session/SKILL.md` and `openapi.json`).
+
+**Decided against the recommendation, with the risk accepted knowingly.** Under consent a *yes*
+is one click while a *no* requires a written reason and a section flag, so equal pay for unequal
+effort tilts toward assent. Accepted because **the item volume is too low to farm** — the
+board's only subjects are Full Ideas and constitutional amendments, both rare by construction.
+Revisit if item volume grows; the award is one constant.
+
+### 11. An author may never vote on their own item
+
+Server-side, on the `peer_votes` anti-self precedent (migration 058, `UNIQUE(voter, target)`).
+This is the bright line that keeps ratification from being ceremonial, and it is the one rule
+that survived from a much larger scrutiny mechanism the owner cut.
+
+## Consequences
+
+**Goal 1000067 (IC5, task 1002999) is unblocked by the pass event, and by nothing else.** ADR
+0172-per-craft is explicit that stream 3 *"consumes the Board Room's pass event; invents no
+parallel vote."* There is exactly one vote surface in this system. The event fires once per
+ratified idea and must be idempotent across replays, re-closes, and a resubmission that passes
+again. `economy` is deliberately outside this goal's scope: we emit, 1000067 pays.
+
+**The permission keys must land with their grant migration in the same deploy as the code
+constant.** `government_rank_permissions.permission_key` stores the key as text while
+`catalog.js` holds it as a constant; if the rows change while old code is serving, the check
+fails closed — on the very tab an owner would use to investigate (ADR 0174 §Consequences). The
+grant migration is load-bearing, not bookkeeping: `governance_002` is run-once, so an
+already-migrated database never learns a key added only in code.
+
+**Board state lives in `modules/government/`, which is protected.** All board work is therefore
+Archon-gated. This was chosen over `modules/ideas/` (subject-ownership) on the grounds that the
+board is an authority mechanism. The rename that created that folder landed on `origin/main` in
+`14dcedd`; note that task 1003005 reads `abandoned` but was *absorbed* into 1003004 and shipped
+there — read the note, not the status.
+
+**Goal 1000069 is walled to the `governance` alias, not `government`.** Prod served core
+1.19.179 while the new scope key landed in 1.19.180, so the live server rejected the new key at
+goal-creation time. The alias carries identical globs. **Re-point `scope_modules` once 1.19.180
+is deployed.**
+
+**The charter library ships without the Charter Builder.** The Government page presents all
+seven constitutions, the three trajectories and the ladder thresholds, marking which are
+selectable today. This is the reference half only — the configuration machinery is deliberately
+absent, per the scale argument in Context 3. At two builders this is the half that earns its
+keep, and its stated purpose is getting a team up to speed before deciding when to flip the
+switch.
+
+**The agora auto-link from idea 1000738 is deferred, not dropped.** Linking discussion *in*
+would mean reading Discord inbound, contradicting Decision 8. Once goal 1000064 makes the Agora
+a hall surface, the link is hall→hall and needs no adapter. Filed as idea 1000757.
+
+**Rejected: quadratic vote weighting and the attribution-economy knobs.** The synthesis doc's
+Part V spends its length on meter-weighted franchise — the Solon problem, compressing whales
+with √credits, the drift from timocracy toward isonomia. None of it applies here, because v1's
+franchise is a flat membership rule and is not weighted by credits at all. Hop decay (γ), time
+half-life (τ), the 30% stack cap and vote coupling belong to the ideator credit lane, not to
+this decision.
+
+**Rejected: eternity clauses in v1.** Fork rights with an asset-split rule, meter transparency,
+and a dead-man's switch on founder inactivity are real and worth having — Germany's Basic Law
+Art. 79(3) and MolochDAO's ragequit are the precedents — but nothing in v1 depends on them, and
+an unamendable floor written before the amendable part has ever run would be guesswork.
+
+**Rejected: any legal-entity integration.** Equity issuance, Rev. Proc. 93-27 profit interests,
+Subchapter T patronage, and the Howey posture are a later version's problem. v1 credits stay
+reputation- and governance-weighted only, which is also what keeps the Howey question asleep.

package/docs/adr/README.md

@@ -248,5 +248,6 @@ This keeps the decision history honest and traceable.
 | 0171 | [**Profile ↔ cross-project rollup: the join runs in-process on the hub; consent is fail-closed account state; the hide flag lives on the account, enforced in the read path** ([task 1002277](https://cloudbongos.com/builders#/task/1002277), R01 of goal 1000045). The C1 cross-project profile reads the platform-identity rollup through the module's **declared-but-never-registered `platform-identity.hub` port**: the module registers a real provider and core `GET /builders/:id/profile` `resolveOptional`s it beside `reward` — zero network, `null` (clean degrade) on every non-hub instance. Federated instances **link out** instead of inlining (amends profile-page spec Decision 1: an instance-side copy is either stale-on-hide or a per-view hub call). Consent: `profile_state` on `platform_identity_accounts`, **fail-closed** — `active` iff touched by a hub-session `/sso/authorize` (device-poll/check-in create `provisional`; backfill = all provisional, lazy upgrade; no core-`builders` join — type-unsafe vs `system:*` ids and a module-migration boundary breach), so the P03 owner decision can only ever widen, never claw back. The C2 hide flag is `hide_stats` on the account (NOT per-instance `behavior_prefs`), enforced **inside** the module's read functions — `listScoutingRollup` itself gains the `active AND NOT hide_stats` predicate so the live Metic-floor `/people`+`/scouting` surfaces honor it by construction. Hub profile responses go `no-store` (hide must beat the 60s cache). Publishing is gated on hardening the self-reported rollup (membership-row requirement, rank-vocab validation, disciplines caps, check-in→rollup sequencing). Found + filed: the `LATERAL unnest` fan-out inflating rollup sums (task 1002911), the unreserved `u` slug (task 1002912), the missing platform T&C artifact (task 1002913), criterion amendments (task 1002914). Rejected: instance→hub per-view pull (always-on dependency), hub→instance mirroring (stale-on-hide), storing the flag in builder-settings, backfilling `active` from hub `builders` rows.](<redacted>.md) | platform identity / profiles / privacy |
 | 0170 | [**The featured projection tells time honestly: `created_at` in, `updated_at` out, owner from the project's own archon** ([task 1002778](https://cloudbongos.com/builders#/task/1002778), goal 1000061). The hub card's metadata pass added `created_at` to the public `/projects/featured` projection, labelled **Listed** — it is the moment the hub catalogued the row, never when the project began, and the C6 card test bans the word "Created". Two recorded deviations: (1) the task brief said `updated_at` was ready to add, but the column is bumped by every client re-registration AND the Archon's feature toggle, so as a public "last updated" it would report curation noise as project activity — it may sort, never project, and the test pins the SELECT list itself (`SELECT *` banned: the route is CORS-open rank:public and a star would leak `owner_github_id`/`status`). (2) The owner fact reads the project's OWN leaderboard archon row (login + avatar, type-checked and capped) from the payload project-stats already fetches — zero extra requests, the 2-fetch pin intact, the advisory `owner_github_id` column still unread per the design contract. Multi-archon: top-credits archon is named; a fallen-off-the-page archon renders as no owner shown, never a wrong one. Rejected: projecting `updated_at` as asked (it lies), reading `owner_github_id` (advisory, contract-banned), a third per-origin fetch for activity recency (moves the test pin for a fact nobody asked for yet).](<redacted>.md) | platform identity / public surface |
 | 0174 | [**Governance is renamed government, its positions are ranks, and "role" is reserved for the three crafts** ([task 1003002](https://cloudbongos.com/builders#/task/1003002), R01 of goal 1000068). Owner directive, 2026-08-16. The word **role** named two unrelated things: the permission system's ladder tiers (`governance_roles`, the "rank-roles") and the three crafts (`tasks.discipline` = engineer/artist/ideator) — and goal 1000066 was actively claiming it for the crafts (`three-roles-only`, `users-hold-roles`), putting the two on a collision course. Resolved at full depth rather than as a label pass, because a labels-only fix leaves the UI and the code disagreeing, which is the condition that produced the collision. `modules/governance/` → `modules/government/`; the kernel module key, the config files, `/api/bongos/governance/*` → `/government/*`, and the permission keys `governance.manage` → `government.manage` (~50 sites) + `page.view.governance` → `page.view.government`. **The entity IS the rank — no second noun**: `governance_roles` → `government_ranks`, `role_key` → `rank_key`, `rank-roles.js` → `ranks.js`; "position" stays prose-only, since introducing it as a code term would recreate the qualifier problem "rank-role" already demonstrates. The cross-module kernel port `governance.roleSync` → `government.rankSync` must land atomically across its provider and both consumers (`modules/lifecycle/db.js`, `src/bongos/db.js`) because it is a transaction participant on the rank-write path. Hand-composed bundles stay in the one table as **custom ranks** — the owner's call over splitting them into a separate "appointments" concept, with the objection recorded (a custom bundle is not a ladder position, and ADR 0172 §4 already treats the two kinds as different). Enforced by a `fitness.js` rule, allowlist shipped with reasons. **Discord's server roles keep the word** — that noun belongs to Discord's API. Amends ADR 0151 + ADR 0172 (the editable-rank-roles one) in **vocabulary only**; ladder slugs, `builders.rank`, `requireRank`, and every floor/grant/assignment semantic are untouched. Rejected: renaming the ladder slugs (turns a bounded rename into a trust-boundary migration), a permanent compat shim (both vocabularies stay correct forever).](<redacted>.md) | government / permissions |
+| 0175 | [**The Board Room: Full Idea ratification is the first upward-pointing gate** ([task 1003014](https://cloudbongos.com/builders#/task/1003014), R01 of goal 1000069). Every existing gate points DOWN the rank ladder; the owner asked for one that could slow THEM down — *"otherwise I can just ship and build as I want, finding loopholes."* The board's subjects are exactly **two**, both rare by construction: a **Full Idea** and a **change to the constitution itself** (`subject_type` from day one). Because the vote gates no build path, the **ADR 0162 tension dissolves rather than being compromised** — nothing self-executes because there is nothing downstream to execute; ratification confers legitimacy and does NOT auto-create the goal. A vote is a **timed sitting, not a quorum**: absent members are *nulled* (dropped from the denominator, never counted as a no), so the clock is the deadlock exit and no shotgun/fork-with-treasury clause is needed at this scale — default 90 minutes, closing early on full turnout, and yes, a short window means whoever is awake governs (the owner's explicit intent). **Consent, not majority**: silence is consent, one reasoned objection returns the idea, and a zero-vote close PASSES. A rejection must carry free text **plus one of the five Full Idea sections** — which is what **forces the hall to be the voting surface**, since a Discord reaction could only ever be feedback-free; Discord is therefore an outbound notification mirror that casts nothing, and its own mobile app is the mobile push (no mobile surface is built). The completeness grade is the **floor** (a window opens automatically on pass), the vote is the **merit**; concurrent windows are normal. Who governs is **configuration** — day one is monarchy expressed as config on the real machinery, never a separate code path — and **amendments are decided under whatever rule is currently in force**, so flipping out of monarchy is a legal monarchy act and no bootstrap exception is needed. Open ballot; an author may never vote on their own item. Franchise derives from **rank, not role**, and that is forced: `PATCH /me/disciplines` is deliberately ungated, so a craft-scoped chamber would be one-request privilege escalation. Unblocks goal 1000067 / IC5, which consumes the pass event and *"invents no parallel vote"*. Rejected: quadratic vote weighting and the attribution-economy knobs (γ, τ, the 30% stack cap — v1's franchise is not credit-weighted at all), eternity clauses, and any legal-entity integration.](<redacted>.md) | government / ideas / governance |
 
 > ⚠️ **Numbering collision (known):** two ADRs share `0008`. The numbers were assigned in parallel sessions before the lock could be enforced. The files are kept under their existing filenames to preserve git history, but the table disambiguates them as `0008-a` / `0008-b`. New ADRs should resume at `0040` to avoid further collisions. (`0024` is also a real on-disk duplicate: the cloneable-repo/local-first-memory ADR and the multi-agent-system-architecture ADR were both numbered `0024` in parallel; both keep their filenames, disambiguated as `0024-a` / `0024-b` like `0008`. Likewise `0025` ended up with two on-disk files — the offsite-backup ADR and the structured-criterion↔task-link ADR — both kept under their existing filenames and disambiguated as `0025-a` / `0025-b`; separately, the BFG ADR had also claimed `0025` on 2026-05-30 and yielded to `0026`. A third happened 2026-06-06: `0036` was claimed in parallel by the builders-subdomain ADR ([#726](https://example.com/builders#/task/726)) and this Discord-channels ADR ([#727](https://example.com/builders#/task/727)); the Discord-channels ADR yielded to `0037`. A fourth landed 2026-06-10: `0044` was claimed in parallel by the palette-replacement ADR and the per-box game-preview ADR ([#897](https://example.com/builders#/task/897)); both keep their filenames, disambiguated as `0044-a` / `0044-b` like `0008`. A fifth was caught pre-land 2026-06-13: `0050` was claimed in parallel by the device-flow-admission ADR ([#1000](https://example.com/builders#/task/1000)) and the sandbox-for-everyone ADR ([#1001](https://example.com/builders#/task/1001)); the latter yielded to `0052` before merging, so there is no `0050` duplicate. A sixth was caught pre-land 2026-06-21: the tool-agnostic-design-layer ADR ([#1375](https://example.com/builders#/task/1375)) first collided at `0079` with the value-gated-autonomous-engagement ADR, then at `0080` with the llm-cache-api-transport ADR (both part of the 0075–0080 LLM-cost-reduction series, landed on `main` in parallel); it yielded to `0081` before merging, so there is no `0079`/`0080` design-layer duplicate. A seventh landed 2026-06-23: `0084` was claimed in parallel by the auto-derived-per-task-rank-floor ADR and the remove-default-spend-cap ADR (task 1499); the rank-floor ADR landed on `main` first, so the spend-cap ADR yielded to `0085`, leaving no `0084` duplicate. An eighth landed 2026-06-27: `0095` was claimed in parallel by the borrowed-memory-and-retrieval-concepts ADR (PR #459, landed first) and the cross-agent-context-management ADR ([#1651](https://example.com/builders#/task/1651), PR #460); both keep their filenames, disambiguated as `0095-a` / `0095-b` like `0008`. These two are companions — `0095-a` adopts the memory/retrieval concepts and explicitly defers the grep-vs-semantic question to `0095-b`.)

package/package-lock.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bongos/core",
-  "version": "1.19.188",
+  "version": "1.19.189",
   "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

@@ -803,8 +803,10 @@ const { validateOrRespond, LIMITS, parseId, asyncHandler, corsPublicGet, parsePa
 //         landed since 1.19.186 with no explicit bump. run 31978548058. (task 1002620)
 //   1.19.188 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
 //         landed since 1.19.187 with no explicit bump. run 31978931152. (task 1002620)
+//   1.19.189 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+//         landed since 1.19.188 with no explicit bump. run 31983108640. (task 1002620)
 // ---------------------------------------------------------------------------
-const CORE_VERSION = '1.19.188'; // CI auto-patch carrier (ADR 0161); see changelog above
+const CORE_VERSION = '1.19.189'; // CI auto-patch carrier (ADR 0161); see changelog above
 
 // A namespaced logger so a module's log lines are attributable + consistent.
 // Usage: const log = api.logger('dev-box'); log.info('mounted');