@cohortapp/agent-sdk 2.10.0 → 2.11.0

package/.claude/commands/init-maestro.md

@@ -396,13 +396,20 @@ Do NOT modify these sections (keep them exactly as they are, except for agent na
 
    h. **`scripts/daemon/responder.mjs` `FALLBACK_PREAMBLE`** — System prompt that introduces the agent to Claude. Identity intro line must reference the new agent. Preserve the operational rules.
 
-   i. **`scripts/daemon/prompt-builder.mjs` `FALLBACK_PREAMBLE`** — Same treatment.
-
-   j. **`scripts/daemon/classifier.mjs` `SYSTEM_PROMPT`** — Identity intro line. Preserve everything else.
-
-   k. **`scripts/huddle/huddle-server.mjs` `HUDDLE_SYSTEM_PROMPT`** — Voice agent identity line.
-
-   l. **`scripts/spawn-session.sh`** — Sub-session bootstrap prompt that names the agent.
+   > **NO LONGER A MANUAL STEP — these four now read config and must NOT be hand-edited.**
+   > `scripts/daemon/prompt-builder.mjs` (`buildFallbackPreamble`), `scripts/daemon/classifier.mjs`
+   > (`renderClassifierIdentityLine`), `scripts/huddle/huddle-server.mjs`
+   > (`renderHuddleIdentityLine` + `renderHuddleCompanyBlock`) and `scripts/spawn-session.sh`
+   > (sources `config/agent.env`) all render identity, employer and — for the preamble — AUTHORITY
+   > from `config/agent.json`, `config/company.json` and `policies/action-classification.yaml`,
+   > omitting any clause whose field is unset or `UNCONFIGURED`. Editing the literals back in
+   > re-creates the fabrication. If one of them prints the wrong company, fix the CONFIG.
+   >
+   > (Previously items i, j, k and l. Item k asked only for the huddle "Voice agent identity
+   > line" and never mentioned the `ABOUT <COMPANY>:` block six lines below it — which described
+   > a second, different fictional company and was spoken aloud on auto-joined huddles. That
+   > block is now `renderHuddleCompanyBlock(config/company.json)` and emits NOTHING when the
+   > company config is empty.)
 
    m. **`scripts/continuous-monitor.sh`** — Channel monitor agent prompt.
 
@@ -412,9 +419,9 @@ Do NOT modify these sections (keep them exactly as they are, except for agent na
 
    p. **`scripts/rag-indexer.py`, `scripts/user-context-search.py`** — Author docstring at the top. Set to the new agent's full name.
 
-   q. **`scripts/validate-outbound.py`** — Test/regex references to the placeholder agent name "Robin Hayes" or `lookup_entity("Robin Hayes")`. Replace with the new agent's full name. Leave the generic third-party pronoun regex (around line 1007) UNCHANGED — it's a detector, not an identity reference.
+   q. **`scripts/validate_outbound.py`** — ONLY the embedded `--self-test` harness at the bottom, whose fixtures look up example people in the entity index. Everything on the production path (the employer entity-id set, the possessive-claim regex, the AI-self-disclosure business exceptions) now resolves from `config/company.json` at load and must NOT be hand-edited. Leave the generic third-party pronoun regex UNCHANGED — it's a detector, not an identity reference.
 
-   **Verification step (identity AND company):** After rewrites, run `grep -rniE "robin|alex|jordan|northwind" scripts/ config/ agents/ policies/ 2>&1` and confirm NO placeholder identity remains — neither the placeholder persona (Robin / Alex) NOR the placeholder company ("Northwind"). Everything must be the new agent + the company from `config/company.json`. Report any remaining matches you cannot safely auto-resolve so the main agent can decide.
+   **Verification step (identity AND company):** After rewrites, run `node scripts/ci/check-no-residual-identity.mjs` — it now FAILS on fictional placeholder identity anywhere under `scripts/`, `lib/`, `policies/`, `agents/`, `bin/`, `services/` and friends (tests, fixtures, `docs/`, `scaffold/` and `*.example` are exempt by construction, and the remaining known-dirty files are printed from `PLACEHOLDER_PENDING`). Then run `grep -rniE "robin|alex|jordan|northwind" scripts/ config/ agents/ policies/ 2>&1` for anything the guard's patterns do not cover, and confirm NO placeholder identity remains — neither the placeholder persona (Robin / Alex) NOR the placeholder company ("Northwind"). Everything must be the new agent + the company from `config/company.json`. Report any remaining matches you cannot safely auto-resolve so the main agent can decide.
 
 ### Sub-agent 5: Update agent definitions
 

package/docs/guides/mac-mini.md

@@ -48,10 +48,20 @@ Two lanes — pick one:
   pair it to the member, then:
 
   ```bash
-  export COHORT_API_KEY=nlk_…  COHORT_ORG_ID=<org-slug>  COHORT_AGENT_ID=<member-slug>
+  export COHORT_API_KEY=nlk_…  COHORT_ORG_ID=<org-ID>  COHORT_AGENT_ID=<member-slug>
   cohort setup
   ```
 
+  > **`COHORT_ORG_ID` is the org's ID, not its slug** — this line said
+  > `<org-slug>` and that would 401 every call. The value rides as `x-org-id`
+  > (`lib/org/client.mjs#baseHeaders`) and hq compares it with strict equality
+  > against the key's own `Org.id`
+  > (`src/server/auth/org-api-key.ts:163` — no slug fallback, no normalisation).
+  > For Adaptic the two differ: the ID is `org_default_adaptic`, the slug is
+  > `adaptic`. `COHORT_AGENT_ID` **is** a slug (`A001`, `A038`) — the two
+  > variables sitting side by side take different kinds of identifier, which is
+  > exactly why this was easy to get wrong.
+
   Pull-enrollment populates `config/agent.json` from the member profile and
   writes `config/org.yaml` (`org.cohort.{enabled,base,orgId,token}`).
 

package/docs/runbooks/cohort-cutover.md

@@ -55,6 +55,22 @@ machine's `config/org.yaml` pins `server.url` (e.g.
 service changes the `*.up.railway.app` host and strands the fleet. Move the
 fleet to a stable custom domain first (§2), then rename freely.
 
+> ⚠︎ **2026-08-16 — this warning appears to have come true, and it is unresolved.**
+> `https://neolith.up.railway.app` is now UNROUTED: Railway's edge returns
+> `x-railway-fallback: true` with a 404 on `/`, `/v1` and `/v1/ops`, meaning no
+> service is attached to that hostname. Contrast the app, whose rename DID
+> retain its old host — `cohort-app` still answers on
+> `neolith-app-production.up.railway.app`. So the hq-side rename was safe and
+> this one was not.
+>
+> Any fleet machine still pinning that URL is talking to nothing, and
+> `DEPLOYMENT.md` §5.1 was handing the dead host to every new agent as its setup
+> template until this was found. The replacement host was NOT determinable from
+> either repo, from `cohort-os` (the org server does not live there), or from the
+> app's env — a separate Railway project `neolith-production` still exists in the
+> workspace and is the first place to look. Establish the real host, fix §5.1,
+> and sweep every `config/org.yaml` before assuming the fleet is healthy.
+
 ---
 
 ## 2. Custom domain for the org server

package/lib/mcp/server.test.mjs

@@ -154,19 +154,31 @@ test("tools/list: full active surface (email tools present — family is vendore
   // engage_colleagues is the judged version of that; work_track puts the ask on
   // the board and moves it. The line above is the real invariant — this one just
   // pins the number so a silent table change is visible in review.
-  assert.equal(tools.length, 122, "email + artifact + desk families vendored → 122 tools");
+  // 122 → 133: the voice delta (messaging_send_voice_note) plus the mandate /
+  // sub-agent-registry / preference delta — ten curated tools for three
+  // protocol families that were declared, implemented on hq, and curated
+  // NOWHERE, so this transport served them only through the admin-tier
+  // `org_rpc` hatch. One table, two transports: they appear here for free.
+  // 133 → 141: the venture-deliverable desk. OrgResource — a venture's own
+  // catalogue of the artifacts it has produced — was reachable from NO agent
+  // code path in either plane, so the venture's own colleagues could not list,
+  // add, correct, reorder or remove one of their deliverables. Unlike every
+  // other desk block, these eight are GENERATED from the vendored protocol
+  // declaration (lib/org/resource-tools.mjs), so this transport gets them, and
+  // every future resource method, without a second hand-written table.
+  assert.equal(tools.length, 141, "email + artifact + desk families vendored → 141 tools");
   const names = tools.map((t) => t.name);
-  for (const expected of ["org_whoami", "org_describe", "org_rpc", "org_read", "messaging_send", "task_assign", "board_ready", "email_send", "email_inbox", "artifact_create", "artifact_act", "artifact_catalog", "email_mailboxes", "email_draft_send", "files_list", "calendar_find_a_time", "crm_list_deals", "books_reports", "meetings_recap_file"]) {
+  for (const expected of ["org_whoami", "org_describe", "org_rpc", "org_read", "messaging_send", "task_assign", "board_ready", "email_send", "email_inbox", "artifact_create", "artifact_act", "artifact_catalog", "email_mailboxes", "email_draft_send", "files_list", "calendar_find_a_time", "crm_list_deals", "books_reports", "meetings_recap_file", "resource_list", "resource_attach_file"]) {
     assert.ok(names.includes(expected), `${expected} listed`);
   }
   assert.ok(tools.every((t) => t.inputSchema && t.inputSchema.type === "object"));
   h.server.stop();
 });
 
-test("tools/list honours the email gate (emailAvailable:false → 117 tools)", async () => {
+test("tools/list honours the email gate (emailAvailable:false → 136 tools)", async () => {
   const h = harness({ emailAvailable: false });
   const r = await h.request("tools/list", {});
-  assert.equal(r.result.tools.length, 117, "the 5 own-mailbox email tools drop out");
+  assert.equal(r.result.tools.length, 136, "the 5 own-mailbox email tools drop out");
   const names = new Set(r.result.tools.map((t) => t.name));
   // The five own-mailbox tools (email:true) are gated out …
   for (const gated of ["email_send", "email_inbox", "email_message", "email_thread", "email_mark_read"]) {

package/lib/org/client.mjs

@@ -109,9 +109,18 @@ export function isEnabled(cfg) {
  * Distil the org client config from an agent config object. Resolves:
  *   - base:   the server origin for the /v1 binding (explicit `org.cohort.base`,
  *             else derived from `apiUrl` [+ `orgId` path] for back-compat).
- *   - orgId:  the org slug — config `org.cohort.orgId` else COHORT_ORG_ID env
+ *   - orgId:  the org's ID — config `org.cohort.orgId` else COHORT_ORG_ID env
  *             (hq's documented var). Used by the legacy directory-path derivation
  *             and, when known, sent as the `x-org-id` pin header (defence-in-depth).
+ *
+ *             NOT THE SLUG, though this said "the org slug" until 2026-08-21 and
+ *             `docs/guides/mac-mini.md` told operators to export one. hq compares
+ *             the pin with STRICT EQUALITY against the key's `Org.id`
+ *             (`src/server/auth/org-api-key.ts:163`) — no slug fallback — so a
+ *             slug here 401s every call. The two are not interchangeable: the
+ *             ID has the form `org_default_<slug>` (e.g. slug `acme` → ID
+ *             `org_default_acme`), never the bare slug. Note `COHORT_AGENT_ID`
+ *             beside it genuinely IS a slug.
  *   - token:  bearer credential — the RAW OrgApiKey. Resolution order:
  *             config `token` → COHORT_API_TOKEN → COHORT_TOKEN → COHORT_API_KEY.
  *             hq's auth doc names the agent var COHORT_API_KEY; the older
@@ -1314,6 +1323,54 @@ export function messagingSend(params, o = {}) {
   return call("messaging.send", params || {}, o);
 }
 
+/**
+ * Ask hq who — if anyone — should respond to a message in a channel
+ * (messaging.electResponder). This is the SHOULD-I-RESPOND decision, moved off
+ * the daemon and onto hq's `routeResponders`, which for an undirected group
+ * message elects exactly ONE responder or NONE, and already fails safe (no model
+ * → quiet). hq derives the roster + trigger server-side from just
+ * `{messageId, channelId}`, org-scoped, computes the verdict ONCE per messageId
+ * and caches it in a durable ledger event, so concurrent daemons read the same
+ * election (the loser of a race reads the winner).
+ *
+ * Read-style: agent-tier `messaging.read` scope (any paired seat may ask),
+ * `sideEffecting:false` — no client idempotency key, and the server owns the
+ * write-once ledger append. Returns a res frame whose `result` is
+ * `{ election, mode, responders:[{slug,dimension}], deferredToHuman }`.
+ *
+ * FAIL-OPEN AT THE TRANSPORT ONLY: an unreachable/disabled server yields an
+ * error frame, never a throw. The CALLER owns the fail-SAFE inversion — for an
+ * ambient channel, "no verdict / not me" means STAY SILENT, never respond-to-all.
+ *
+ * @param {{messageId:string, channelId:string}} params
+ * @param {object} [o] { base, token, orgId?, fetchImpl? }
+ */
+export function electResponder(params, o = {}) {
+  return call("messaging.electResponder", params || {}, o);
+}
+
+/**
+ * Record a voice note in THIS seat's own designed voice
+ * (messaging.synthesizeVoiceNote) and return the READY `{fileId, durationMs,
+ * sizeBytes}` to attach.
+ *
+ * This is the RECORD half only. Posting is an ordinary `messagingSend` with
+ * `attachments:[{fileId}]` — hq deliberately keeps the two apart because
+ * synthesis is a provider round-trip that cannot ride its transactional send
+ * lane, and because a spoken message must be an ordinary message with a file on
+ * it rather than a second send path with its own governance.
+ *
+ * Refusals come back as error frames naming the cause (no synthesis key on the
+ * deployment, this seat has no designed voice, the hourly recording cap). Relay
+ * the cause — never claim a voice note was sent when the frame was not ok.
+ *
+ * `messaging_send_voice_note` (tool-surface) composes both halves into one verb.
+ * @param {{text:string}} params
+ */
+export function messagingSynthesizeVoiceNote(params, o = {}) {
+  return call("messaging.synthesizeVoiceNote", params || {}, o);
+}
+
 /** React to an org message (messaging.react). */
 export function messagingReact(params, o = {}) {
   return call("messaging.react", params || {}, o);

package/lib/org/protocol.checksum

@@ -1 +1 @@
-9ecd8993a6a9aceac04da479c6626a3b3852378b81bfd2b7590d2eee2099c9a9
+b2cbf124c99800a0ad1b19d7aea6a88c3c72f07b53838eb44ef6f82d888fda43

package/lib/org/protocol.mjs

@@ -95,6 +95,15 @@ export const FAMILIES = Object.freeze([
   // because the same surface outlives the run — the Org › Architecture view
   // reads this state for a workspace that has long since committed.
   "architecture",
+  // RESOURCE (2026-08): the venture-deliverable catalogue — `OrgResource`, the
+  // workspace's own index of what it has to show for itself (site, deck,
+  // one-pager, memo, brand book, film, brand assets, repo). The table has been
+  // written by the portal and rendered by `/resources` since the three-tier
+  // workforce migration and was reachable from NO agent code path at all: zero
+  // hits across hq's methods/, mcp/ and llm-responder/ trees, so the venture's
+  // own colleagues could not list, add, correct, reorder or remove one of
+  // their own deliverables. This family is that surface.
+  "resource",
 ]);
 
 /**
@@ -311,7 +320,35 @@ export const METHODS = Object.freeze({
   //     the transactional lane. Still messaging.write scope: faking "X is
   //     composing" in a room is a social write a read-only key must not have. ---
   "messaging.typing": { family: "messaging", scope: "messaging.write", sideEffecting: false },
+  // --- messaging.synthesizeVoiceNote (2026-08): a colleague SPEAKS when asked
+  //     to. hq could already synthesise an agent's voice note, but only as a
+  //     reflex — it answered a HUMAN's spoken note in kind and nothing else —
+  //     so an agent asked in TEXT ("send me a voicenote with this update")
+  //     truthfully answered that it could not. This is the verb that makes the
+  //     ability reachable: it records the acting seat's OWN designed voice and
+  //     returns the READY fileId, which `messaging.send` then attaches like any
+  //     other file (same ACL, same outbound gate, same redacted audit row — no
+  //     parallel send path). Split in two deliberately: synthesis is a provider
+  //     round-trip with a 20s timeout and cannot ride hq's 5s transactional
+  //     lane, so this half is sideEffecting:false and self-audits its own
+  //     `files`/`media.voice.synthesized` chain row, exactly as `books.ask`
+  //     does for its model call. messaging.write scope, not read: putting words
+  //     in a named colleague's mouth is a social write of the first order. ---
+  "messaging.synthesizeVoiceNote": { family: "messaging", scope: "messaging.write", sideEffecting: false },
   "messaging.channels": { family: "messaging", scope: "messaging.read", sideEffecting: false },
+  // --- messaging.electResponder (2026-08): the SERVER-SIDE "should anyone answer,
+  //     and who?" election for a multi-participant channel. A fleet daemon calls it
+  //     with just {messageId, channelId}; hq assembles the RouteInput server-side
+  //     (roster/trigger/channel, org from the KEY) and runs the SAME response
+  //     planner the in-process responder uses, returning ONE verdict every seat
+  //     converges on — replacing each daemon's local, room-blind directed_at_agent
+  //     gate. messaging.read scope (every paired seat may ask; in DEFAULT_AGENT_
+  //     SCOPES). Declared sideEffecting:false though it appends: the verdict is a
+  //     write-once ledger event ("responder"/"responder.election", keyed on
+  //     messageId) and a CACHE HIT must return with ZERO appends — which the
+  //     side-effecting exactly-one-append contract forbids — so it self-audits its
+  //     own chain row like messaging.synthesizeVoiceNote and books.ask do. ---
+  "messaging.electResponder": { family: "messaging", scope: "messaging.read", sideEffecting: false },
   // --- calling (SP3): call lifecycle in the human app. NOT reserved-admin. ---
   "calling.start": { family: "calling", scope: "calling.write", sideEffecting: true },
   "calling.join": { family: "calling", scope: "calling.write", sideEffecting: true },
@@ -1008,6 +1045,67 @@ export const METHODS = Object.freeze({
   "architecture.status": { family: "architecture", scope: "org.read", sideEffecting: false },
   "architecture.accept": { family: "architecture", scope: "org.write", sideEffecting: true, idempotent: true },
   "architecture.approve": { family: "architecture", scope: "org.write", sideEffecting: true, idempotent: true },
+  // --- resource (2026-08): THE VENTURE-DELIVERABLE CATALOGUE. `OrgResource` is
+  //     the org-scoped index of a venture's own artifacts — one row per
+  //     deliverable, keyed `(orgId, slug)`, provisioned by the portal
+  //     (`source:"ftlab-portal"`), by Genesis, by the artifact ingest, or by
+  //     hand. Eight methods: list/get (reads) and create/update/delete/reorder
+  //     + attachFile/detachFile (writes).
+  //
+  //     SCOPES REUSE `org.read` / `org.write` rather than minting a
+  //     `resource.*` pair — the subagent/genesis precedent, and here it is also
+  //     the whole ACCESS-LEVEL point. A catalogue card is org-structural
+  //     authored content exactly like a persona, an SOP or an annotation, which
+  //     is what `org.write` already names; `org.read` is in hq's VIEWER tier
+  //     (src/server/auth/role-scopes.ts) and both are in DEFAULT_AGENT_SCOPES.
+  //     So on the day these descriptors land, every seat that exists can READ
+  //     its venture's catalogue and every EDITOR seat can maintain it, with no
+  //     key reminted and no tier table edited. A private scope pair would have
+  //     to be threaded through SCOPES, DEFAULT_AGENT_SCOPES and the VIEWER tier
+  //     before ONE existing credential could reach the family — which is the
+  //     same unreachable-on-arrival failure this declaration exists to end.
+  //     (`org.write` is deliberately NOT in hq's HUMAN_DEFAULT_SCOPES: the
+  //     human mobile bearer is intentionally narrower than an agent, and the
+  //     founder's own catalogue editing runs through the web app's server
+  //     actions under `requireOrgContext()`, never this bearer.)
+  //
+  //     THE FILES BRIDGE IS A POINTER, NOT A SECOND DRIVE. The artifact ingest
+  //     files a venture's artifacts as real `WorkspaceFile` rows and stamps
+  //     `OrgResource.fileId`. `resource.*` returns that id and the card's own
+  //     columns and NOTHING derived from the drive row — no bytes, no content,
+  //     no name, size, version or share list. That is a share boundary, not
+  //     tidiness: the catalogue is ORG-WIDE under `org.read` while the drive is
+  //     SEAT-scoped by `driveVisibilityWhere` (hq methods/files/list.ts), so a
+  //     `resource.*` that re-served file content would be a one-call bypass of
+  //     the share filter — the exact defect that handler's docblock warns
+  //     about. A card is a citation; `files.get` / `files.docRead` /
+  //     `files.exportRequest` are the retrieval path and already exist.
+  //     `resource.attachFile` is the ONE place the families touch, and it
+  //     resolves the file through the drive's own `getFileOrThrow` (org pin +
+  //     `canSeeDriveFile`, NOT_FOUND either way) so it can neither cite another
+  //     tenant's file nor act as an existence oracle for one this seat cannot
+  //     see. `files.uploadRegister`'s `.strict()` schema is untouched.
+  //
+  //     TENANCY, twice over. Slug-addressed rows go through the compound unique
+  //     `orgId_slug` — the tenant is PART OF THE KEY, so another org's card is
+  //     unaddressable. Id-addressed rows go through `ctx.scopeWhere({ id })` on
+  //     findFirst/updateMany/deleteMany, never `findUnique({ where: { id } })`,
+  //     which would cross tenants.
+  //
+  //     Writes are `sideEffecting:true` and append exactly ONE chain event each
+  //     under `family:"resource"`; `idempotent:true` is opt-in at the caller.
+  //     `resource.delete` removes the CARD only — the `WorkspaceFile` keeps its
+  //     own 30-day soft-delete lane, which is why `fileId` is a plain String
+  //     and not a relation (schema.prisma: a cascade would lose the record that
+  //     the venture ever had a deck). ---
+  "resource.list": { family: "resource", scope: "org.read", sideEffecting: false },
+  "resource.get": { family: "resource", scope: "org.read", sideEffecting: false },
+  "resource.create": { family: "resource", scope: "org.write", sideEffecting: true, idempotent: true },
+  "resource.update": { family: "resource", scope: "org.write", sideEffecting: true, idempotent: true },
+  "resource.delete": { family: "resource", scope: "org.write", sideEffecting: true, idempotent: true },
+  "resource.reorder": { family: "resource", scope: "org.write", sideEffecting: true, idempotent: true },
+  "resource.attachFile": { family: "resource", scope: "org.write", sideEffecting: true, idempotent: true },
+  "resource.detachFile": { family: "resource", scope: "org.write", sideEffecting: true, idempotent: true },
 });
 
 /**

package/lib/org/protocol.test.mjs

@@ -139,7 +139,11 @@ test("protocol: frozen family + method counts (additive evolution guard)", () =>
   // and architecture (the four tier review decisions and the one whole-
   // architecture approval, which outlive the run as the Org › Architecture
   // view) → 53.
-  assert.equal(FAMILIES.length, 53, "family count");
+  // The 2026-08 venture-deliverable pass adds 1: resource (the OrgResource
+  // catalogue — a venture's own deliverables). The table predates every agent
+  // plane and was reachable from none of them, so a venture's colleagues could
+  // not list, add, correct, reorder or remove one of their own artifacts → 54.
+  assert.equal(FAMILIES.length, 54, "family count");
   // 357 = the mesh-protocol + agent UI-parity + calling + branding + email
   // methods, plus the Live Integrations surface: integration.toolsetVersion +
   // integration.listAgentTools (SP1) and integration.invokeTool (SP5, execute a
@@ -188,7 +192,20 @@ test("protocol: frozen family + method counts (additive evolution guard)", () =>
   // had shipped WITHOUT descriptors, which made all 13 unreachable — dispatch
   // rejects unknown methods and scopeForMethod resolves them to `admin`, which
   // no principal holds → 474.
-  assert.equal(Object.keys(METHODS).length, 474, "method count");
+  // The 2026-08 voice-capability pass adds 1: messaging.synthesizeVoiceNote —
+  // hq could always synthesise a colleague's voice note but only as a REFLEX
+  // (answering a human's spoken note in kind), so an agent asked in text for a
+  // voice note truthfully answered that it could not. This is the verb that
+  // makes it askable on every plane; the POST stays plain messaging.send → 475.
+  // The 2026-08 venture-deliverable pass adds 8: resource.list/get (reads) and
+  // resource.create/update/delete/reorder/attachFile/detachFile (writes). Both
+  // reads ride `org.read` and every write `org.write`, so the family is
+  // reachable by the VIEWER and EDITOR tiers that already exist rather than by
+  // a scope nobody has been minted. attachFile/detachFile are the ONLY bridge
+  // to `files.*`: a card carries a fileId POINTER and the drive keeps its own
+  // seat-scoped read surface → 483. Then +1: messaging.electResponder (the
+  // fleet's server-side respond-election) → 484.
+  assert.equal(Object.keys(METHODS).length, 484, "method count");
 });
 
 test("protocol SP3: messaging + calling families/methods/scopes", async () => {