@bongos/core 1.19.610 → 1.19.611

package/.bongos-core.json

@@ -2,11 +2,11 @@
   "artifact": "bongos-core",
   "manifest_schema": 1,
   "generator": "scripts/gds/package-core.js",
-  "core_version": "1.19.610",
-  "core_contract": "1.19.610",
-  "source_commit": "4c1f1badb5d2b5fa83e5968be5fa1e1f55d93e2b",
+  "core_version": "1.19.611",
+  "core_contract": "1.19.611",
+  "source_commit": "2fe1716bf46fd008eb614d9fb317b0e9ee2874eb",
   "source_ref": "HEAD",
-  "built_at": "2026-09-09T02:54:17.395Z",
+  "built_at": "2026-09-09T03:07:36.926Z",
   "redaction": {
     "model": "docs-redacted+functional-verbatim",
     "docs_redacted": 458,
@@ -17,7 +17,7 @@
     "gate": "passed"
   },
   "file_count": 2562,
-  "tree_sha256": "d2202f52c9a79a7724caf58530643f0d415692205c8ba79f0bcf84bf52efe99c",
+  "tree_sha256": "c6a3113ed2f20af25a3ebcaee8cb4ff9cd42890d51e890a85c31ddf9d63ff5ea",
   "files": [
     {
       "path": ".claude/skills/blocker-review/SKILL.md",
@@ -1837,7 +1837,7 @@
     {
       "path": "docs/adr/0264-the-ten-working-areas.md",
       "mode": "0000644",
-      "sha256": "f87933b29006e445dd6d5e4861ce73648f2cc774daacf47ad890f5ae97738e60"
+      "sha256": "b6127318d595f9885dbf6c42c1567c926f45200df2e2144dd2bbce9313e67d91"
     },
     {
       "path": "docs/adr/0265-work-with-no-goal-and-the-order-the-cut-needs.md",
@@ -2732,7 +2732,7 @@
     {
       "path": "docs/module-api-changelog.md",
       "mode": "0000644",
-      "sha256": "a0d2f5cc61592667c0aee1a2c8f91de5818664c949c3b5d25b63e4dea6fa13d6"
+      "sha256": "4cc20b3afc8ec94a1d53e3d3f746269a1a7def4b6798d81402fe9078c002d3b1"
     },
     {
       "path": "docs/modules-contract.md",
@@ -7632,12 +7632,12 @@
     {
       "path": "package-lock.json",
       "mode": "0000644",
-      "sha256": "e7585d9eda4e8d1c31e482b906b057faea09a6ce9762fe2f2a3291645cc05006"
+      "sha256": "73ce6d69717b6ed9e4cf704e12b5578a86a5a9d34baaa1df34df7caa5accbedb"
     },
     {
       "path": "package.json",
       "mode": "0000644",
-      "sha256": "d9b8d44d792bded0ba975222aaeea57e61d9f55c065c872e419e699306b9111f"
+      "sha256": "5ac0729891d64cd779f810b1bf4f98997a7dd8756c8baaa9d82577c7e7e29b60"
     },
     {
       "path": "public-docs/index.html",
@@ -9362,7 +9362,7 @@
     {
       "path": "src/module-api.js",
       "mode": "0000644",
-      "sha256": "ae1fb8dbae19e0cb39080790c1b71ad57db3249fed69cce4e633e537c1ae5269"
+      "sha256": "790abd4adb2065c87aa21a729b69b33d01ed07be1c5c307a865f2f8942cc9d3f"
     },
     {
       "path": "src/module-loader/catalog.js",

package/docs/adr/0264-the-ten-working-areas.md

@@ -170,3 +170,30 @@ Also folded, where §3 named no destination: [#1000032](https://cloudbongos.com/
 ### One correction to the execution plan, for whoever closes BONGOS-V2
 
 `roll_forward` **does not carry a goal's done-when criteria** — the successor `INSERT` in [db-versions.js](../../modules/lifecycle/db-versions.js) copies prose, scope, membership and category, and nothing in the close path touches `done_when_criteria`. The pre-execution plan predicted this would drive invariant C4 to 7/27. **It did not**, because the same transaction promotes the planning version to `building` and C4 only measures a planning version — so the criterion-less successors were never counted. The substance still matters even though the invariant stayed green: a successor arrives unable to achieve, and only the fold (which archives it) or a hand-written criterion resolves that.
+
+## 7. The names in §1, mapped to accounts — 2026-09-08
+
+§1 names owners as people; the database knows accounts, and until now nothing wrote
+down which was which. Recorded under [#1003729](https://cloudbongos.com/builders#/task/1003729). The map is evidenced from goal
+membership rather than inferred from spelling — a name that merely *looks* like a login
+is not a match.
+
+| §1 name | Account | How it was established |
+|---|---|---|
+| Rini | `jaxri` (1000095) | Sole **lead** of area 2, which §1 gives to Rini; also a member of area 1, Rini's other area. |
+| Will | `willHermesLines` (1000027) | **Lead** of area 5; member of areas 4 and 10 — the three areas §1 names him in. |
+| Masterqua | `IAMMASTERQUA` (1000025) | Member of areas 7 and 10, both of which name Masterqua. |
+| Lars | `example-owner` (3) | The owner; lead on every area. |
+| Scott | `scootermack` (1000094) | **Owner decision, 2026-09-08.** Two accounts existed — `scootermack` (archon, already a member of area 1) and `scottymccormack` (1000160, xenos, no membership anywhere). Now **lead of areas 3 and 8**, which §1 gives to Scott and which previously carried no membership for him. |
+| Nils | — | **Unmapped.** No roster account matches. |
+| Niels | — | **Unmapped.** §3 says "Niels finishes" the rename; those five tasks carry no assignee (tasks have no assignee field — only `shipped_by`, and they are unshipped). |
+
+**§1 spells the name two ways** — "Nils" in area 10's owner line, "Niels" in §3's rename
+note. Whether that is one person or two is not derivable from the data, and neither
+spelling matches any of the fifteen roster accounts. Worth resolving before anything
+relies on area 10's "all except Nils and Scott".
+
+**An owner in prose is not an owner in the database.** §1's owner column, and the
+`Owner:` line in each area's done-when criterion, are text — they grant nothing and are
+read by no gate. The load-bearing record is `goal_members`, which is why areas 3 and 8
+could read as owned while holding no membership for their owner at all.

package/docs/module-api-changelog.md

@@ -1669,5 +1669,7 @@ is load-bearing: the script throws rather than guess if it is missing, and
         landed since 1.19.608 with no explicit bump. run 34297289824. (task 1002620)
   1.19.610 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
         landed since 1.19.609 with no explicit bump. run 34305007041. (task 1002620)
+  1.19.611 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.19.610 with no explicit bump. run 34305857169. (task 1002620)
 ---------------------------------------------------------------------------
 ```

package/package-lock.json

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

package/package.json

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

@@ -55,7 +55,7 @@ const { buildInfo } = require('./build-info');
 // 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.610'; // CI auto-patch carrier (ADR 0161); changelog: docs/module-api-changelog.md
+const CORE_VERSION = '1.19.611'; // 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');