@bongos/core 1.19.917 → 1.19.919

package/.bongos-core.json

@@ -2,22 +2,22 @@
   "artifact": "bongos-core",
   "manifest_schema": 1,
   "generator": "scripts/gds/package-core.js",
-  "core_version": "1.19.917",
-  "core_contract": "1.19.917",
-  "source_commit": "5e828ad0df8cbaa5a638c0365e6a9f993756b6f9",
+  "core_version": "1.19.919",
+  "core_contract": "1.19.919",
+  "source_commit": "bc2cae9667f75f9a2df301fc776a5e0b79451325",
   "source_ref": "HEAD",
-  "built_at": "2026-09-20T17:33:13.906Z",
+  "built_at": "2026-09-20T19:06:48.075Z",
   "redaction": {
     "model": "docs-redacted+functional-verbatim",
-    "docs_redacted": 506,
+    "docs_redacted": 508,
     "agent_docs_stubbed": 26,
-    "functional_verbatim": 2298,
+    "functional_verbatim": 2302,
     "rules": 3,
     "gate_literals": 3,
     "gate": "passed"
   },
-  "file_count": 2830,
-  "tree_sha256": "5d48e907f305164b84433d1bad09d324336c2fb2924f148081143ff761c39f58",
+  "file_count": 2836,
+  "tree_sha256": "fcb4d5d17d74106fc9ba7d49143956885bb9c5dadc48c2e1a3aa39ebcc76a851",
   "files": [
     {
       "path": ".claude/skills/ask-for-help/SKILL.md",
@@ -347,12 +347,12 @@
     {
       "path": "clients/bongos-client/README.md",
       "mode": "0000644",
-      "sha256": "3d49c3ab2ec849b4b6b8856fc33161dae6d4728565afc3e781c9f9b8c00068c5"
+      "sha256": "56d3e08ff4e4893d4d6b30c9292f2c1b0730deb2bff99ea64d7d5df7971995c1"
     },
     {
       "path": "clients/bongos-client/bongos-client.global.js",
       "mode": "0000644",
-      "sha256": "2697c2c2ca3b5ede19b7f5511eb51ae6173973b4db01d20183ef560a95315c42"
+      "sha256": "7cfab2d88dc9d36fc57334db3b43c0c31b3656e2bff7ebff11d0c18b12a61850"
     },
     {
       "path": "clients/bongos-client/examples/hello-world.mjs",
@@ -362,17 +362,17 @@
     {
       "path": "clients/bongos-client/index.cjs",
       "mode": "0000644",
-      "sha256": "b80472a5a66e342b8dc9c09c61a570cc3272756cf311eb16f77a125d8ae66afd"
+      "sha256": "8a5ed1946540c3adb30ff986f1845bdc65b5a6e441698723f8c31eb8e1374ef2"
     },
     {
       "path": "clients/bongos-client/index.d.ts",
       "mode": "0000644",
-      "sha256": "de24c22270e6a95dcf5674aac3b445e08fce3cd1982d0e922d84ca9e199a36e0"
+      "sha256": "e84a082d51b6f1e3890886a087763ec155fa31d17ac697a291e557df5bce2345"
     },
     {
       "path": "clients/bongos-client/index.mjs",
       "mode": "0000644",
-      "sha256": "084e5d2634ec4a5ddbc4a537ad32ec88296bb55f0439c7c4dc8e534eaad5fd71"
+      "sha256": "7676427e266c9528793e47c3c9431c329b67f0b29edff522724f430b4c29a37f"
     },
     {
       "path": "clients/bongos-client/package.json",
@@ -2062,7 +2062,7 @@
     {
       "path": "docs/adr/0314-module-protection-is-per-path-not-per-module.md",
       "mode": "0000644",
-      "sha256": "accaba461051e427c251e9c4ec4ff74304447fd6cd68f940311f4b978ff234c2"
+      "sha256": "d408c3f7bee29bbdf5f537ec7ed4559b88fae5d8074a8d58e556dc9e65bff46d"
     },
     {
       "path": "docs/adr/0315-a-plane-with-no-proxy-is-refused-not-given-a-no-op-ingress.md",
@@ -2079,20 +2079,30 @@
       "mode": "0000644",
       "sha256": "4dd5bbb9c14e4ba19568646ceea2d29b66c46b99555d6c236a25b7b40097756c"
     },
+    {
+      "path": "docs/adr/0318-listing-a-file-for-task-affinity-is-not-owning-it.md",
+      "mode": "0000644",
+      "sha256": "d5364169236db8c8d1a7968051fba352bb368aca53b19e554f172e0c3dc90d5d"
+    },
+    {
+      "path": "docs/adr/0319-a-removal-verdict-is-a-row-beside-the-question.md",
+      "mode": "0000644",
+      "sha256": "2fbb3e040b55162284242f545af76b1254fafbecfe042b8c792dc0dca475c4f8"
+    },
     {
       "path": "docs/adr/README.md",
       "mode": "0000644",
-      "sha256": "05a90e437ed0c53a9bcc4f310f9cb056c4f8aa333ab8953f2f56a20d4381f7f9"
+      "sha256": "087b5151c182476c1f541e239776099319ad7fa95e6ebc2dc5ccf2b320c84f0c"
     },
     {
       "path": "docs/api-reference.md",
       "mode": "0000644",
-      "sha256": "dfc37d531b880bc87d6d4e1b09eae50ef3e0301781ed84923304bc77b878b9b9"
+      "sha256": "8c709c0a86391ef42df7c594087d8ebe77bb26c19b8f92f95a21c19da30de87e"
     },
     {
       "path": "docs/api/openapi.json",
       "mode": "0000644",
-      "sha256": "8ab5797e6b515965da750890ab78ae16d61326d19a26751a0dde3bc2f72b6797"
+      "sha256": "6e2d8fc4d48d267ee7b16a81f48651c6d19dfa55716d7736c92e5cb734cc6b4f"
     },
     {
       "path": "docs/architecture.md",
@@ -2117,12 +2127,12 @@
     {
       "path": "docs/copy-inventory.md",
       "mode": "0000644",
-      "sha256": "cadfe92b87eaf4f2bb952debc703c53b833fd83badbefcce40e7203a0d150c95"
+      "sha256": "4f848ba8e139ff864151d71e4f743f799b23cf1d6a59e3638aae13ed45bce4d6"
     },
     {
       "path": "docs/copy-registry.json",
       "mode": "0000644",
-      "sha256": "f6571a42a27d5cfeef058d06937fc669a31da076bc26972c5e29a8fa1d156b5d"
+      "sha256": "dc177418430b6f87b508867d35d8ef7e821d113d0ede598462a690402d699f46"
     },
     {
       "path": "docs/design/apex-pass-2-direction.md",
@@ -2652,7 +2662,7 @@
     {
       "path": "docs/module-api-changelog.md",
       "mode": "0000644",
-      "sha256": "7459f942b736ed35b74c50c3f95279e64f3c80dc7e06d686aef147bf6c3bb62c"
+      "sha256": "e15b7bc78c0b64fc27725df643ec05f20e047322623ac182f3614fea341521bb"
     },
     {
       "path": "docs/modules-contract.md",
@@ -4837,7 +4847,7 @@
     {
       "path": "modules/hall-ui/public/goal-inbox.js",
       "mode": "0000644",
-      "sha256": "21a107078833924161c2111f40586272eed71eeba7eb1686088b1d2000d9ff78"
+      "sha256": "8e8d581eb99bbff050e088b727266b9f4c0ab957d1c98fd407e2c4d592a5c8b3"
     },
     {
       "path": "modules/hall-ui/public/goals-lib.js",
@@ -5257,7 +5267,7 @@
     {
       "path": "modules/hall-ui/public/style.css",
       "mode": "0000644",
-      "sha256": "4eb1af09e4c3fde77f892f137f32ef768396eb9b0400515c01903128d394de9e"
+      "sha256": "a7824a889c87fe40725350fd9543929e69e1370fb17023af0447f8254887d72e"
     },
     {
       "path": "modules/hall-ui/public/task-detail.js",
@@ -5502,7 +5512,7 @@
     {
       "path": "modules/lifecycle/cascade.js",
       "mode": "0000644",
-      "sha256": "52e63c329e4546f0a8ce2ca75157b9974b23eeaabf155f7ea02ead4d8f9bb8a8"
+      "sha256": "fd8aeec221eede847aa3b0047c01721ac7e2076e95675a71a117eff3bf3bbc55"
     },
     {
       "path": "modules/lifecycle/check-rollup.js",
@@ -5739,6 +5749,11 @@
       "mode": "0000644",
       "sha256": "4e4099764712b6ac8ad322cb846eb1e4b1118e936d03628e01a6a04adb4d4ebf"
     },
+    {
+      "path": "modules/lifecycle/migrations/lifecycle_009_removal_verdicts.sql",
+      "mode": "0000644",
+      "sha256": "e98efbb1537f0d99adb6b6b66c1fdccfd4bbac16b97362d479af903eb9de492c"
+    },
     {
       "path": "modules/lifecycle/mingle.js",
       "mode": "0000644",
@@ -5747,7 +5762,7 @@
     {
       "path": "modules/lifecycle/module.json",
       "mode": "0000644",
-      "sha256": "4c6e01ef15774232ad9284915546b2d9756dc89f85159980fb7087e7a6673d3c"
+      "sha256": "01f96d398408491bc4f1d9357c23c259f16e52184569849a0caf775f5b38836b"
     },
     {
       "path": "modules/lifecycle/pg-constraint-fail.js",
@@ -5774,6 +5789,11 @@
       "mode": "0000644",
       "sha256": "ef63843d5d00230a90063c454a5ad7a9dc170ce26cedc99377807ae1ced3f7c0"
     },
+    {
+      "path": "modules/lifecycle/removal-proposals.js",
+      "mode": "0000644",
+      "sha256": "8270ce55255998a4f0bbf574a54df0ba2597013c727b4afb1ce2abad9c9d4d2a"
+    },
     {
       "path": "modules/lifecycle/rot.js",
       "mode": "0000644",
@@ -5859,6 +5879,11 @@
       "mode": "0000644",
       "sha256": "a8e851ca630a24b197e7ecb8f8cd8ac3d169801bacbac72097528500f95d6cdb"
     },
+    {
+      "path": "modules/lifecycle/routes/removal-proposals.js",
+      "mode": "0000644",
+      "sha256": "329f130d3556dc05981ce6b4b6ce4d55984c6ca42fd0f421fd70cba63eb277ac"
+    },
     {
       "path": "modules/lifecycle/routes/rot.js",
       "mode": "0000644",
@@ -7847,12 +7872,12 @@
     {
       "path": "package-lock.json",
       "mode": "0000644",
-      "sha256": "fd2d387fbc65cce2c412625937abd7fd2c7760083fd0768aa8ae45c2e8bd4992"
+      "sha256": "c74ec04aa7a18c9c94e42afecaac34a114331a3769e1df4af00e192555155f66"
     },
     {
       "path": "package.json",
       "mode": "0000644",
-      "sha256": "bfee39b9a538046973186020153d4058238ccd25e55c8874316fd5ebab0c42c2"
+      "sha256": "fc839d817a279254882dd33532bbbb2831174de15f28b3c72a3830021e8ded5f"
     },
     {
       "path": "public-docs/index.html",
@@ -9447,7 +9472,7 @@
     {
       "path": "scripts/hall-preview/refresh-fixtures.js",
       "mode": "0000644",
-      "sha256": "3faeb959f81f32e23b11c9ab623df7899bae647c07837bca54c946e7807ef0f6"
+      "sha256": "3974f78c40edde5fd07b2e14dcb0c8ceb45e7b0bd510cafde3a0670b41421586"
     },
     {
       "path": "scripts/hall-preview/server.js",
@@ -9662,7 +9687,7 @@
     {
       "path": "src/bongos/module-scope-map.js",
       "mode": "0000644",
-      "sha256": "cfcc13ad9d554c4f6f0d8bb4df822a1e2a7f589c2bc3c2829b95b64d00f82cd0"
+      "sha256": "40f2196830c746ed440ba91b938bece8ba48fdf225285c6a6d5dccd109d47d3d"
     },
     {
       "path": "src/bongos/module-submissions.js",
@@ -9852,7 +9877,7 @@
     {
       "path": "src/module-api.js",
       "mode": "0000644",
-      "sha256": "d0494683c02dfc17a402568d4ed72ccc574b73b4813d06de8eda9ccfcafe09d9"
+      "sha256": "e5fb0cc646c7821da2c99ceb43ee9a9214399fb81b1ee26e1c9bc84ff5bff380"
     },
     {
       "path": "src/module-loader/catalog.js",
@@ -10372,7 +10397,7 @@
     {
       "path": "tests/blockers_hall.mjs",
       "mode": "0000644",
-      "sha256": "3b3b24fe066acff344af8eabee0feb6df0b4129ad688d990cfed4c8a60d9cd33"
+      "sha256": "b071e16e40b5acfeab02eb756c56ddba608d07068072b7f767737a4dcd588b68"
     },
     {
       "path": "tests/blockers_kit_pager.mjs",
@@ -12357,7 +12382,7 @@
     {
       "path": "tests/module-scope-map.mjs",
       "mode": "0000644",
-      "sha256": "4d65821ed847d364a80920b29c82cf1ee8ac06b3a8349845902e58e75cf96c7b"
+      "sha256": "0a6878a91c21b5e8c31f0c06518177969f907cb0a980733c2ec1a89f8621bcb8"
     },
     {
       "path": "tests/module_api.mjs",
@@ -13124,6 +13149,11 @@
       "mode": "0000644",
       "sha256": "b447287dca1ffe65a926715e0a5f07c0a05e3503066febf85b7f6d317b805c8f"
     },
+    {
+      "path": "tests/removal_verdict.mjs",
+      "mode": "0000644",
+      "sha256": "16017d19192929aea21956a6cf5e52fa1767e2c12a7e37c5453c17b9e83b8368"
+    },
     {
       "path": "tests/rename_history_restraint.mjs",
       "mode": "0000644",

package/clients/bongos-client/README.md

@@ -5,7 +5,7 @@ A **generated**, zero-dependency typed client for the Bongos API — produced fr
 by hand; it regenerates when the spec changes, so it can never drift from the routes.
 
 - API version: **v1** (served at `/api/bongos/v1`)
-- 401 operations across 60 resource groups
+- 403 operations across 61 resource groups
 
 ## Use it from your project
 

package/clients/bongos-client/bongos-client.global.js

@@ -802,6 +802,12 @@ function createClient(opts = {}) {
       // GET /public/versions — rank: public — GET /public/versions
       getPublicVersions: (args) => request("GET", "/public/versions", { hasBody: false }, args),
     },
+    "removalProposals": {
+      // GET /removal-proposals — rank: metic+archon — GET /removal-proposals
+      getRemovalProposals: (args) => request("GET", "/removal-proposals", { hasBody: false }, args),
+      // POST /removal-proposals/{id}/decide — rank: metic+archon — POST /removal-proposals/:id/decide
+      postRemovalProposalsIdDecide: (args) => request("POST", "/removal-proposals/{id}/decide", { hasBody: true }, args),
+    },
     "scouting": {
       // GET /scouting — rank: metic+archon — GET /scouting
       getScouting: (args) => request("GET", "/scouting", { hasBody: false }, args),

package/clients/bongos-client/index.cjs

@@ -801,6 +801,12 @@ function createClient(opts = {}) {
       // GET /public/versions — rank: public — GET /public/versions
       getPublicVersions: (args) => request("GET", "/public/versions", { hasBody: false }, args),
     },
+    "removalProposals": {
+      // GET /removal-proposals — rank: metic+archon — GET /removal-proposals
+      getRemovalProposals: (args) => request("GET", "/removal-proposals", { hasBody: false }, args),
+      // POST /removal-proposals/{id}/decide — rank: metic+archon — POST /removal-proposals/:id/decide
+      postRemovalProposalsIdDecide: (args) => request("POST", "/removal-proposals/{id}/decide", { hasBody: true }, args),
+    },
     "scouting": {
       // GET /scouting — rank: metic+archon — GET /scouting
       getScouting: (args) => request("GET", "/scouting", { hasBody: false }, args),

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

@@ -128,6 +128,7 @@ export interface GetPublicRepoInfoResponse { blob_base: unknown; tree_base: unkn
 export interface GetPublicTasksIdResponse { task: unknown }
 export interface GetPublicUptimeResponse { services: unknown }
 export interface GetPublicVersionsResponse { versions: unknown; page: PageInfo }
+export interface GetRemovalProposalsResponse { pending: unknown; count: unknown }
 export interface GetScoutingHandleResponse { sliver: unknown }
 export interface GetScoutingResponse { builders: unknown }
 export interface GetSecurityDocsResponse { docs: unknown }
@@ -372,6 +373,7 @@ export interface PostProvisioningInstancesIdGithubAppResponse { state: unknown;
 export interface PostProvisioningInstancesIdRestartResponse { ok: boolean; queued: unknown; action: unknown; status: unknown; message: unknown }
 export interface PostProvisioningInstancesIdTeardownResponse { ok: boolean; queued: unknown; action: unknown; status: unknown; superseded: unknown; message: unknown }
 export interface PostProvisioningInstancesRequest { slug: string; target_ref?: string; hosting_shape?: string; domain?: string; no_address?: boolean; tier?: string; onboard_mode?: string; type?: string; description?: string; detail?: Record<string, unknown>; modules?: string[] }
+export interface PostRemovalProposalsIdDecideRequest { verdict: string; note?: string }
 export interface PostSearchMarkRequest { chunk_id?: StringifiableId; useful?: unknown }
 export interface PostSearchRequest { expand?: unknown; q?: string; source_kind?: string; limit?: unknown }
 export interface PostSearchResponse { expand?: unknown; chunk?: unknown; query?: unknown; count?: unknown; total_full_tokens?: unknown; results?: unknown; corpus?: unknown }
@@ -1175,6 +1177,12 @@ export interface BongosClient {
     /** GET /public/versions — rank: public */
     getPublicVersions(args?: RequestArgs): Promise<GetPublicVersionsResponse>;
   };
+  "removalProposals": {
+    /** GET /removal-proposals — rank: metic+archon */
+    getRemovalProposals(args?: RequestArgs): Promise<GetRemovalProposalsResponse>;
+    /** POST /removal-proposals/{id}/decide — rank: metic+archon */
+    postRemovalProposalsIdDecide(args: RequestArgs & { body: PostRemovalProposalsIdDecideRequest }): Promise<ApiResponse>;
+  };
   "scouting": {
     /** GET /scouting — rank: metic+archon */
     getScouting(args?: RequestArgs): Promise<GetScoutingResponse>;

package/clients/bongos-client/index.mjs

@@ -798,6 +798,12 @@ export function createClient(opts = {}) {
       // GET /public/versions — rank: public — GET /public/versions
       getPublicVersions: (args) => request("GET", "/public/versions", { hasBody: false }, args),
     },
+    "removalProposals": {
+      // GET /removal-proposals — rank: metic+archon — GET /removal-proposals
+      getRemovalProposals: (args) => request("GET", "/removal-proposals", { hasBody: false }, args),
+      // POST /removal-proposals/{id}/decide — rank: metic+archon — POST /removal-proposals/:id/decide
+      postRemovalProposalsIdDecide: (args) => request("POST", "/removal-proposals/{id}/decide", { hasBody: true }, args),
+    },
     "scouting": {
       // GET /scouting — rank: metic+archon — GET /scouting
       getScouting: (args) => request("GET", "/scouting", { hasBody: false }, args),

package/docs/adr/0314-module-protection-is-per-path-not-per-module.md

@@ -111,11 +111,16 @@ new derivation mechanism. Filed separately:
   structural path test — directories under `scripts/` are territory and still
   protect), narrowing the derived set from twelve to the nine predicted below.
   Nothing was unprotected to achieve it and the path wall did not move.
-- **`builder-settings`, deliberately out of scope.** Its overlap is
-  `src/bongos/routes/me.js` caught by the blanket `src/bongos/routes/` prefix, so
-  narrowing it means either finishing the strangler move of `me.js` into
-  `modules/builder-settings/` or narrowing a blanket protected glob — a security
-  change with its own blast radius.
+- ~~**`builder-settings`, deliberately out of scope.**~~ **Resolved** by
+  [ADR 0318](0318-listing-a-file-for-task-affinity-is-not-owning-it.md)
+  ([task 1004110](https://cloudbongos.com/builders#/task/1004110)), and by neither
+  of the two routes predicted here. Its overlap was `src/bongos/routes/me.js`
+  caught by the blanket `src/bongos/routes/` prefix — but that glob was a task
+  AFFINITY listing, not an ownership claim, on a file `MODULE_GLOBS` itself
+  called a core facade. Ownership moved to `kernel`, where the aggregator
+  belongs; the blanket glob was left alone (all eighteen route files are
+  protected by it and nothing else) and no strangler move was needed (the
+  aggregator resolves ten module ports). The derived set narrows nine to eight.
 - **Nine protected paths are owned by no module at all** — `gen-repo-map.js`,
   `gen-file-map.js`, `gen-session-index.js`, `install-git-hooks.js`, `cli-lib.js`,
   `run-unit-tests.js`, `git-merge-regen.js`, `scripts/gds/hooks/` and

package/docs/adr/0318-listing-a-file-for-task-affinity-is-not-owning-it.md

@@ -0,0 +1,101 @@
+# ADR 0318 — Listing a file for task affinity is not claiming to own it
+
+- **Status:** accepted — **implemented** by [task 1004110](https://cloudbongos.com/builders#/task/1004110) (2026-09-20)
+- **Date:** 2026-09-20
+- **Task:** [task 1004110](https://cloudbongos.com/builders#/task/1004110), goal 1000095 — BONGOS-V2
+- **Extends** [ADR 0314](0314-module-protection-is-per-path-not-per-module.md), which left this case open by name.
+- **Supersedes nothing.**
+
+## The question
+
+After [ADR 0314](0314-module-protection-is-per-path-not-per-module.md), nine
+modules derive `protected` — making a goal scoped to them Archon-only to create.
+`builder-settings` was one of them, and it earned that on exactly one glob:
+`src/bongos/routes/me.js`, caught by the blanket `src/bongos/routes/` prefix in
+`PROTECTED_GLOBS`.
+
+ADR 0314 named this and left it, because clearing it looked like it needed one of
+two expensive things: finishing the strangler move of `me.js` into
+`modules/builder-settings/`, or narrowing a blanket protected glob. Both were
+scoped out. The task that picked this up was written the same way — those two
+options, and *"the choice is the deliverable"*.
+
+Both are wrong, and measuring them is what shows a third thing was actually broken.
+
+## What the measurements said
+
+**Narrowing the blanket prefix removes the only wall that exists.** All eighteen
+files under `src/bongos/routes/` are protected by that prefix *and nothing else* —
+no route file has a second protecting glob. Narrowing it unwalls `auth.js`,
+`builders.js`, `backup.js` and `core-update.js` in the same stroke. This is now
+pinned as a test rather than left as a caution, so the next reader does not have
+to re-derive it.
+
+**Moving `me.js` into `modules/builder-settings/` inverts the port architecture.**
+`GET /me` is a deliberate aggregator: it resolves **ten** module ports —
+`lifecycle`, `reward`, `onboarding`, `government`, `specialities`, `grade`,
+`box.hasEverConnected`, `art.sharedKeyConfigured`, `art.getBuilderGeminiKeyRow`,
+`discord.isLinked` — and `builder-settings` is one of the ten. Hosting it inside
+one module would mean that module resolving nine foreign ports from the inside,
+which is the `core -> module` edge [ADR 0083](0083-modular-architecture-strangler-build-plan.md)
+rule 1 exists to forbid. A core facade is precisely what prevents that.
+
+Three places already said so, in the code, before this task was written: the file
+header (*"This file kept only the read aggregation"*), `module.json` (*"the
+`GET /me` aggregator stays a thin core facade"*), and `MODULE_GLOBS` itself.
+
+## The decision
+
+**`MODULE_GLOBS` listed `src/bongos/routes/me.js` under `builder-settings` for
+task affinity — and said so in the same comment — while `isProtected()` read it
+as an ownership claim.** Affinity is a convenience for authoring; ownership is a
+statement about territory. One listing, read as the other, made a whole module
+Archon-only on the strength of a file its own comment called core.
+
+So: **ownership follows what the file is.** `src/bongos/routes/me.js` moves to
+`kernel`, which already owns `src/bongos/routes/security.js` and is the home of
+the core route surface. `builder-settings` keeps its own directory and its
+pref-mirroring CLI, and stops being protected.
+
+This is [ADR 0314](0314-module-protection-is-per-path-not-per-module.md) one step
+on. That decision said *owning the command is not owning the authority*, for a CLI
+entrypoint that merely lives near a module. The same error wearing different
+clothes: **being listed next to a module is not owning it either.** 0314 solved
+its case structurally, with a path test (`isCommandPath`). This one is solved by
+correcting the data, because there is exactly one such listing — see below.
+
+## Why not a general affinity tier
+
+The obvious generalisation is to mark affinity entries in `MODULE_GLOBS` so
+`isProtected()` skips them, mirroring `isCommandPath`. Rejected, because the
+audit does not support it. Of the nine protected modules, three others
+(`kernel`, `devsecops`, `methodology`) are protected only by paths outside their
+own directory — but in every one of those the foreign path genuinely *is* the
+domain: `kernel` **is** `src/bongos/auth.js`, `devsecops` **is** `.github/`,
+`methodology` **is** `CLAUDE.md` and `docs/`.
+
+`builder-settings` was the only module protected by a path its own source
+described as belonging elsewhere. A new tier in `MODULE_GLOBS` would be a new
+concept, and a new place for a hole to hide, built for a population of one.
+
+## Consequences
+
+- `protectedModules()` goes **9 -> 8**. `builder-settings` leaves the set.
+- **The wall that matters does not move.** This decides who may CREATE a goal
+  whose territory includes `/me`. It does not decide who may WRITE it: a
+  sub-Metic builder touching `src/bongos/routes/me.js` is still refused by
+  `checkPermissionPaths`, which the tests assert directly rather than assume.
+- A `builder-settings`-scoped goal can no longer author a task touching `/me`;
+  that needs `kernel` scope. Correct, rather than a loss — the aggregator spans
+  ten modules and belongs to none of them.
+- `src/bongos/routes/` now has **two** of eighteen files owned, up from two with
+  one of them wrong. The other sixteen remain authorable by no goal;
+  [task 1004116](https://cloudbongos.com/builders#/task/1004116) holds that
+  decision, and this change removes the builder-settings overlap that made its
+  option (a) awkward.
+
+## Not built here
+
+- **The other sixteen route files.** Still unowned, still
+  [task 1004116](https://cloudbongos.com/builders#/task/1004116). The blanket-prefix
+  tripwire added here is the measurement that task needs, landed early.

package/docs/adr/0319-a-removal-verdict-is-a-row-beside-the-question.md

@@ -0,0 +1,69 @@
+# ADR 0319 — A removal verdict is a row beside the question, because both answers close it the same way
+
+**Status:** accepted · **Date:** 2026-09-20 · **Task:** [task 1004095](https://cloudbongos.com/builders#/task/1004095) (goal 1000095 — BONGOS-V2)
+
+**Related:** [ADR 0313](0313-a-removal-is-proposed-by-the-ship-and-confirmed-by-a-person.md) (the decision of record — the system proposes, a person confirms) · [ADR 0242](0242-a-cascade-is-a-declaration-table-on-the-event-that-already-exists.md) (the runner a rule is appended to, and may not fan out) · [ADR 0299](0299-the-nod-queue-stays-scoped-to-routed-filings.md) (why the nod queue is not widened) · [ADR 0312](0312-provenance-is-a-second-ideas-owned-edge-table.md) (the descent a confirmed removal dims)
+
+## Context
+
+[ADR 0313](0313-a-removal-is-proposed-by-the-ship-and-confirmed-by-a-person.md) settled that a ship which deletes an earlier shipped task's files files a **question**, and that a person answers it: Metic+, `task.promote`, on the existing awaiting-nod surface, with an unanswered proposal rotting on the normal clock. Task 1004090 built the question. Nothing could answer it.
+
+Answering turns out to have one property that decides the whole design: **both answers close the proposal the same way.** The proposal is a question, not work — confirming leaves nothing to build, and so does dismissing. Either way the only sensible end state for that task row is `abandoned`, the ledger's one spelling of "finished with the project, not delivered" (`modules/lifecycle/task-status.js`).
+
+So a status alone cannot be the record. "Yes, that work is gone" and "no, that was a refactor" would be the same row, and brightness — the live share of a descent, the next task in this chain — would have no way to tell the star it must dim from the one it must not. ADR 0313 already ruled out the obvious alternative: a `removed` task status, because `shipped` is terminal by design and a removal is "a fact about work's fate, recorded beside it, not a new terminal state that ship rollup would have to learn."
+
+## Decision
+
+### The verdict is its own row, and there is exactly one of them per proposal
+
+`lifecycle_removal_verdicts` (migration `lifecycle_009`) holds `proposal_task_id` (**primary key**), `ship_task_id`, `verdict ∈ {confirmed, dismissed}`, `decided_by`, `decided_at`, `note`. It is the "beside it" ADR 0313 asked for. The verdict write and the status change commit in **one transaction**: a verdict with no closed task would be re-answerable, and a closed task with no verdict is precisely the erasure this exists to prevent.
+
+The primary key on `proposal_task_id` is a decision, not a default. A second answer is **refused** (`ALREADY_DECIDED`, 409), never upserted and never treated as an idempotent success, because overwriting destroys the only record that a person answered differently. The proposal row is locked `FOR UPDATE` before any of the row-scoped checks, so two people pressing Confirm and Dismiss at the same moment cannot both read "undecided"; the second loses on the refusal rather than winning on write order. Amending a verdict is deliberately not built: if it is ever needed it is a second row and an append-only history, not an UPDATE.
+
+`ALREADY_DECIDED` is checked **before** `PROPOSAL_CLOSED`, because an answered proposal is also abandoned — checking status first would tell someone "this is not an open question" when the useful answer is "it was dismissed, by builder 7, yesterday".
+
+### The verdict is what this ships; the target list is not
+
+The proposal names the affected tasks and paths as **prose in its body**, because a cascade files one task per rule per ship with no field for a target and ADR 0242 forbids widening the runner to fan out (owner decision, 2026-09-20, recorded in `cascade.js:removalProposalBody`). This ADR does not change that and does not parse it. A body is written for a person to read; a reader that silently depends on its line shape breaks the day somebody improves the wording.
+
+What brightness gets from here is structured: the verdict, and `ship_task_id` — denormalised out of the proposal's `source_ref`, which encodes it as `cascade-removal-proposed-on-ship-<id>`, a string nothing can join on (the same complaint `ideas_007` makes about the same field). Brightness designs its own storage for targets when it needs one, which is where the owner put that decision.
+
+A ref that cannot be parsed still yields an answerable proposal, with `ship_task_id` NULL. The verdict is the point; refusing to record one because a convenience column could not be filled would be the tail wagging the dog.
+
+### The proposals get their own slice on the attention card, not a row in the nod queue
+
+Spec decision 15 says "the existing awaiting-nod surface". The **surface** is the hall's one Needs-your-attention card; the **queue** is `listRoutedAwaitingNod`, which filters `origin = 'route'` on `ideas_task_lineage` and which [ADR 0299](0299-the-nod-queue-stays-scoped-to-routed-filings.md) decided — on live numbers — stays scoped to routed filings and is honestly named for that population. A removal proposal has no idea lineage at all, so widening that predicate to reach it would both break ADR 0299 and make an ideas-owned table answer a lifecycle question.
+
+So: same card, same floor, separate slice (`#attention-removals`, straight after the nod), fed by its own routes.
+
+### The permission is reused; the verb is not
+
+`GET /removal-proposals` and `POST /removal-proposals/:id/decide` both gate on the **existing** `task.promote` atom — Metic+, the same floor as the nod, so a caller who can see the queue can act on it by construction rather than by coincidence. No new permission and no new page, as spec decision 15 requires.
+
+A new *route* is nonetheless needed, and that is not a contradiction. The nod could reuse `POST /tasks/:id/promote` because promoting is exactly what a nod does; there is no existing route that means "that work is genuinely gone". `/tasks/:id/abandon` would close the question without recording which answer was given — the one thing this feature exists to produce.
+
+The path is top-level (`/removal-proposals`, the `/override-requests` precedent) rather than `/tasks/removal-proposals`, because the manifest mounts the `tasks` route file first and its `/tasks/:id` would swallow a literal single segment declared in a later file — the trap `modules/ideas/routes/inbox.js` documents for `/inbox/awaiting-nod`, avoided here by not sharing the prefix.
+
+### Rot is inherited, not rebuilt
+
+An unanswered proposal sits at `backlog`, which is in `rot.TASK_ROTTABLE_STATUSES`, so it enters the existing rot feed on the project's clock with no code written for it — spec decision 14, and why that decision had no competing option. Answering it writes `abandoned`, which is terminal and not rottable, so it leaves the feed by the same mechanism. Both halves are pinned against the rot module's own exported vocabulary rather than asserted in a comment.
+
+## Consequences
+
+**A confirmed removal still changes nothing else.** No status on the removed work moves, no credit is clawed back, `shipped` stays terminal. The verdict is a fact recorded beside the work, and brightness is the only thing that will read it.
+
+**A cascade task created before this shipped is answerable.** The predicate is `source = 'cascade'` plus the removal rule's ref prefix, both read from `cascade.js` rather than re-typed, so any proposal the rule has ever filed qualifies. In practice the set is empty: the rule could not fire in production until task 1004090's final commit.
+
+**The rot feed shows these only to the owner.** A cascade-filed task has `created_by = NULL`, and `rottingFor` addresses a null-creator row solely to a caller holding `builder.roster.read` — the core_227 convention, deliberate rather than accidental, since there is no person a system-filed row could honestly be addressed to. The attention slice is not scoped that way: it shows every open proposal to every Metic+.
+
+**A verdict cannot be corrected through the API.** Stated plainly because it will be noticed: the recovery for a mis-answered proposal is currently a row deletion by someone with SQL, and the right fix — should it ever be asked for — is an append-only amendment, not an UPDATE on this table.
+
+## Alternatives rejected
+
+- **The status alone as the record.** Both answers close the same way, so it records neither.
+- **A `removed` task status, or reusing `merged_into_task_id`.** ADR 0313 rejected the first; the second is CHECK-constrained to `abandoned` rows and describes work cut *before* it landed.
+- **Parsing the affected tasks out of the proposal body at confirm time.** Couples a machine read to prose written for a person, and the owner already placed that storage decision with brightness.
+- **Widening the nod queue to carry removal proposals.** Breaks ADR 0299 and makes an ideas-owned lineage table answer a lifecycle question.
+- **Two routes, `/confirm` and `/dismiss`.** The same act with opposite content; splitting it invites the halves to drift in what they close, record and refuse.
+- **Upserting a second verdict, or treating it as an idempotent 200.** Destroys the record that a person answered differently.
+- **A `LIKE 'prefix%'` match on `source_ref`.** A rule key may contain an underscore, and an underscore is a LIKE wildcard — a silent widening of the read that decides what may be answered.

package/docs/adr/README.md

@@ -409,3 +409,5 @@ This keeps the decision history honest and traceable.
 | 0316 | [**The ignite floor is a scheduling dial, not the trusted tier** ([task 1004084](https://cloudbongos.com/builders#/task/1004084), goal 1000095 — BONGOS-V2). BV2 decision 3 makes the ignite floor — who may turn a quick idea straight into claimable work — a per-instance setting, and decision 16 adds the descent decay rate beside it, the two to share one home. Both the spec and the seeded task described the mechanism the same way: the floor IS the `METIC_PLUS` constant in `modules/ideas/routing.js`, so this is "a setting, not a refactor". Tracing the code before building refuted that: `METIC_PLUS` is spelled once but READ for four semantically different gates — the two `decideLanding` bug branches (land at `ready` or at `backlog`), `mayProposeCriterion` (who may file a `kind='criterion-proposal'`, a planning-scope write), and the protected-scope wall in `authorizeRoutedLanding` (who may route work into the permission / ship-grade / deploy / migration core). Only the first two are the ignite floor, so making the CONSTANT configurable would mean an instance setting its floor to `xenos` — exactly the "project of one wants every thought claimable" case the owner asked for — ALSO gaining the right to file criterion-proposals and to breach the protected core. The codebase already said so in three places nobody had read into the spec: the constant's own header ("It grants nothing — the server-side rank floor and the goal's scope wall are separate, load-bearing gates"), the protected-scope branch ("the two are layers, not alternatives"), and `tests/filing_abuse_matrix.mjs`, which models the widening as an ATTACK and pins the literal. Decision: a separate dial. `modules/ideas/config.js` + `config/ideas.neutral.json` carry both knobs on the `modules/government/config.js` precedence (env -> instance root `config/ideas.json` -> core root neutral; the ADR 0268 dual-root split matters, since one root reads the host pack out of `node_modules` where `npm ci` erases it). `igniteFloor` defaults to `metic`, resolving to exactly the `METIC_PLUS` set, and is threaded into `decideLanding` as a ready-made `trustedRanks` **Set** by the callers — `routing.js` is TOLD the floor and never reads config, staying pure and DB-free — while `METIC_PLUS` stays a FIXED constant for the other two gates, neither of which takes a floor argument (pinned structurally). `descentDecayRate` defaults to 0.5 and ships with no production caller, because R11 is its intended reader and depends on the unbuilt R08 — the same deliberate slice boundary `modules/government/config.js` documents for itself, and what decision 16 asked for. Everything fails to VANILLA rather than dead: a malformed pack, an unknown rank or an out-of-band rate falls back, and an unrecognised floor yields the DEFAULT set, never an empty one (failing closed would stop every ignition on a typo). Rejected: configuring `METIC_PLUS` as written (a security widening in a config file's clothes); splitting it into four named constants (the other three want the same fixed tier, and naming them invites configuring them); having `routing.js` read the config itself (makes the landing matrix impure and untestable at a different floor). Spec decision 3's "spelled in one place" describes the intent, not the mechanism; the spec was not edited and the task description was amended in flight.](0316-the-ignite-floor-is-not-the-trusted-tier.md) | ideas / permissions |
 | 0315 | [**A plane with no proxy is refused, not given a no-op ingress** ([task 1004017](https://cloudbongos.com/builders#/task/1004017), goal 1000106 — BONGOS-V2). The piece [ADR 0306](0306-instance-supervision-is-a-seam-with-systemd-as-the-default.md) explicitly deferred: the self-host image ships no proxy, so provisioning step 6's `<slug>.caddy` snippet write and `systemctl reload caddy` cannot work there and a child instance gets no front door. **Two failure shapes, only one visible**: a DOMAINED child already half-refused, because `caddy adapt` fails with no binary and [ADR 0303](0303-provisioning-verifies-the-base-caddyfile-and-never-edits-it.md)'s own catch turns that into a gap — but the message told the operator to add a directive to `/etc/caddy/Caddyfile`, a file the container does not have and that ADR 0303 §1 forbids provisioning from creating; a DOMAINLESS child skipped that preflight entirely (it is gated on `inst.domain`), reached step 6 and died on the `sudo` write, an uncaught throw that bypasses the `{ok:false}` pending-retry path and hard-errors the instance on attempt one — a crash recorded where a refusal was the honest answer. Decision: `ingressPlaneGap(exec)` probes the plane with `caddy version` — one cheap unprivileged read, the same posture as `checkCaddyWiring` — and both standup legs refuse with `Ingress preflight failed: …`, deliberately NOT domain-gated, because the domainless child is the one 0303 could not see. **Only a missing binary proves there is no proxy**: under remote exec `boxExec` is `ssh <host> bash -s`, so an unreachable co-hosting box throws here too, and diagnosing a network blip as 'this plane has no proxy, provision elsewhere' would be a confident wrong answer that burns the intent's retry budget — exit 127 is read as proof, anything else answers 'could not confirm a reverse proxy on this plane' with the real cause leading. The three refusals are ordered **capacity → ingress → wiring**, cheapest and most fundamental first and all before any mutation, which moves 0303's preflight behind the ADR 0285 capacity measurement; both still refuse before anything changes, so only the precedence between two refusals moves. **No ingress seam and no no-op backend**, despite the obvious symmetry with 0306: a `none` implementation whose `writeSite`/`reload` are no-ops lets the standup SUCCEED while leaving the child unreachable — neither half of the task's done-when, and exactly the silently-broken instance it exists to prevent. Does not decide: what a child's front door IS on a container plane (a published port, a bundled proxy, an explicit localhost-only shape) — a future ADR that adds one replaces this refusal rather than extending it. Teardown is left alone on purpose: it already reloads `allowFail`, and refusing there would strand a row instead of cleaning it.](0315-a-plane-with-no-proxy-is-refused-not-given-a-no-op-ingress.md) | provisioning / ingress |
 | 0317 | [**A plane that cannot give an instance its own account is refused, not given a shared uid** ([task 1004018](https://cloudbongos.com/builders#/task/1004018), goal 1000106 — BONGOS-V2). The last of the three container gaps [ADR 0306](0306-instance-supervision-is-a-seam-with-systemd-as-the-default.md) deferred, and the sibling of [ADR 0315](0315-a-plane-with-no-proxy-is-refused-not-given-a-no-op-ingress.md). [ADR 0281](0281-an-instance-identity-is-its-own-unix-account-and-pg-role.md) makes an instance's identity its own unix account, and the unit's `User=`/`Group=` is what stops one co-tenant reading a sibling's `/proc/<pid>/environ` — where every instance's `EnvironmentFile` carries its GitHub App private key and OAuth client secret (audit B3). `useradd` needs uid 0; the self-host image is `node:22-bookworm-slim` running `USER node` with **no sudo**, so there the account cannot be created at all. **Two failure shapes, neither honest**: today step 1c's `boxExec(ensureInstanceUserCmd(...))` is not `allowFail`, so it throws AFTER every preflight passed, AFTER the status flip to `provisioning`, and — for a standalone — after a repo pull and an `npm ci`, recording a crash with the box half-changed; and tomorrow it goes quiet, because a compose self-host only stops short of step 1c by ADR 0315's coincidence, and 0315 says in its own consequences that a future front door **replaces** that refusal. Decision: `accountPlaneGap(exec, { privileged })` in `provision-repo.js` probes with `${sudo}sh -c 'test "$(id -u)" = 0'` and `provisionInstance` refuses with `Account preflight failed: …` before any mutation. **The probe runs the SAME escalation the mutation will** (`PROVISION_SUDO=1` renders the same `sudo ` prefix `ensureInstanceUserCmd` uses), so a pass is evidence rather than inference. **`sh -c`, not a bare `test`, is load-bearing**: under sudo the outer unprivileged shell would expand `$(id -u)` first and answer about the wrong user, passing on exactly the plane this refuses — and for the same reason there is no pipeline, whose exit status is its last stage's. **Only a shell that ran and answered proves it**: `boxExec` is `ssh <host> bash -s` under remote exec, so exit 1 (`test` said no) and 127 (no sudo binary) are read as proof while ssh's own 255 answers "could not confirm" with the real cause leading — ADR 0315's rule applied to a different question. Ordered **third**, after capacity and ingress and before 0303's wiring check: the first three ask about the PLANE, 0303 asks about this instance's DOMAIN, and 0315's order is extended rather than rearranged. **Rejected: accepting it** — documenting a self-host container as single-tenant with a shared uid is a silent downgrade of the vector 0281 closed, observable nowhere on the running box, and "single-tenant" is not what a container hosting several child projects is; **an identity seam with a container implementation**, because nothing exists to put behind it and a seam whose second backend does nothing is 0315's no-op wearing a seam's clothes; **probing `useradd --help` / `command -v useradd`**, which succeed unprivileged on the very image this refuses; **`${sudo}id -u` compared against `0`**, which decides on captured stdout where every sibling preflight and every test fake treats exit status as the contract; and **refusing inside step 1c**, which keeps the refusal after the status flip. Not covered, deliberately: root-but-no-`useradd` (an Alpine-style plane fails loudly at step 1c as today), and teardown (0315's reason — a refusal there strands a row instead of cleaning it). No `PROVISION_ALLOW_SHARED_UID`: a runner either reaches root on this plane or it does not.](0317-a-plane-that-cannot-give-an-instance-its-own-account-is-refused.md) | provisioning / identity |
+| 0319 | [**A removal verdict is a row beside the question, because both answers close it the same way** ([task 1004095](https://cloudbongos.com/builders#/task/1004095), goal 1000095 — BONGOS-V2). [ADR 0313](0313-a-removal-is-proposed-by-the-ship-and-confirmed-by-a-person.md) settled that a ship deleting an earlier shipped task’s files files a QUESTION and a person answers it; task 1004090 built the question and nothing could answer it. Building the answer surfaced the property that decides the design: a proposal is a question, not work, so CONFIRMING and DISMISSING both leave nothing to build and both end the task at `abandoned` — meaning a status alone records neither, and brightness could not tell the star it must dim from the one it must not. ADR 0313 had already rejected the obvious alternative (a `removed` status; `shipped` is terminal and much of the ledger leans on it — a removal is a fact recorded BESIDE work, not a new terminal state). Decision: `lifecycle_removal_verdicts` (migration `lifecycle_009`), PRIMARY KEY on `proposal_task_id` so one proposal holds one answer ever — a second decide is REFUSED (409), never upserted and never an idempotent 200, because overwriting destroys the record that a person answered differently; the row is locked `FOR UPDATE` first, so simultaneous Confirm and Dismiss cannot both read “undecided”, and `ALREADY_DECIDED` is checked BEFORE `PROPOSAL_CLOSED` because an answered proposal is also abandoned and the useful message is the one naming the earlier verdict. The verdict and the status change commit in ONE transaction. What this does NOT ship is the target list: the affected tasks and paths stay PROSE in the proposal body (the owner’s 2026-09-20 decision, since [ADR 0242](0242-a-cascade-is-a-declaration-table-on-the-event-that-already-exists.md) forbids widening the runner to fan out), and nothing here parses it — brightness designs that storage. What brightness does get is structured: the verdict plus `ship_task_id`, denormalised out of the `source_ref` that encodes it as a string nothing can join on. Surface: spec decision 15’s “existing awaiting-nod surface” is the CARD, not the QUEUE — [ADR 0299](0299-the-nod-queue-stays-scoped-to-routed-filings.md) keeps that queue scoped to routed filings and a removal proposal has no idea lineage at all, so it gets its own slice on the same card at the same floor. The PERMISSION is reused (`task.promote`, Metic+, read and write both) and the VERB is not: no existing route means “that work is genuinely gone”, and `/tasks/:id/abandon` would close the question without recording which answer was given. Top-level `/removal-proposals` rather than `/tasks/removal-proposals`, because the manifest mounts `tasks` first and its `/tasks/:id` swallows a later file’s literal segment. Rot is INHERITED: `backlog` is rottable and `abandoned` is not, so an unanswered proposal rots and an answered one leaves the feed with no code written for either — pinned against the rot module’s own exported vocabulary. Rejected: the status as the record; parsing the body at confirm time; widening the nod queue; separate `/confirm` and `/dismiss` routes; upserting a second verdict; a `LIKE ‘prefix%’` match (a rule key may contain an underscore, which is a LIKE wildcard).](0319-a-removal-verdict-is-a-row-beside-the-question.md) | ideas / lifecycle |
+| 0318 | [**Listing a file for task affinity is not claiming to own it** ([task 1004110](https://cloudbongos.com/builders#/task/1004110), goal 1000095 — BONGOS-V2). The case [ADR 0314](0314-module-protection-is-per-path-not-per-module.md) named and left open, closed by neither of the two routes it predicted. `builder-settings` derived `protected` — Archon-only to scope a goal to — on exactly one glob, `src/bongos/routes/me.js`, caught by the blanket `src/bongos/routes/` prefix. **That glob was never an ownership claim:** `MODULE_GLOBS` listed it for task AFFINITY and said in the same comment that the `GET /me` aggregator stays a thin core facade, and `isProtected()` cannot tell the two apart. **Both predicted routes were measured and rejected.** Narrowing the blanket prefix: all eighteen files under `src/bongos/routes/` are protected by that prefix AND NOTHING ELSE, so narrowing unwalls `auth.js`, `builders.js`, `backup.js` and `core-update.js` together — now pinned as a tripwire test rather than left as a caution. Moving `me.js` into `modules/builder-settings/`: the aggregator resolves TEN module ports (`lifecycle`, `reward`, `onboarding`, `government`, `specialities`, `grade`, `box`, `art` ×2, `discord`) and `builder-settings` is one of them, so hosting it inside one module means resolving nine foreign ports from the inside — the `core -> module` edge [ADR 0083](0083-modular-architecture-strangler-build-plan.md) rule 1 forbids. Decision: **ownership follows what the file is** — `me.js` moves to `kernel`, which already owns `src/bongos/routes/security.js`. This is 0314 one step on: owning the command is not owning the authority, and **being listed next to a module is not owning it either**. **Rejected: a general affinity tier** in `MODULE_GLOBS` mirroring `isCommandPath` — the audit does not support it. Three other modules (`kernel`, `devsecops`, `methodology`) are also protected only by paths outside their own directory, but in each the foreign path genuinely IS the domain; `builder-settings` was the only module protected by a path its own source called core, so a new tier would be a new place for a hole to hide, built for a population of one. `protectedModules()` goes 9 -> 8. **The wall that matters does not move:** a sub-Metic builder touching `/me` is still refused by `checkPermissionPaths`, asserted directly rather than assumed. The sixteen still-unowned route files remain [task 1004116](https://cloudbongos.com/builders#/task/1004116), whose option (a) this de-risks.](0318-listing-a-file-for-task-affinity-is-not-owning-it.md) | permissions / module scope |