@bongos/core 1.19.292 → 1.19.294

package/.bongos-core.json

@@ -2,22 +2,22 @@
   "artifact": "bongos-core",
   "manifest_schema": 1,
   "generator": "scripts/gds/package-core.js",
-  "core_version": "1.19.292",
-  "core_contract": "1.19.292",
-  "source_commit": "57bc876c876c64bf07069a3646e253006a917fc6",
+  "core_version": "1.19.294",
+  "core_contract": "1.19.294",
+  "source_commit": "fffe6738492ac7d113228cc4f9b1d5eae0ed16d3",
   "source_ref": "HEAD",
-  "built_at": "2026-08-22T15:49:03.336Z",
+  "built_at": "2026-08-22T17:51:40.637Z",
   "redaction": {
     "model": "docs-redacted+functional-verbatim",
-    "docs_redacted": 320,
+    "docs_redacted": 321,
     "agent_docs_stubbed": 22,
-    "functional_verbatim": 1391,
+    "functional_verbatim": 1395,
     "rules": 3,
     "gate_literals": 3,
     "gate": "passed"
   },
-  "file_count": 1733,
-  "tree_sha256": "ca47008669375b8c24cbecd5f6142a05b189fce9c02e8c3d2bdc29a2da237f87",
+  "file_count": 1738,
+  "tree_sha256": "70e835883854335f17289f54d647911185cfc4cfb1ec5b17424a88e6bbd8156f",
   "files": [
     {
       "path": ".claude/skills/blocker-review/SKILL.md",
@@ -1399,20 +1399,25 @@
       "mode": "0000644",
       "sha256": "e7d0245b21406ddcd118dce29ffb1df5a4797e33d66231aa6bc734316c19530f"
     },
+    {
+      "path": "docs/adr/0184-ship-requires-an-assurance.md",
+      "mode": "0000644",
+      "sha256": "d68cae6169d7ef251fdf6c721e63a124bd3bf46979ffa51459db435426d24f8b"
+    },
     {
       "path": "docs/adr/README.md",
       "mode": "0000644",
-      "sha256": "5e8bcc7eff0a9940760952e4dffe3855474e506439d677625f411164ae226a35"
+      "sha256": "0eafe881d241706331548cf8212c5e84f2f42167c2ac5688427820fa394d77ef"
     },
     {
       "path": "docs/api-reference.md",
       "mode": "0000644",
-      "sha256": "2c4a9b56aea5a8e1a42c70ad5c2646c0d6db6d713c13b8d2068bd3a2fa6ac27e"
+      "sha256": "8fb83f272ef8810df2c517d9514495f44016da2e23cdd67937463f40c0d1605d"
     },
     {
       "path": "docs/api/openapi.json",
       "mode": "0000644",
-      "sha256": "fcb40a7d655517e6dd24b2d4e0e00a9fcace75b2eb0aa89348d2546abf8df422"
+      "sha256": "f51be43a281c9609980fca57d2fa11cafb460a414e506174715d53c08cef6965"
     },
     {
       "path": "docs/architecture.md",
@@ -3777,7 +3782,7 @@
     {
       "path": "modules/lifecycle/db.js",
       "mode": "0000644",
-      "sha256": "18b2053d9195936be86d98e00812ab69980986f91cf83bc9db054441036192fd"
+      "sha256": "f4d3df748f39109c775ae167712926cd44832aba0651251f508adc4a8d4e57fe"
     },
     {
       "path": "modules/lifecycle/dead-deps.js",
@@ -3862,7 +3867,7 @@
     {
       "path": "modules/lifecycle/publish-reconciler.js",
       "mode": "0000644",
-      "sha256": "900fc9ecfe91a0c1e9cd62b619f609c1416196d502c007d0bbb87c41387b6163"
+      "sha256": "8f08c6d58db41ba247aaf5b04b5a8988365b469e96c0ad04c336f272ef308c4e"
     },
     {
       "path": "modules/lifecycle/routes/analytics.js",
@@ -3902,13 +3907,18 @@
     {
       "path": "modules/lifecycle/routes/tasks.js",
       "mode": "0000644",
-      "sha256": "0600b76953e28b2c5828301606c72e2490756d43a2eb74b4bc92dca9d795cb77"
+      "sha256": "3dbbf03588eb70c3d84b1d98f1e7a94a2c7bd0612d4835bd0fe1cc0470b802b4"
     },
     {
       "path": "modules/lifecycle/routes/versions.js",
       "mode": "0000644",
       "sha256": "044ca86e5605c19dd8e523da9eb061b4a90ed0af199ec1288c3c5f1b1bb8f46b"
     },
+    {
+      "path": "modules/lifecycle/ship-assurance.js",
+      "mode": "0000644",
+      "sha256": "2938d8ea651af09b3c73d294057c153ce079170ae34a42e3e94025daab097dcf"
+    },
     {
       "path": "modules/lifecycle/ship-card.js",
       "mode": "0000644",
@@ -4527,12 +4537,12 @@
     {
       "path": "package-lock.json",
       "mode": "0000644",
-      "sha256": "417cc856bf6eca0ed8c214b12624c6bc7567bb96b07a5999ebf5b72ab6b4ca05"
+      "sha256": "4555259c80ad21945412441d859ab9ff5f68be5adb28d7c02b2d405b42339398"
     },
     {
       "path": "package.json",
       "mode": "0000644",
-      "sha256": "06e136123405fad423973fd79250b7baae689b122c0975e41f369ae87cdfe9e9"
+      "sha256": "26ce6a3328f57b80487d9b5fd31db9cb1c200c93d8f5ec307f763b39e8b28e6e"
     },
     {
       "path": "public-docs/index.html",
@@ -5732,7 +5742,7 @@
     {
       "path": "scripts/gds/ship.js",
       "mode": "0000644",
-      "sha256": "542d36dfe7dd25d20936844b237b6681b1e64d34c66448438cf7ef9d86abb79f"
+      "sha256": "73c2e91340171d6a9112e869552be17e0f82aeb80a5c680205ac452d34c3ddc4"
     },
     {
       "path": "scripts/gds/smoke-batch-claim.sh",
@@ -5779,6 +5789,11 @@
       "mode": "0000644",
       "sha256": "5cc69c5f3301912325aa48481e63141523ad75241f021e0e8f1a6dc592048bdd"
     },
+    {
+      "path": "scripts/gds/strand-watch.js",
+      "mode": "0000644",
+      "sha256": "abcf87286fa3b3be81c18e5927495f64c140322a83223c4dc673d8325c08121f"
+    },
     {
       "path": "scripts/gds/task.js",
       "mode": "0000644",
@@ -6177,7 +6192,7 @@
     {
       "path": "src/module-api.js",
       "mode": "0000644",
-      "sha256": "a00525dccc2576669f8793418e40f7232dd2f8662163900142b561ce3c93a2db"
+      "sha256": "ea4af468628d2a5b45ee1e1916622975f263fc4059cff13a49cadb898f35a4db"
     },
     {
       "path": "src/module-loader/catalog.js",
@@ -7867,7 +7882,7 @@
     {
       "path": "tests/orphaned_claim_ship.mjs",
       "mode": "0000644",
-      "sha256": "ecc09c00cc35a2a77bb8a2519332ee3da5b8a5ed8e580e5b21eb4ca43f12a10b"
+      "sha256": "a67dd7e828196929e1fdcdc6cf09255aa583c2013b30632ad8eb847cc6ff5d3b"
     },
     {
       "path": "tests/override_attribution.mjs",
@@ -7907,7 +7922,7 @@
     {
       "path": "tests/pay_on_land.mjs",
       "mode": "0000644",
-      "sha256": "f5ff4080073fa5e6b8d764860dc677b6e617b7b055c2233047163e9c0ed66ce9"
+      "sha256": "6c623a5abe9aadf4821ad8ca291fb5d7805a7a5bc874bfc3cd7e51e83de289d2"
     },
     {
       "path": "tests/permission_path.mjs",
@@ -8344,6 +8359,11 @@
       "mode": "0000644",
       "sha256": "57afd052aaf40ac487d53bf6850710e43c79babaeaa1859374fcc5d8200d92c2"
     },
+    {
+      "path": "tests/ship_assurance.mjs",
+      "mode": "0000644",
+      "sha256": "6fc882d215ce78f968b25477db8596ea70a28765fd222b8a9ffca331e7f2827c"
+    },
     {
       "path": "tests/ship_autolinkify.mjs",
       "mode": "0000644",
@@ -8519,6 +8539,11 @@
       "mode": "0000644",
       "sha256": "2ddc5ada648e7eabb41d3ae0afd39f885f3840c8ec14483f83330e8eade11330"
     },
+    {
+      "path": "tests/strand_watch.mjs",
+      "mode": "0000644",
+      "sha256": "bba2bde5b7a4a25ccddff58fb2fde0ef84ef67224e63819232221a461234a30f"
+    },
     {
       "path": "tests/streak.mjs",
       "mode": "0000644",

package/docs/adr/0184-ship-requires-an-assurance.md

@@ -0,0 +1,106 @@
+# 0184 — A ship must account for itself: `shipTask` requires a land proof or a declared no-artifact
+
+- **Status:** Accepted
+- **Date:** 2026-08-19
+- **Tasks:** [#1002483](https://cloudbongos.com/builders#/task/1002483) (goal 1000024, build-pipeline integrity). Carried forward from blocker 1000047
+- **Extends:** [ADR 0120](<redacted>.md) — pay on land. This makes "land" checkable at the write.
+- **Related:** ADR 0055 (server-mediated publish), 0137 (land → release → deploy are three gates), 0082 (generated-file conflict resolver); tasks 1313 / 1547 / 1002615 / 1002724 (the per-task land proof), [#1002478](https://cloudbongos.com/builders#/task/1002478) (the no-artifact dead end)
+
+## Context
+
+`db.shipTask` is the confirmed→shipped flip. Since ADR 0120 it is also **where the credit is booked**.
+Its only precondition was:
+
+```sql
+UPDATE tasks SET status = 'shipped' … WHERE id = $1 AND status = 'confirmed'
+```
+
+Nothing about whether any code reached `main`.
+
+The two **automated** paths each proved the land before calling it — the reconciler sweep and
+reconcile-on-read both run `landProvenForTask` and refuse without a proof. The **manual** route,
+`POST /tasks/:id/ship`, called `shipTask` with nothing. It is `requireBuilder` +
+`gateTaskOwnership(allowSupervisor: true)`, so a task confirmed with no pushed code could be flipped
+to shipped by its claim holder, or by **any Metic+ running `/merge-mode`**, and it would book its
+`task.shipped` credit.
+
+Blast radius was genuinely small — it takes two deliberate steps, the automated healers refuse, and
+ADR 0120 made strands loud and gated the builder's next claims. That is exactly why it kept being
+deferred. **And why it needed a decision rather than another deferral:** it had resurfaced as a
+blocker repeatedly, and its tracking task ([#1000900](https://cloudbongos.com/builders#/task/1000900))
+was closed in June on a rationale asserting task 1001547 had delivered a confirm-time gate. It had
+not — blocker 1000047's own final update says so explicitly, and the code agreed with the blocker, not
+with the closure note. So the hole was untracked for two months **because a record was wrong**, which
+is the same failure this ADR's gate is about: a ledger entry nobody could check.
+
+## Decision
+
+### 1. The gate lives at the WRITE, not at the route
+
+`shipTask` requires a `landAssurance` and is **fail-closed** — no assurance, no ship, thrown before
+any pool use.
+
+Gating only `POST /tasks/:id/ship` was the cheaper option and was rejected: it leaves the invariant
+unenforced at the layer that actually moves the ledger, so the next caller added anywhere reopens it
+silently. There are three call sites today; the point is that there is no way to add a fourth that
+ships without accounting for it.
+
+### 2. Two kinds, and the second one is why this doesn't make things worse
+
+```
+proof        the caller verified THIS task's own commit is on main
+no_artifact  a deliberate DB-only ship, declared and recorded
+```
+
+A no-artifact ship is an **explicitly supported shape** — CLAUDE.md's "Direct DB writes are work too"
+— and task 1002478 documents that it is already a dead end below Archon. A naive land-proof gate would
+have made that strictly worse, which 1002483 warned about in as many words: *solve them together or
+they will fight.*
+
+Naming `no_artifact` as a **kind** is the resolution. A DB-only ship stops being an absence the gate
+has to be talked out of and becomes a recorded answer: the builder declares it, says what was
+delivered, and the ledger keeps both. That is a small step toward 1002478 rather than away from it.
+
+### 3. Every assurance carries a reason, and the reason is audited
+
+Both kinds require non-empty prose, capped at 500 characters, written to `audit_log` after the
+transaction commits. The ledger should say **why** a ship was allowed, not merely that it happened —
+which is precisely what was missing when this hole went unnoticed.
+
+The audit write is post-commit and best-effort by construction (`insertAuditLog` uses the module pool,
+not the transaction's client). An audit miss must never roll back a landed ship — the same posture
+`src/bongos/middleware/audit.js` already takes.
+
+### 4. The CLI declares its own empty ships
+
+`scripts/gds/ship.js` POSTs `/ship` with an empty body after a `--db-only` / `--allow-empty` land. Left
+alone, this gate would have refused exactly the flow CLAUDE.md calls supported — turning a correctness
+fix into a regression for every builder shipping DB-only work. The deliberate-empty land sites now mark
+themselves, and the CLI sends the declaration.
+
+## Consequences
+
+- **A confirmed-but-unpushed task can no longer be manually shipped or paid.** The refusal names both
+  remedies: push the branch and let the reconciler land it, or declare the no-artifact ship.
+- **The hall's task page ships through the same route** and will now receive a `409
+  ship_land_not_proven` for an unprovable task. That is the correct behaviour — the UI should not be
+  able to phantom-ship either — but its error rendering was not reviewed here and may show the refusal
+  poorly. Worth a look.
+- **`shipTask`'s signature changed.** Three production call sites and four test files were updated. Any
+  out-of-repo caller breaks loudly rather than shipping blind, which is the intended direction.
+- **A STALE `ship.js` against an updated server cannot complete a DB-only ship.** The CLI is what sends
+  the `no_artifact` declaration; an older checkout POSTs an empty body and collects
+  `409 ship_land_not_proven` on a task that has no commit to prove. The refusal names exactly what to
+  send, but the old CLI will not send it, so the remedy is to update the checkout (or re-send by hand).
+  Bounded rather than open-ended — the CLI travels with the core, so on the monolith and on a consumer
+  instance the two move together; the skew window is a builder running a stale clone or dev box. Worth
+  knowing before the first report, because the symptom ("I cannot ship my DB-only task") does not
+  obviously point at a version skew. **Note this affects ONLY no-artifact ships:** a normal ship is
+  proven server-side from git and needs nothing from the CLI.
+- **This does not gate CONFIRM.** A codeless confirm is still accepted; what it can no longer do is
+  reach `shipped` and book a credit. Gating confirm is a separate question — confirm means "verified",
+  not "landed", and conflating them would break the legitimate confirm-then-land sequence.
+- **Rejected — option (c), record the residual as tolerable.** Defensible on blast radius, and it was
+  genuinely close. It lost because the residual had already survived one incorrect closure and several
+  blocker filings; a decision to accept it would have been the fourth record asserting this was
+  handled, with nothing checkable behind it.

package/docs/adr/README.md

@@ -257,5 +257,6 @@ This keeps the decision history honest and traceable.
 | 0181 | [**Teardown accepts every state but `torn_down`, and deliberately keeps the address** ([task 1003042](https://cloudbongos.com/builders#/task/1003042), goal 1000058). Walk finding N5: an instance at `status='error'` could never be removed — the owner's teardown answered 409 `not_teardownable` and the archon `force-teardown`, which exists as the escape hatch, answered the SAME refusal, because both read one hand-kept whitelist `['provisioning','active','tearing_down']` that omitted `requested` and `error`. No role had a path out, so errored rows accumulated permanently (instance 15 `swag` from 2026-08-07). The whitelist justified itself as "nothing running to tear down", which is FALSE for `error`: a provision failing mid-run lands there AFTER it may have created the database, taken a port, and written the systemd unit, Caddy block and DNS record — a partial standup is the thing most in need of reclaiming. `TEARDOWN_FROM` is now DERIVED from `INSTANCE_STATES` minus `torn_down`, so a future state is teardownable by DEFAULT — the bug was an allow-list that silently omitted states, and for a failure mode whose signature is "a row with no exit", the safe default is that an exit exists. The runner needed no change (its steps are each `allowFail`); only the web guard refused. The one surviving refusal is now ONE shared helper: the copies had drifted, and force-teardown's positional `res.fail` form put the bare code `not_teardownable` on the wire as the human text. **The `port` and `domain` are deliberately NOT released** — releasing the port alone would be WORSE than the status quo, because the `<slug>.caddy` block survives teardown and proxies the hostname to a PORT NUMBER, so a later instance given that port would answer at the torn-down project's still-live address (verified live: two projects torn down 2026-08-13 still resolved on 2026-08-19). Holding the port is what keeps the address inert at a harmless 502; releasing both is [task 1002897](https://cloudbongos.com/builders#/task/1002897). Retention is also correct for revive, which re-uses the same hostname. Copy was corrected to match: it had promised "the address stops answering", which was never true.](0181-teardown-state-gate-and-address-retention.md) | provisioning / lifecycle |
 | 0182 | [**Project visibility is TWO axes: a derived publish gate and a stored join door** ([task 1002320](https://cloudbongos.com/builders#/task/1002320), goal 1000046). Goal 1000046 seeded 31 tasks each citing "per R01" — this ADR — so nothing in the goal could start until it landed: it gated **29 open tasks**, the largest single chokepoint in the repo, while itself parked at `backlog` with no dependencies. The spec its planning task cites was never written, so this is the design of record. The goal's criterion says **four** states (Public/Private/Stealth/Unlisted) and R04 says **three** stored plus a derived dark-matter; both are right and conflating them is the trap. There are two INDEPENDENT axes: **publishability** (DERIVED from the identity gate — name + description, per the owner interview) decides whether a project is on the map at all, and **the join door** (STORED `visibility ∈ public|private|stealth`, owner-set) decides how it renders and who gets in. Four user-facing states = 3 × publishable + one derived state that collapses all three. The column name `visibility` is a mild lie kept for consistency with `goals.visibility` (ADR 0112) — it does NOT decide visibility, publishability does — and the ADR is the mitigation. All three stored states are VISIBLE; only the derived state is invisible, which is what makes the 3+1 split honest rather than a workaround. `private` inherits ADR 0112's exact meaning (visible-but-closed); `stealth` exposes EXISTENCE but not IDENTITY, and its redaction is **server-side in the feed** — the naive client-side version leaks to anyone opening the network tab, and the orbs page is a static site OUTSIDE this repo (R09) so it could never be enforced there. Three mechanisms touch "does this appear" and are separated: `status` (operational), `visibility` (owner), `featured` (Archon editorial) — on the map iff `status='active' AND publishable`, with `featured` only ranking among those. That is a real behaviour change: today's predicate is `featured=true AND status='active'`, so **featuring is currently load-bearing for visibility at all** and the goal's owner-control premise silently does not work without it. Visibility is owned by the INSTANCE and the hub row is a CACHE (ADR 0141 §3 + the admin-console spike's D1) — so `owner_github_id` being "advisory, not an authority" is CORRECT rather than a gap, R05 moves to an instance surface, and R08's absent-report default is fail-closed (unreported ⇒ dark matter, off the map rather than exposed by omission). Per-state join rules compose with the separate `open|closed` join policy ([task 1002817](https://cloudbongos.com/builders#/task/1002817)) by one rule: **visibility sets the ceiling, join policy may only narrow** — otherwise the two settings are a coin-flip decided by evaluation order. Finally, `stealth` COLLIDES with the existing instance-wide pre-launch password gate (`STEALTH_PASSWORD`, `src/bongos/stealth-gate.js`), which means nearly the opposite (a whole instance made unreadable vs a project publicly on the map, anonymously); per ADR 0174 the product meaning keeps the word and the infra rename is filed separately rather than decided by an ADR about visibility. Rejected: a stored 4-valued enum (makes `unlisted` compete with `private`, and lets publishable+unlisted disagree), a separate `published` boolean (can drift from the identity it summarises; derived cannot), and keeping `featured` as the visibility gate (an owner who sets public and appears nowhere has not been given control).](<redacted>.md) | platform-identity / project visibility |
 | 0183 | [**A done-when criterion closes itself; the review queue becomes a place to look** ([task 1002069](https://cloudbongos.com/builders#/task/1002069), goal 1000072, owner request 2026-07-05). ADR 0086 §6 made `satisfied` reachable exactly one way — a Metic+ calling `POST /done-when/:id/satisfy` — even though the signal it gated on is unambiguous (**every** gating task shipped) and a human confirming it adds no information. When nobody runs `/goal-review` the result is not a careful pause but a **lying board**: this session measured goal 1000072 at `6/9 shipped, 0/5 criteria`. Now one helper, `doneWhen.autoSatisfyShippedCriteria(exec, {taskId})`, runs from **two** places for two different reasons — inside `shipTask`'s txn (scoped, **immediate**, on the txn client so a rolled-back ship cannot leave a goal achieved) and unscoped on every `publish-reconciler` tick (**backlog drain** for criteria whose tasks shipped before this existed, since nothing will ship against them again, plus **self-heal**). Idempotent by construction — it reads only `satisfied=false` rows — which is what makes an every-tick sweep safe. **The load-bearing subtlety is the delivery guard.** Auto-close needs BOTH "nothing still pending" AND **≥ 1 task actually `shipped`**; the second is not redundant, because since [task 1002651](https://cloudbongos.com/builders#/task/1002651) made `abandoned` terminal-not-pending, a criterion whose tasks were **all cut** satisfies the first clause *vacuously* and would auto-close on ZERO delivered work, cascading its goal to `achieved` (measured: `buildCriterionProgress` returns `pending_review:true` for exactly that shape). Yet `pending_review` **keeps** that wider meaning on purpose — it asks "should a human LOOK at this", and 1002651 chose that an all-abandoned criterion surfaces so someone decides whether it still means anything. So: everything that auto-closes was flagged; not everything flagged auto-closes. An earlier draft "aligned" the two predicates and broke that intent — `tests/criterion_progress.mjs` caught it; **do not re-align them**, the gap is the design. `/goal-review` is kept, demoted from gate to viewing surface; manual `POST /satisfy` stays for what automation cannot judge (a criterion with no linked tasks never auto-closes). Honest limits recorded: auto-satisfy cannot help a criterion nothing is LINKED to, and the in-txn close logs before commit (accepted — threading the summary out through `withTx` would cost ~5 lines in the over-threshold `db.js` under shrink-only ratchet policy). Rejected: sweep-only (up to 5 min to see your own goal close), hook-only (never drains the backlog), a stored `pending_review` column (second source of truth), deleting `/goal-review`.](<redacted>.md) | lifecycle / goal tier |
+| 0184 | [**A ship must account for itself: `shipTask` requires a land proof or a declared no-artifact** ([task 1002483](https://cloudbongos.com/builders#/task/1002483), goal 1000024). `db.shipTask` is the confirmed→shipped flip and, since [ADR 0120](<redacted>.md), where the CREDIT is booked — yet its only precondition was `WHERE status = 'confirmed'`, nothing about whether code reached main. The two AUTOMATED paths each proved the land first; the MANUAL route passed nothing, so a task confirmed with no pushed code could be shipped by its claim holder **or by any Metic+ sweeping `/merge-mode`**, booking its `task.shipped` credit. It stayed untracked for two months because its tracking task was closed in June asserting task 1001547 had delivered the gate — it had not, blocker 1000047's own final update says so, and the code agreed with the blocker rather than the closure note: **a hole hidden by a record nobody checked**, which is the same failure the gate is about. Decision: the gate lives at the WRITE, not the route (a route gate leaves the invariant unenforced at the layer that moves the ledger, so the next caller reopens it silently), and `shipTask` is FAIL-CLOSED on a required `landAssurance`. TWO kinds, and the second is why this does not make things worse: `proof` (this task's commit is on main) and **`no_artifact`** — a deliberate DB-only ship, an explicitly supported shape (CLAUDE.md "Direct DB writes are work too") that [task 1002478](https://cloudbongos.com/builders#/task/1002478) documents as a dead end below Archon. A naive proof-only gate would have made 1002478 strictly worse; naming no-artifact as a KIND turns it from an absence the gate must be talked out of into a recorded answer. Both carry a reason, audited post-commit and best-effort (an audit miss must never roll back a landed ship). `ship.js` now declares its own `--db-only`/`--allow-empty` lands, without which this fix would have regressed the very flow CLAUDE.md calls supported. Rejected: (b) gate only the route — leaves the write unguarded; (c) record the residual as tolerable — defensible on blast radius and genuinely close, but it would have been the FOURTH record asserting this was handled with nothing checkable behind it. Does NOT gate confirm: a codeless confirm is still accepted, it simply cannot reach `shipped` or pay.](<redacted>.md) | lifecycle / integrity |
 
 > ⚠️ **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/docs/api/openapi.json

@@ -12938,6 +12938,18 @@
             "description": "Path parameter `id`."
           }
         ],
+        "requestBody": {
+          "required": false,
+          "content": {
+            "application/json": {
+              "schema": {
+                "type": "object",
+                "additionalProperties": true
+              }
+            }
+          },
+          "x-validated": true
+        },
         "responses": {
           "200": {
             "description": "Success.",
@@ -12950,7 +12962,7 @@
             }
           },
           "400": {
-            "$ref": "#/components/responses/BadRequest"
+            "$ref": "#/components/responses/ValidationFailed"
           },
           "401": {
             "$ref": "#/components/responses/Unauthorized"

package/docs/api-reference.md

@@ -516,7 +516,7 @@ Base path: `/api/bongos`. Ranks (enforced server-side, [ADR 0016](adr/<redacted>
 | POST | `/api/bongos/tasks/:id/promote` | `metic+archon` | — | backlog→ready promotion; scope mutation; ADR 0090 (was archon). |
 | POST | `/api/bongos/tasks/:id/publish-branch` | `any-builder` | `branch`, `head_sha`, `bundle_b64`, `value_summary` |  |
 | GET | `/api/bongos/tasks/:id/publish-status` | `any-builder` | — | GET /tasks/:id/publish-status?branch=<branch> — poll the PR + prod-deploy state for a server-mediated publish so ship.js can confirm the … |
-| POST | `/api/bongos/tasks/:id/ship` | `any-builder` | — | confirmed → shipped. |
+| POST | `/api/bongos/tasks/:id/ship` | `any-builder` | validated | confirmed → shipped. |
 | POST | `/api/bongos/tasks/:id/vote` | `metic+archon` | `vote` | POST /tasks/:id/vote { vote: 1 \| -1 \| 0 } — cast/change/clear a peer vote on a confirmed/shipped task. |
 | GET | `/api/bongos/tasks/claimable` | `any-builder` | — | NOTE: /tasks/claimable must come BEFORE /tasks/:id or Express will route 'claimable' to the :id param. |
 | GET | `/api/bongos/tasks/newcomer-floor` | `any-builder` | — | GET /tasks/newcomer-floor — supply gauge for the newcomer queue (task 614). |

package/modules/lifecycle/db.js

@@ -30,6 +30,7 @@
 
 const api = require('../../src/module-api');
 const { pool, withTx, insertAuditLog, LIVE_RANK_LADDER, RANK_TIER } = api;
+const log = api.logger('lifecycle'); // namespaced; the ratchet counts bare console calls
 // The seam registry (resolveOptional/emit/emitAsync) — the doorway re-exports it,
 // so the module reaches the `reward`/`onboarding` ports + emits kernel events
 // (task.shipped, builder.box-reconcile-needed) without importing core.
@@ -2377,22 +2378,6 @@ async function removeDependency(fromKind, fromId, toKind, toId) {
   return rowCount > 0;
 }
 
-// Edges for a node. reverse=false: what (kind,id) depends on; reverse=true: what
-// depends on (kind,id).
-
-async function getDependencies(kind, id, { reverse = false } = {}) {
-  const selfKind = reverse ? 'to_kind' : 'from_kind';
-  const selfId = reverse ? 'to_id' : 'from_id';
-  const { rows } = await pool.query(
-    `SELECT from_kind, from_id, to_kind, to_id, created_at
-       FROM dependencies
-      WHERE ${selfKind} = $1 AND ${selfId} = $2
-      ORDER BY from_kind, from_id, to_kind, to_id`,
-    [kind, id]
-  );
-  return rows;
-}
-
 // ---------------------------------------------------------------------------
 // Task ↔ criterion links (task_criteria, migration 055 / ADR 0025; populated on
 // task-create + manage endpoints by task 438). Mirrors the task_dependencies
@@ -3725,7 +3710,11 @@ async function needsRebaseTasksForBuilder(builderId, client = pool) {
   return rows;
 }
 
-async function shipTask({ taskId, builderId }, deps = {}) {
+// The ship gate (task 1002483, ADR 0184) — see ./ship-assurance for the why.
+const { normalizeShipAssurance, assertShipAssurance, recordShipAssurance, SHIP_ASSURANCE_KINDS } = require('./ship-assurance');
+
+async function shipTask({ taskId, builderId, landAssurance }, deps = {}) {
+  const shipAssuranceValue = assertShipAssurance(landAssurance); // FAIL-CLOSED, ADR 0184
   // #538 test seam (mirrors confirmTask): a caller-supplied pool is honored ONLY
   // under NODE_ENV==='test', so a regression test can drive the txn with a
   // SQL-aware fakeClient. Production callers omit deps → module pool.
@@ -3888,8 +3877,11 @@ async function shipTask({ taskId, builderId }, deps = {}) {
       builderId: actualShipperId, rank: 'thetes', status: rankGraduation.status, actor: 'auto-graduation:#692',
     }).catch(() => {});
   }
+  await recordShipAssurance({ insertAuditLog, taskId, builderId: actualShipperId, assurance: shipAssuranceValue, log });
   return {
     ...shipRow,
+    shipAssurance: shipAssuranceValue, // echoed so a caller can show it, not guess
+
     graduatedTo: rankGraduation ? 'thetes' : null,
     // ADR 0120: the per-task reward that landed on THIS ship (0 on a re-ship /
     // reconciler re-sweep — idempotent). The ship route surfaces it so the
@@ -5700,7 +5692,6 @@ module.exports = {
   findCycle,
   addDependency,
   removeDependency,
-  getDependencies,
   unsatisfiedDeps,
   parseCriterionRef,
   resolveCriterionIds,
@@ -5719,6 +5710,7 @@ module.exports = {
   restoreTask, // ADR 0152 — the abandoned→backlog undo that pairs with the Metic+ abandon grant
   applyGrade,
   shipTask,
+  normalizeShipAssurance, SHIP_ASSURANCE_KINDS, // ADR 0184 — re-exported from ./ship-assurance
   flagTaskNeedsRebase, // ADR 0120 part 2 — reconciler flags an unlandable confirmed task for its builder
   needsRebaseTasksForBuilder, // ADR 0120 part 3/5 — the claim gate + hall/CLI read the builder's owed rebases
   listConfirmedTasksForReconcile, // task 1134 — server-owned publish reconciler feed

package/modules/lifecycle/publish-reconciler.js

@@ -705,7 +705,14 @@ async function runSweep(deps = {}) {
     }
 
     try {
-      const shipped = await db.shipTask({ taskId: r.task_id, builderId: r.builder_id });
+      // task 1002483: the sweep only reaches here on a PROVEN land (the `if
+      // (!landed) … continue` above), so it hands that proof to the gate rather
+      // than letting shipTask re-derive it. landNote carries which probe proved it.
+      const shipped = await db.shipTask({
+        taskId: r.task_id,
+        builderId: r.builder_id,
+        landAssurance: { kind: 'proof', reason: landNote || 'reconciler: land proven' },
+      });
       reconciled++;
       dispositions.push(`${r.task_id}:shipped`);
       logFn(

package/modules/lifecycle/routes/tasks.js

@@ -14,6 +14,8 @@ const { buildGoalAdvisory } = require('../goal-advisory');
 // longer imports the grader — it resolves the `grade` kernel PORT at grade time
 // (seams.resolveOptional('grade'), in POST /tasks/:id/grade below).
 const githubPush = require('../github-push');
+const shipAssurance = require('../ship-assurance');
+const RECONCILE_PROOF = Object.freeze({ kind: 'proof', reason: 'publish-status reconcile: land proven' });
 const seams = api;
 const { classifyTaskKind, VALID_KINDS, VALID_DISCIPLINES, VOTABLE_TASK_STATUSES, TASK_FIELD_BOUNDS } = require('../task-classifier');
 const { isModuleKey, moduleKeys } = api.moduleScopeMap;
@@ -1138,8 +1140,12 @@ module.exports = function buildTasksRouter() {
     // OWN confirmed task. allowSupervisor lets Metic+ (who run /merge-mode) ship
     // across builders; the claim holder ships their own; everyone else is 403'd.
     if (!(await gateTaskOwnership(req, res, id, { allowSupervisor: true }))) return;
+    if (validateOrRespond(req, res, shipAssurance.SHIP_BODY_SCHEMA)) return; // ADR 0184
     try {
-      const task = await db.shipTask({ taskId: id, builderId: req.builder.id });
+      // The ship gate (ADR 0184) — this route is the path that had none.
+      const landAssurance = await shipAssurance.gateManualShip(res, { taskId: id, body: req.body || {}, db, githubPush, log: api.logger('lifecycle') });
+      if (!landAssurance) return;
+      const task = await db.shipTask({ taskId: id, builderId: req.builder.id, landAssurance });
       // task 1749: emit task.shipped on THIS entry point too, not just the
       // publish-status reconcile-on-read path (line ~1545) + the reconciler
       // sweep. A direct ship here (e.g. /merge-mode sweeping the confirmed
@@ -1718,7 +1724,7 @@ module.exports = function buildTasksRouter() {
       }
       if (githubPush.landConfirmed(status) && !reconcile_blocked) {
         try {
-          const shipped = await db.shipTask({ taskId: id, builderId: req.builder.id });
+          const shipped = await db.shipTask({ taskId: id, builderId: req.builder.id, landAssurance: RECONCILE_PROOF }); // ADR 0184
           reconciled = true;
           // task 1045: the box that published can't post the Discord broadcast —
           // it holds no webhook secret (ADR 0053 "box holds nothing"), so a box

package/modules/lifecycle/ship-assurance.js

@@ -0,0 +1,159 @@
+'use strict';
+
+// modules/lifecycle/ship-assurance.js — WHY a ship was allowed (task 1002483,
+// ADR 0184). A sibling of ship-preflight.js / ship-card.js: pure, DB-free, and
+// deliberately NOT inside db.js, which is already an oversized file the quality
+// ratchet measures.
+//
+// THE HOLE THIS CLOSES. db.shipTask is the confirmed→shipped flip and, since
+// ADR 0120, where the CREDIT is booked. Its only precondition was
+// `WHERE status = 'confirmed'` — nothing about whether any code reached main. The
+// two AUTOMATED paths each proved the land before calling; the MANUAL route
+// passed nothing, so a task confirmed with no pushed code could be flipped to
+// shipped by its claim holder or by any Metic+ sweeping /merge-mode, booking its
+// task.shipped credit.
+//
+// TWO KINDS, and the second is the reason this gate does not make things worse:
+//
+//   proof        the caller verified THIS task's own commit is on main.
+//   no_artifact  a deliberate DB-only ship — an explicitly supported shape
+//                (CLAUDE.md, "Direct DB writes are work too") that task 1002478
+//                documents as a DEAD END below Archon today. Naming it a KIND is
+//                what keeps this gate from worsening that: a no-artifact ship
+//                becomes a recorded answer, not an absence the gate has to be
+//                talked out of.
+//
+// Both carry a `reason`, so the audit row says WHY a ship was allowed rather than
+// merely that it happened — which is exactly what was missing when this hole went
+// unnoticed for two months behind an incorrect closure note.
+
+// The write-schema for the manual ship route's declaration fields (ADR 0118
+// requires every write route to validate its body). Declared beside the gate
+// that consumes them.
+const SHIP_BODY_SCHEMA = Object.freeze({
+  no_artifact: { type: 'boolean' },
+  no_artifact_reason: { type: 'string', maxLength: 500 },
+});
+
+const KINDS = Object.freeze(['proof', 'no_artifact']);
+const MAX_REASON_CHARS = 500;
+
+// Validate an assurance. Returns { ok, value } | { ok:false, code, allowed }.
+// FAIL-CLOSED by construction: every unhappy shape returns a code, and shipTask
+// throws on any of them, so a caller that cannot say why this is a legitimate
+// ship never reaches the write.
+function normalizeShipAssurance(a) {
+  if (!a || typeof a !== 'object' || Array.isArray(a)) {
+    return { ok: false, code: 'ship_assurance_required' };
+  }
+  if (!KINDS.includes(a.kind)) {
+    return { ok: false, code: 'ship_assurance_bad_kind', allowed: KINDS };
+  }
+  const reason = String(a.reason == null ? '' : a.reason).replace(/\s+/g, ' ').trim();
+  if (!reason) return { ok: false, code: 'ship_assurance_reason_required' };
+  return { ok: true, value: { kind: a.kind, reason: reason.slice(0, MAX_REASON_CHARS) } };
+}
+
+// Derive the assurance for a MANUAL ship (POST /tasks/:id/ship) — the path that
+// had no gate at all. Returns { assurance } to proceed, or { refusal } the route
+// answers verbatim.
+//
+// Order matters: PROVE first, and only fall back to the declaration. A caller who
+// pushed real work should never have to declare anything, and a declaration must
+// never be able to override an available proof.
+//
+// A probe miss is NOT a licence to ship. It means "no proof yet", which lands on
+// the same refusal — the fail direction is to wait, never to pay.
+//
+// `deps` is injected so this is unit-testable with no network and no DB.
+async function deriveShipAssurance({ taskId, body = {}, db, githubPush, onProbeError }) {
+  try {
+    const publishedSha = await db.getClaimPublishedSha(taskId);
+    const status = await githubPush.getPublishStatus({ taskId, publishedSha });
+    const proof = await githubPush.landProvenForTask({ taskId, publishedSha, status });
+    if (proof && proof.proven) return { assurance: { kind: 'proof', reason: proof.reason } };
+  } catch (e) {
+    if (onProbeError) onProbeError(e);
+  }
+
+  if (body.no_artifact === true) {
+    const reason = String(body.no_artifact_reason || '').trim();
+    if (!reason) {
+      return {
+        refusal: {
+          code: 'no_artifact_reason_required',
+          status: 400,
+          details: {
+            what_this_means: 'A no-artifact ship is legitimate, but the ledger records WHY. Say what was delivered (a DB row, a config change, a decision) in no_artifact_reason.',
+          },
+        },
+      };
+    }
+    return { assurance: { kind: 'no_artifact', reason } };
+  }
+
+  return {
+    refusal: {
+      code: 'ship_land_not_proven',
+      status: 409,
+      details: {
+        what_this_means: 'This task has no commit provably on main, so shipping it here would book a credit for work nobody can point at.',
+        your_options: [
+          'Push the branch and let it land — the reconciler ships it automatically once the merge is provable.',
+          'If this task genuinely has no code artifact, re-send with { "no_artifact": true, "no_artifact_reason": "…" } so the ledger records the declaration.',
+        ],
+      },
+    },
+  };
+}
+
+
+// Record WHY a ship was allowed, not merely that it happened. POST-COMMIT and
+// best-effort by design: insertAuditLog uses the module pool rather than the
+// ship's transaction client, and an audit miss must never roll back a landed ship
+// (the posture src/bongos/middleware/audit.js already takes).
+async function recordShipAssurance({ insertAuditLog, taskId, builderId, assurance, log }) {
+  try {
+    await insertAuditLog({
+      builderId,
+      route: `/tasks/${taskId}/ship`,
+      method: 'SHIP',
+      requestBodyRedacted: { ship_assurance: assurance },
+      responseStatus: 200,
+      surface: 'lifecycle',
+    });
+  } catch (e) {
+    if (log) log.warn('shipTask: ship-assurance audit write failed (non-blocking):', e && e.message);
+  }
+}
+
+// Throwing form, so the caller is one line. Returns the normalized value or
+// throws with the named code — shipTask's FAIL-CLOSED precondition.
+function assertShipAssurance(landAssurance) {
+  const a = normalizeShipAssurance(landAssurance);
+  if (a.ok) return a.value;
+  const e = new Error('ship assurance required');
+  e.code = a.code;
+  e.allowed = a.allowed;
+  throw e;
+}
+
+// Route form: derive, or answer the refusal on `res` and return null. Keeps the
+// gate a two-line concern in the (oversized) route file.
+async function gateManualShip(res, opts) {
+  const { log, taskId } = opts;
+  const derived = await deriveShipAssurance({
+    ...opts,
+    onProbeError: (e) => log && log.warn(`POST /tasks/${taskId}/ship: land probe failed (${e && e.message}) — no proof`),
+  });
+  if (derived.refusal) {
+    res.fail(derived.refusal.code, derived.refusal.status, derived.refusal.details);
+    return null;
+  }
+  return derived.assurance;
+}
+
+module.exports = {
+  normalizeShipAssurance, deriveShipAssurance, recordShipAssurance,
+  assertShipAssurance, gateManualShip, SHIP_BODY_SCHEMA, SHIP_ASSURANCE_KINDS: KINDS, MAX_REASON_CHARS,
+};