@bongos/core 1.19.701 → 1.19.702

package/.bongos-core.json

@@ -2,11 +2,11 @@
   "artifact": "bongos-core",
   "manifest_schema": 1,
   "generator": "scripts/gds/package-core.js",
-  "core_version": "1.19.701",
-  "core_contract": "1.19.701",
-  "source_commit": "6c01baa69654043099e16c9bf0353eff61d2012d",
+  "core_version": "1.19.702",
+  "core_contract": "1.19.702",
+  "source_commit": "3b1a2e8029758a6ee091812baccb9e24fdc4670a",
   "source_ref": "HEAD",
-  "built_at": "2026-09-13T03:22:47.893Z",
+  "built_at": "2026-09-13T03:33:51.903Z",
   "redaction": {
     "model": "docs-redacted+functional-verbatim",
     "docs_redacted": 477,
@@ -17,7 +17,7 @@
     "gate": "passed"
   },
   "file_count": 2631,
-  "tree_sha256": "640bb539971ad78a750aa80116d26c7f1f81fc1b2afb21ef0fd33855189fe10a",
+  "tree_sha256": "7bf1dff3812c90015cc9d2476643856d5c6e9e950d26c6859e219c0eab9796b5",
   "files": [
     {
       "path": ".claude/skills/ask-for-help/SKILL.md",
@@ -227,7 +227,7 @@
     {
       "path": ".claude/skills/planning-session/SKILL.md",
       "mode": "0000644",
-      "sha256": "2cb49f8643cf49664c1b9371e7ca4bce605eaa58c1806a32d3c98dcb517c3ad9"
+      "sha256": "701d484d1ae558257d0f319d9b684b242294f24602e98186b8c19ffa58459711"
     },
     {
       "path": ".claude/skills/priority-session/SKILL.md",
@@ -2802,7 +2802,7 @@
     {
       "path": "docs/module-api-changelog.md",
       "mode": "0000644",
-      "sha256": "4fc39aaaae76afb8153485474fc9f3459a2ee380b96f59d1d693a4a7680db464"
+      "sha256": "7458093aecd8dd3fcc7753356a12e995b25663e9251a295c406e4ecc4cc54c27"
     },
     {
       "path": "docs/modules-contract.md",
@@ -7782,12 +7782,12 @@
     {
       "path": "package-lock.json",
       "mode": "0000644",
-      "sha256": "f7fb304e4955f8024186863281f2540c2e92299e49b16f7f6ea0f78c6d46d22a"
+      "sha256": "1aa096840e001b544038432419a0e07577014954f7cb83d8e19c716704e3f36c"
     },
     {
       "path": "package.json",
       "mode": "0000644",
-      "sha256": "be0e756de883b5e3291f721efe8515540771994df5d83f0eb96bd07f87ecf1e8"
+      "sha256": "cee79b868fecce6053d7d04108233e795a92c3635854bea1bf3003b909953e20"
     },
     {
       "path": "public-docs/index.html",
@@ -9552,7 +9552,7 @@
     {
       "path": "src/module-api.js",
       "mode": "0000644",
-      "sha256": "2fdd8c72769bba600991d5c886878c7390ef2086f67ad8c1036555e45631a971"
+      "sha256": "be1bd4054da76be7eb7aa62d3e9ee2805de116d811e25043a49bbd4731ad1643"
     },
     {
       "path": "src/module-loader/catalog.js",
@@ -11912,7 +11912,7 @@
     {
       "path": "tests/planning_session_skill.mjs",
       "mode": "0000644",
-      "sha256": "1f2d52192e96bc1f2693a4b1a8458bc0f533e9c971c9ac42d9199e11d01eec48"
+      "sha256": "bdf3a2d275c6f40fd1c3b8fbb16f39724227496ce8e38b89b408384610d3df7e"
     },
     {
       "path": "tests/platform_boot.mjs",

package/.claude/skills/planning-session/SKILL.md

@@ -279,12 +279,35 @@ Once the spec is finalized (Phase 4), **read `docs/specs/<ver>-<goal-slug>.md` a
 
 5. **Run the seed script.** Verify exit code 0 — the seed's own final step (the Seeding contract's `verifySeedCriteriaLinks` call, above) already fails loudly if any criterion's linked task count doesn't match the plan, so a 0 exit means the links landed correctly, not just that the POSTs didn't error. Also spot-check totals via `GET /api/gds/public/progress` and `GET /api/gds/versions/<ver>/done-when`.
 
-6. **Promote the zero-dep layer to `ready`.** Every newly-seeded task lands `status='backlog'`. The auto-promotion trigger only fires when a *dependency* ships — so a task with zero deps has nothing to wait for and would sit unclaimable forever. Run, in the same psql session as the migration (or via SSH to the droplet):
+6. **Promote the zero-dep layer to `ready` — scoped to the tasks you just seeded.** Every newly-seeded task lands `status='backlog'`. The auto-promotion trigger only fires when a *dependency* ships — so a task with zero deps has nothing to wait for and would sit unclaimable forever.
+
+   **Scope this to your own seed, and never to the whole version** (task 1001438). `version_id + status='backlog' + kind<>'spike' + no dep edge` also describes rows that are sitting at `backlog` **on purpose**, and promoting those is a silent, unlogged override of another subsystem's decision:
+   - **cascade-filed tasks** — `cascade.js` files generated work at `backlog`, **never** `ready`, as one of its four pinned properties (`modules/lifecycle/CLAUDE.md`; task 1003549). A cascade task has no dependency edge, so an unscoped promote flips exactly the rows that guarantee says it never will.
+   - **restored tasks** — `POST /tasks/:id/promote` → `db.restoreTask` returns an abandoned task to `backlog` so a human re-scopes the dead edge deliberately (owner ruling 2026-08-21, ADR-backed in `modules/lifecycle/CLAUDE.md`). Promoting it straight to `ready` is the "silently release work built on something that was never built" outcome that ruling forbids.
+
+   Both are ordinary carry-overs in any version that has been live for a while, so the blast radius grows the longer an instance runs.
+
+   Every seed script POSTs with `source: 'planning-session'` and a per-seed `source_ref` prefix (see `scripts/gds/<redacted>.js`), which is the handle to scope by — it needs no id transcription and cannot drift from what the seed actually created. **Dry-run the SELECT first and read the rows**, in the same psql session as the migration (or via SSH to the droplet):
+
+   ```sql
+   SELECT id, title, priority, kind
+   FROM tasks
+   WHERE version_id = '<ver>'
+     AND source = 'planning-session'
+     AND source_ref LIKE '<seed-ref-prefix>-%'
+     AND status = 'backlog'
+     AND kind <> 'spike'
+     AND id NOT IN (SELECT task_id FROM task_dependencies);
+   ```
+
+   The count must match the zero-dep tasks your seed script just created. If it is larger, your `source_ref` prefix is catching an earlier seed — narrow it (or fall back to the explicit list, `AND id = ANY('{<seeded ids>}')`) before writing anything. Then re-run it as the UPDATE:
 
    ```sql
    UPDATE tasks
    SET status = 'ready', promoted_at = now()
    WHERE version_id = '<ver>'
+     AND source = 'planning-session'
+     AND source_ref LIKE '<seed-ref-prefix>-%'
      AND status = 'backlog'
      AND kind <> 'spike'
      AND id NOT IN (SELECT task_id FROM task_dependencies)

package/docs/module-api-changelog.md

@@ -1861,5 +1861,7 @@ is load-bearing: the script throws rather than guess if it is missing, and
         landed since 1.19.699 with no explicit bump. run 34735048203. (task 1002620)
   1.19.701 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
         landed since 1.19.700 with no explicit bump. run 34735311256. (task 1002620)
+  1.19.702 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.19.701 with no explicit bump. run 34735775228. (task 1002620)
 ---------------------------------------------------------------------------
 ```

package/package-lock.json

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

package/package.json

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

@@ -71,7 +71,7 @@ const { responsibilityFor, ROLE_RESPONSIBILITIES } = require('./role-responsibil
 // 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.701'; // CI auto-patch carrier (ADR 0161); changelog: docs/module-api-changelog.md
+const CORE_VERSION = '1.19.702'; // 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');

package/tests/planning_session_skill.mjs

@@ -91,5 +91,48 @@ test('the step is scoped to process-change sessions, not every planning session'
   assert.ok(/skip/i.test(section), 'says explicitly when to skip it');
 });
 
+// --- task 1001438: the Phase 5 promote must be scoped to the seeded set -----
+// The bug was an UPDATE filtered only by version_id + backlog + non-spike +
+// zero-dep. That predicate also describes rows parked at `backlog` ON PURPOSE —
+// cascade.js files generated work at backlog and never ready (one of its four
+// pinned properties), and db-ship.js restoreTask returns an abandoned task to
+// backlog so a human re-scopes the dead edge. Neither carries a dependency edge,
+// so an unscoped promote silently overrides both. These pin the scoping so the
+// narrowing cannot be dropped back out during a later edit of this step.
+
+function promoteStep() {
+  const start = NORM.indexOf('Promote the zero-dep layer');
+  assert.notEqual(start, -1, 'the Phase 5 promote step must still exist');
+  const end = NORM.indexOf('Surface higher-priority spikes', start);
+  return NORM.slice(start, end === -1 ? undefined : end);
+}
+
+test('the Phase 5 promote is scoped to the seeded set, not the whole version', () => {
+  const step = promoteStep();
+  // Either handle is acceptable — the source_ref prefix (no id transcription) or
+  // the explicit id list the row originally proposed.
+  assert.ok(
+    step.includes('source_ref LIKE') || step.includes("id = ANY('{"),
+    'the promote must carry a seed-scoped predicate, not version_id alone',
+  );
+  assert.ok(step.includes("source = 'planning-session'"), 'names the seed source it scopes by');
+});
+
+test('the promote step says WHY scoping matters, naming both kinds of deliberate backlog row', () => {
+  const step = promoteStep();
+  assert.ok(/cascade/i.test(step), 'names cascade-filed tasks');
+  assert.ok(/restore/i.test(step), 'names restored (formerly abandoned) tasks');
+  // A reader who only sees "scope it" will widen it again the first time the
+  // narrow filter is inconvenient. The reason is the durable half.
+  assert.ok(/on purpose|deliberate/i.test(step), 'says these rows sit at backlog deliberately');
+});
+
+test('the operator is told to dry-run the SELECT before the UPDATE', () => {
+  const step = promoteStep();
+  assert.ok(/SELECT id, title, priority, kind/.test(step), 'a read-only form of the query is shown first');
+  assert.ok(/dry-run/i.test(step), 'labels it as a dry run');
+  assert.ok(step.indexOf('SELECT id, title') < step.indexOf('UPDATE tasks'), 'the SELECT comes before the UPDATE');
+});
+
 console.log(`\nplanning_session_skill: ${passed} passed, ${failed} failed`);
 if (failed > 0) process.exit(1);