@blamejs/core 0.13.14 → 0.13.16

package/CHANGELOG.md

@@ -8,6 +8,10 @@ upgrading across more than a few patches at a time.
 
 ## v0.13.x
 
+- v0.13.16 (2026-05-27) — **`b.mail.agent` docs now describe the facade accurately, and not-yet-wired verbs point to the primitive to use.** b.mail.agent's module documentation claimed it was "the standardization contract for every mail protocol" that JMAP / IMAP / POP3 all route through — but no protocol server actually dispatches through the agent (the framework's own JMAP EmailSubmission handler composes b.mail.send.deliver directly), and the compose / send / reply / forward, sieve.list / sieve.activate, identity / vacation / mdn.* and export / job / import verbs throw mail-agent/not-implemented. The docs are corrected to describe what the agent is: a mailbox-access facade (RBAC + posture + audit + dispatch around a mail store) whose read surface plus the mailbox-mutation and Sieve-upload methods are wired, with the remaining verbs not yet routed through it. Those verbs' error message now names the underlying primitive to compose directly (b.mail.send.deliver, b.mail.sieve, b.mailMdn, …) instead of citing a version tag that had long passed. The public WIRED_AT export (a method→version map that no longer reflected reality) is replaced by COMPOSE_HINT (a method→primitive-to-compose map). No behaviour change: the same methods are wired or throw exactly as before. **Changed:** *`b.mail.agent` documentation corrected; not-implemented errors point to the primitive to compose* — The `@module` / `@card` no longer claim the agent is the universal protocol-dispatch contract — it's documented as a mailbox-access facade with a wired read + mutation + Sieve-upload surface, and the compose/send/identity/vacation/MDN/export verbs documented as not yet routed through it (compose the underlying primitive directly until a protocol server adopts the agent). The `mail-agent/not-implemented` error now names that primitive (e.g. `b.mail.send.deliver`) rather than a passed version tag. **Removed:** *`b.mail.agent.WIRED_AT` export replaced by `COMPOSE_HINT`* — The `WIRED_AT` export mapped each method to a framework version that was supposed to "light it up" — versions that have all shipped without the wiring, so the map was misleading. It is replaced by `COMPOSE_HINT`, mapping each not-yet-wired method to the primitive an operator composes directly. Operators reading `b.mail.agent.WIRED_AT` should read `b.mail.agent.COMPOSE_HINT` instead (pre-1.0: no compatibility shim).
+
+- v0.13.15 (2026-05-27) — **Corrected more source citations and made deferred/reserved options honest in their docs.** A second accuracy pass over source threat-annotations and option docs. Three citation corrections: the base64url strict-decode guard cited CVE-2022-0235 (which is actually a node-fetch cookie-leak, unrelated) — it now names the weakness class it defends (CWE-347 / CWE-1286 signature canonicalization); the glob consecutive-wildcard ReDoS cap cited the wrong library (the CVE-2026-26996 ReDoS is minimatch, not picomatch — the adjacent picomatch one is CVE-2026-33671); and CVE-2026-32178 is reframed to the CWE-138 header-injection-spoofing class the public record actually documents (and dropped from the end-of-data SMTP-smuggling list, which is a different class). Several options/statuses are now honest about not-yet-implemented surface: b.archive.read.zip.fromTrustedStream is marked experimental (its methods throw and its options aren't honored yet — the example now shows the supported buffer-then-random-access path); b.acme revokeCert's useCertKey / certPrivateKey are marked reserved (the cert-key path throws; account-key signing is the supported default); and a stale message claiming passkey break-glass factors were a future feature is removed (passkeys are a live allowed factor). No runtime behaviour changes beyond message/doc text. **Changed:** *Deferred / reserved surface now documented honestly* — `b.archive.read.zip.fromTrustedStream` is marked `experimental` — its `inspect`/`entries`/`extract` throw and its `bombPolicy`/`audit` options aren't honored yet; the documented example now shows the supported path (buffer the stream, then use the random-access reader). `b.acme` `revokeCert`'s `useCertKey` / `certPrivateKey` options are marked reserved (the cert-key-signed-revocation path throws; account-key signing, the default, covers mainstream CAs). A `b.breakGlass` policy error and comment that called passkey factors a future feature are corrected — passkeys are a live allowed factor. **Fixed:** *Corrected misattributed CVE citations in source threat-annotations* — `b.crypto.fromBase64Url`'s strict-decode guard cited CVE-2022-0235 (a node-fetch header-leak, unrelated to base64/JWT decoding); it now cites the weakness class it actually defends — CWE-347 / CWE-1286 signature canonicalization. `b.guardRegex`'s consecutive-`*` cap attributed CVE-2026-26996 to picomatch; that ReDoS is in minimatch (the picomatch ReDoS it also defends is CVE-2026-33671) — the library name is corrected. CVE-2026-32178 is reframed to the CWE-138 header-injection spoofing class the public advisory documents, and removed from the end-of-data SMTP-smuggling trio (a distinct class). No behaviour change — the defenses are unchanged.
+
 - v0.13.14 (2026-05-27) — **DNSSEC chain validation now bounds KeyTrap (CVE-2023-50387) amplification with hard caps.** b.network.dns.dnssec.verifyChain tried every DNSKEY whose 16-bit key tag matched an RRSIG, with no cap on how many candidates or total signature verifications a single response could drive. A hostile zone publishing many DNSKEYs sharing one key tag (plus matching RRSIGs) could force O(keys x signatures) full public-key verifications from one query — the KeyTrap denial-of-service (CVE-2023-50387). Validation is now bounded by non-configurable caps that match the BIND / Unbound mitigations: at most 4 same-tag candidate keys are tried per RRSIG, at most 64 DNSKEYs per zone link and 16 DS records per delegation are accepted, the chain is at most 128 links deep, and the whole response is held to a signature-validation budget that scales with chain depth (so a legitimate deep delegation is never false-rejected while bounded collisions stay bounded); exceeding any of these refuses the response rather than performing the work. Separately, a domain name that encodes to more than 255 octets is now refused at canonicalization (RFC 1035 §2.3.4), which also bounds the NSEC3 closest-encloser label enumeration, and the NSEC3 iteration ceiling is lowered from 500 to 150 to match the BIND 9.16.33+ / Unbound 1.17.1 fix for the sibling CVE-2023-50868. **Security:** *`verifyChain` caps colliding-key fan-out and total signature validations (KeyTrap / CVE-2023-50387)* — A zone advertising many same-key-tag DNSKEYs and RRSIGs can no longer drive unbounded public-key verifications. New refusals: `dnssec/too-many-colliding-keys` (>4 same-tag candidates per RRSIG), `dnssec/too-many-dnskeys` (>64 DNSKEYs per zone link), `dnssec/too-many-ds` (>16 DS records per delegation), `dnssec/too-many-links` (chain deeper than 128), and `dnssec/validation-budget-exceeded` (signature validations beyond the depth-scaled budget). The caps are intentionally non-configurable — they sit well above any legitimate zone, and the budget scales with chain depth so deep delegations validate normally. · *Domain-name octet cap + lower NSEC3 iteration ceiling* — A name that canonicalizes to more than 255 octets is refused (`dnssec/bad-name`, RFC 1035 §2.3.4), which bounds the per-label NSEC3 closest-encloser enumeration (CVE-2023-50868 class). The default NSEC3 iteration ceiling drops from 500 to 150, matching the BIND 9.16.33+ / Unbound 1.17.1 post-CVE defaults (RFC 9276 recommends 0).
 
 - v0.13.13 (2026-05-27) — **Archive extraction-path verification now refuses Windows reserved names, NTFS data streams, and trailing-dot/space per segment.** b.guardFilename.verifyExtractionPath (the per-entry gate b.archive.read.zip.extract / b.safeArchive run on every extracted file) checked traversal, absolute paths, drive-letter and UNC prefixes, null bytes, PATH_MAX overflow, and realpath containment — but not the per-segment Windows write-target hazards the disk validate / sanitize paths already reject. An archive entry named CON, NUL.txt, subdir/LPT1, file.txt:hidden, or secret.txt. stayed inside the extraction root, so the containment and realpath checks passed it, yet on Windows it would resolve to a device, write a hidden NTFS stream, or (after Windows strips the trailing dot/space) overwrite a sibling file. These are now refused: any path segment that collides with a Windows reserved device name, uses NTFS alternate-data-stream syntax (name:stream), or carries a trailing dot or leading/trailing whitespace. The checks are platform-unconditional — a verifier running on Linux still refuses names that are only dangerous on the Windows host that ultimately extracts the archive — with a per-check opt-out (reservedNamePolicy / adsPolicy / leadingTrailingPolicy: "allow") for Linux-only targets. **Security:** *`verifyExtractionPath` refuses per-segment Windows extraction hazards (reserved names / NTFS ADS / trailing dot-space)* — Closes a within-root write-target-redirection gap: an extracted entry could stay inside the destination yet, on Windows, resolve to a device (`CON` / `NUL` / `COM1` / `LPT1`), write a hidden alternate data stream (`file.txt:payload`), or overwrite a sibling after Windows strips a trailing dot/space (`config.`). The verification gate now rejects all three per path segment. Refusal is platform-unconditional (the verifier may run on a different OS than the extractor); set `reservedNamePolicy` / `adsPolicy` / `leadingTrailingPolicy` to `"allow"` to opt a check out on a Linux-only target. Single-entry, name-only residuals — 8.3 short-name aliasing, case-insensitive cross-entry collisions, and archive symlink/hardlink entry-target validation — remain the extract orchestrator's responsibility (it owns the case-folded seen-set and the link-target gate).

package/lib/acme.js

@@ -1079,14 +1079,17 @@ function create(opts) {
    * the DER-encoded cert (base64url-encoded automatically) plus an
    * optional `reason` code per RFC 5280 §5.3.1 (0=unspecified,
    * 1=keyCompromise, 3=affiliationChanged, 4=superseded, 5=cessationOfOperation).
-   * Signs with the account key by default; pass `useCertKey:true`
-   * + the cert's private key to authorize via the cert's own key
-   * when the account key is unavailable.
+   * Signs with the account key — the only supported path today, and
+   * sufficient for mainstream CAs. (The cert-key-signed variant —
+   * `useCertKey` / `certPrivateKey` — is reserved and not yet
+   * implemented; passing `useCertKey:true` throws.)
    *
    * @opts
    *   reason:          number,    // RFC 5280 §5.3.1 reason code; default 0 (unspecified)
-   *   useCertKey:      boolean,   // sign with the cert's own key instead of account key
-   *   certPrivateKey:  KeyObject, // required when useCertKey:true
+   *   useCertKey:      boolean,   // RESERVED — cert-key-signed revocation is not yet
+   *                               //   implemented; account-key signing (the default)
+   *                               //   covers mainstream CAs. Passing true throws.
+   *   certPrivateKey:  KeyObject, // RESERVED — consumed only by the cert-key path above
    *
    * @example
    *   await acme.revokeCert(certDerBuffer, { reason: 4 });   // 4 = superseded

package/lib/archive-read.js

@@ -772,7 +772,7 @@ function zip(adapter, opts) {
  * @primitive b.archive.read.zip.fromTrustedStream
  * @signature b.archive.read.zip.fromTrustedStream(adapter, opts?)
  * @since     0.12.7
- * @status    stable
+ * @status    experimental
  * @related   b.archive.read.zip, b.archive.adapters.trustedStream
  *
  * Forward-scan-only ZIP reader for trusted Readable sources. No
@@ -781,20 +781,23 @@ function zip(adapter, opts) {
  * `b.archive.zip().toStream()` output back into a reader for round-trip
  * verification).
  *
- * Adversarial input MUST use the random-access entry point with an
- * `fs` / `buffer` / `objectStore` / `http` adapter.
+ * NOT YET IMPLEMENTED: the streaming LFH walker is not built —
+ * `inspect()` / `entries()` / `extract()` throw
+ * `archive-read/trusted-stream-*-deferred`, and `bombPolicy` / `audit`
+ * are accepted but not yet honored. Re-opens when a streaming
+ * consumer needs it. Until then, collect the stream into a buffer and
+ * use the random-access reader, which is the supported path for both
+ * trusted round-trip verification and adversarial input.
  *
  * @opts
- *   bombPolicy:       { maxEntries, maxEntryDecompressedBytes,
- *                       maxTotalDecompressedBytes, maxExpansionRatio },
- *   audit:            b.audit,
+ *   bombPolicy:       { ... },   // reserved — not yet honored
+ *   audit:            b.audit,   // reserved — not yet honored
  *
  * @example
- *   var produced = fs.createReadStream("./own-export.zip");
- *   var reader   = b.archive.read.zip.fromTrustedStream(
- *     b.archive.adapters.trustedStream(produced)
- *   );
- *   for await (var e of reader.entries()) console.log(e.name, e.size);
+ *   // Supported path: buffer the stream, then read random-access.
+ *   var bytes  = await someStreamToBuffer(producedZipStream);
+ *   var reader = b.archive.read.zip(b.archive.adapters.buffer(bytes));
+ *   var entries = await reader.inspect();
  */
 function fromTrustedStream(adapter, opts) {
   if (!adapter || adapter.kind !== "trusted-sequential") {
@@ -805,25 +808,26 @@ function fromTrustedStream(adapter, opts) {
   var bombPolicy = _normalizeBombPolicy(opts.bombPolicy);
   void bombPolicy;
 
-  // Trusted stream walks LFH-by-LFH. v0.12.7 ships the API surface +
-  // a basic LFH walker for round-trip verification of the framework's
-  // own emitted archives. The full feature parity (extraction via
-  // streaming inflate, data-descriptor scanning) is intentionally
-  // deferred to v0.12.8 alongside the tar reader's sequential mode.
+  // The streaming LFH walker is not built — only the API surface +
+  // adapter validation exist. Extraction via streaming inflate +
+  // data-descriptor scanning re-opens when a streaming consumer needs
+  // it; until then the supported path is to buffer the stream and use
+  // the random-access reader (which handles both trusted round-trip
+  // verification and adversarial input).
   async function inspect() {
     throw new ArchiveReadError("archive-read/trusted-stream-inspect-deferred",
-      "fromTrustedStream.inspect() is deferred to v0.12.8 — use the random-access entry " +
-      "point with b.archive.adapters.buffer(await collect(readable)) for v0.12.7");
+      "fromTrustedStream.inspect() is not implemented — collect the stream into a buffer and " +
+      "use b.archive.read.zip(b.archive.adapters.buffer(bytes))");
   }
 
   async function* entries() {
     throw new ArchiveReadError("archive-read/trusted-stream-entries-deferred",
-      "fromTrustedStream.entries() is deferred to v0.12.8 — collect into buffer for v0.12.7");
+      "fromTrustedStream.entries() is not implemented — collect into a buffer and use the random-access reader");
   }
 
   async function extract() {
     throw new ArchiveReadError("archive-read/trusted-stream-extract-deferred",
-      "fromTrustedStream.extract() is deferred to v0.12.8 — collect into buffer for v0.12.7");
+      "fromTrustedStream.extract() is not implemented — collect into a buffer and use the random-access reader");
   }
 
   return {

package/lib/break-glass.js

@@ -130,9 +130,9 @@ function _ensureFactorLockout() {
 // keys + encryption-context binding (cross-cell tampering / accidental
 // row-swap fails closed). It does NOT defend against vault-key
 // compromise alone — the DEK is still vault-recoverable. True
-// second-factor cryptographic gating ships in v0.5.2 with passkey
-// integration (the passkey private key lives on the YubiKey, not in
-// the framework, so a vault leak alone can't unwrap).
+// second-factor cryptographic gating uses passkey integration (the
+// passkey private key lives on the YubiKey, not in the framework, so a
+// vault leak alone can't unwrap).
 
 // In-memory DEK cache. Keyed by table name. Cleared on _resetForTest.
 var dekCache = new Map();
@@ -520,8 +520,7 @@ function _validatePolicySet(table, opts) {
     if (ALLOWED_FACTORS.indexOf(opts.factors[j]) === -1) {
       throw new BreakGlassError("breakglass/bad-policy",
         "policy.set: factors[" + j + "] '" + opts.factors[j] +
-        "' not in v0.5.0 allowed factors [" + ALLOWED_FACTORS.join(",") + "]" +
-        " (passkey lands in v0.5.2)");
+        "' not in allowed factors [" + ALLOWED_FACTORS.join(",") + "]");
     }
   }
   // Model B (cryptographic mode) ships in v0.5.1. When enabled,

package/lib/crypto.js

@@ -789,10 +789,12 @@ function toBase64Url(buf) {
  *
  * Strict mode (default) refuses non-canonical input — chars outside
  * the RFC 4648 §5 alphabet, length-mod-4-of-1, mixed `+/` from
- * standard base64, trailing garbage. Defends a CVE-2022-0235 class
- * footgun where Node's permissive decoder silently tolerated
- * tampered JWT signatures. Operators with a documented lossy legacy
- * payload opt out per call via `{ strict: false }`.
+ * standard base64, trailing garbage. Defends the CWE-347 /
+ * CWE-1286 signature-canonicalization footgun where a permissive
+ * base64url decoder silently tolerates a tampered JWS / JWT signature
+ * (non-canonical bytes decoding to the same buffer). Operators with a
+ * documented lossy legacy payload opt out per call via
+ * `{ strict: false }`.
  *
  * @opts
  *   strict: boolean   // default: true — refuse non-canonical input
@@ -817,7 +819,8 @@ function fromBase64Url(s, opts) {
   // OAuth `state` round-tripping) MUST reject non-canonical / malformed
   // input. The Node base64url decoder silently tolerates trailing
   // garbage, mixed `+/` from standard base64, missing padding errors,
-  // and length-mod-4 shapes — CVE-2022-0235 class footgun. Strict mode
+  // and length-mod-4 shapes — the CWE-347 / CWE-1286 signature-
+  // canonicalization footgun. Strict mode
   // (the default) refuses anything outside the RFC 4648 §5 alphabet +
   // length rules. Operators with a known-lossy legacy payload pass
   // `{ strict: false }` to opt out per call.

package/lib/guard-dsn.js

@@ -84,8 +84,9 @@
  *     generating a DSN (the existing `b.mail.bounce` primitive does
  *     this); this guard parses INBOUND DSNs and gates the parse
  *     surface bounds, not the bounce-generation policy.
- *   - **DSN header-injection class** (CVE-2026-32178 .NET
- *     System.Net.Mail at outbound; the inbound parse path here)
+ *   - **DSN header-injection class** (CVE-2026-32178 — .NET CWE-138
+ *     special-element / header-injection spoofing, the System.Net.Mail
+ *     vector per MSRC, at outbound; the inbound parse path here)
  *     — refuses CR/LF/NUL/C0 in header lines.
  *   - **CSAF / iSchedule prose tampering** — operator inspecting
  *     the prose part for the original recipient runs into the

package/lib/guard-list-id.js

@@ -37,8 +37,9 @@
  *     octets. Total header value capped at 998 bytes per RFC 5322
  *     §2.1.1 line cap.
  *   - **CRLF + control-char refusal** — header-injection defense
- *     (CVE-2026-32178 .NET System.Net.Mail class on the wire-protocol
- *     surface; this primitive's job is the SEMANTIC shape).
+ *     (CVE-2026-32178 — .NET CWE-138 header-injection spoofing, the
+ *     System.Net.Mail vector per MSRC, on the wire-protocol surface;
+ *     this primitive's job is the SEMANTIC shape).
  *   - **Phrase-injection refusal** — Operator-supplied display
  *     phrase mustn't carry CRLF / `<` / `>` outside the angle
  *     brackets (a separate Bcc/Cc header smuggled into the phrase

package/lib/guard-regex.js

@@ -248,14 +248,14 @@ function _detectIssues(input, opts) {
 }
 
 // Consecutive-star wildcard cap (CVE-2026-26996). Operator-supplied
-// glob fragments compile to picomatch / RegExp; a long run of `*`
-// against a non-matching literal walks O(4^N). Three-or-more
+// glob fragments compile to minimatch / picomatch / RegExp; a long run
+// of `*` against a non-matching literal walks O(4^N). Three-or-more
 // consecutive `*` is the canonical bad shape; `**` (recursive glob)
 // stays permitted, gated by the profile's `maxConsecutiveStars`.
 function _detectConsecutiveStar(input, opts, issues) {
   if (opts.consecutiveStarPolicy === "allow") return;
-  // CVE-2026-26996 is a picomatch / glob-shape backtracking class —
-  // `***+literal` walks O(4^N) when picomatch translates the run to a
+  // CVE-2026-26996 is a minimatch glob-shape backtracking class —
+  // `***+literal` walks O(4^N) when minimatch translates the run to a
   // backtracking-heavy regex. Native ECMAScript regex syntax cannot
   // produce three consecutive `*` quantifiers (it's a SyntaxError),
   // so applying this detector to `inputKind: "regex"` strings only

package/lib/guard-smtp-command.js

@@ -15,8 +15,7 @@
  *   ## Smuggling defense — bare-CR / bare-LF refusal
  *
  *   The SMTP smuggling class (`CVE-2023-51764` Postfix, `CVE-2023-51765`
- *   Sendmail, `CVE-2023-51766` Exim, `CVE-2026-32178` .NET
- *   `System.Net.Mail`) exploits implementations that accept the
+ *   Sendmail, `CVE-2023-51766` Exim) exploits implementations that accept the
  *   non-standard end-of-data sequence `<LF>.<LF>` or `<LF>.<CR><LF>`
  *   instead of the standard `<CR><LF>.<CR><LF>`. The introduced break-
  *   out lets a malicious peer inject a second message past SPF / DMARC

package/lib/mail-agent.js

@@ -7,19 +7,26 @@
  * @featured   true
  *
  * @intro
- *   The standardization contract for every mail protocol blamejs ships.
- *   JMAP (v0.9.27), IMAP (v0.9.28), POP3 (v0.9.29), ManageSieve (v0.9.30),
- *   the inbound MX listener (v0.9.24), and the submission listener
- *   (v0.9.25) all translate their protocol calls into `agent.X(args)`.
- *   The agent owns RBAC, posture enforcement, audit emission,
- *   dispatch, and worker isolation; every protocol on top is a thin
- *   shell.
+ *   A mailbox-access facade that owns RBAC, posture enforcement, audit
+ *   emission, dispatch (local / worker-pool / queue), and worker
+ *   isolation around a mail store, so a protocol server built on top
+ *   can stay a thin shell. It is designed to be the shared dispatch
+ *   layer mail-protocol servers route through; today the read surface
+ *   and the mailbox-mutation + Sieve-upload methods are wired, while the
+ *   compose/send and identity/vacation/MDN/export verbs are not yet
+ *   wired into the facade (see below).
  *
- *   `agent.create()` returns the facade. Methods backed by v0.9.19's
- *   `b.mailStore` run immediately; methods that depend on later slices
- *   throw `mail-agent/not-implemented` with a `wiredAt` tag naming the
- *   version that lights them up (defer-with-condition — operator can
- *   match against the tag to scope their integration).
+ *   `agent.create()` returns the facade. Methods backed by
+ *   `b.mailStore` (folders / fetch / search / move / flag / delete /
+ *   expunge, plus `sieve.put`) run immediately. The remaining verbs —
+ *   compose / send / reply / forward, sieve.list / sieve.activate,
+ *   identity / vacation / mdn.*, export / job / import — throw
+ *   `mail-agent/not-implemented`: they are not yet routed through the
+ *   agent. Until they are, compose the underlying primitive directly
+ *   (`b.mail.send.deliver` for outbound, `b.mail.sieve` for Sieve,
+ *   `b.mailMdn` for MDN, etc.) — which is what the framework's own JMAP
+ *   `emailSubmissionSet` handler does. They wire into the facade when a
+ *   protocol server adopts the agent as its dispatch layer.
  *
  *   ```js
  *   var agent = b.mail.agent.create({
@@ -58,9 +65,11 @@
  *   on every entrypoint.
  *
  * @card
- *   The standardization contract for every mail protocol — JMAP / IMAP /
- *   POP3 all translate into `agent.X(args)`. RBAC + posture + audit +
- *   dispatch owned here; protocols on top are thin shells.
+ *   Mailbox-access facade — RBAC + posture + audit + dispatch around a
+ *   mail store, so a protocol server on top stays a thin shell. Read +
+ *   mailbox-mutation + Sieve-upload methods are wired; compose/send and
+ *   identity/vacation/MDN/export verbs compose the underlying primitive
+ *   directly until a protocol server routes them through the agent.
  */
 
 var lazyRequire        = require("./lazy-require");
@@ -118,25 +127,25 @@ var SCOPE_FOR_METHOD = Object.freeze({
   import:           "mail:import",
 });
 
-// Methods deferred behind a `wiredAt` version. Operator gets a clear
-// error pointing at the slice that lights them up — defer-with-
-// condition per the v1-defensible-scope rule.
-var WIRED_AT = Object.freeze({
-  compose:          "v0.9.25",
-  send:             "v0.9.25",
-  reply:            "v0.9.25",
-  forward:          "v0.9.25",
-  "sieve.list":     "v0.9.26",
-  "sieve.put":      "v0.9.26",
-  "sieve.activate": "v0.9.26",
-  "identity.set":   "v0.9.25",
-  "vacation.set":   "v0.9.25",
-  "mdn.send":       "v0.9.25",
-  "mdn.parse":      "v0.9.25",
-  "mdn.allowList":  "v0.9.25",
-  export:           "v0.9.34a",
-  job:              "v0.9.34a",
-  import:           "v0.9.34",
+// Verbs not yet routed through the agent facade. The error points the
+// operator at the underlying primitive to compose directly (the
+// escape hatch) — defer-with-condition: these wire into the agent when
+// a protocol server adopts it as its dispatch layer.
+var COMPOSE_HINT = Object.freeze({
+  compose:          "b.mail.send.deliver",
+  send:             "b.mail.send.deliver",
+  reply:            "b.mail.send.deliver",
+  forward:          "b.mail.send.deliver",
+  "sieve.list":     "b.mail.sieve",
+  "sieve.activate": "b.mail.sieve",
+  "identity.set":   "your identity store + b.mail.sieve",
+  "vacation.set":   "b.mail.sieve (vacation extension)",
+  "mdn.send":       "b.mailMdn",
+  "mdn.parse":      "b.mailMdn",
+  "mdn.allowList":  "b.mailMdn",
+  export:           "b.mailStore / b.auditTools",
+  job:              "the dispatch queue directly",
+  import:           "b.mailStore",
 });
 
 /**
@@ -653,9 +662,10 @@ function _notImplemented(ctx, method, args) {
   // the slice lights up.
   if (ctx.posture) guardMailQuery.validateActor(args && args.actor, ctx.posture);
   _checkPermission(ctx, method, args);
-  ctx.auditEmit("mail.agent.not_implemented", args && args.actor, { method: method, wiredAt: WIRED_AT[method] });
+  ctx.auditEmit("mail.agent.not_implemented", args && args.actor, { method: method, composeDirectly: COMPOSE_HINT[method] });
   return Promise.reject(new MailAgentError("mail-agent/not-implemented",
-    "agent." + method + ": wired at " + WIRED_AT[method] + " (defer-with-condition)"));
+    "agent." + method + " is not yet routed through the agent facade — compose " +
+    COMPOSE_HINT[method] + " directly"));
 }
 
 // ---- Internals ------------------------------------------------------------
@@ -771,7 +781,7 @@ module.exports = {
   consumer:         consumer,
   MailAgentError:   MailAgentError,
   SCOPE_FOR_METHOD: SCOPE_FOR_METHOD,
-  WIRED_AT:         WIRED_AT,
+  COMPOSE_HINT:     COMPOSE_HINT,
   HEAVY_METHODS:    HEAVY_METHODS,
   // Re-export the guard family so callers can introspect without
   // separate requires.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blamejs/core",
-  "version": "0.13.14",
+  "version": "0.13.16",
   "description": "The Node framework that owns its stack.",
   "license": "Apache-2.0",
   "author": "blamejs contributors",

package/sbom.cdx.json

@@ -2,10 +2,10 @@
   "$schema": "http://cyclonedx.org/schema/bom-1.5.schema.json",
   "bomFormat": "CycloneDX",
   "specVersion": "1.5",
-  "serialNumber": "urn:uuid:7b7971af-a00b-4343-af83-3f8ef1a433dc",
+  "serialNumber": "urn:uuid:cd0375e1-7520-4024-b6eb-d8c708fc00db",
   "version": 1,
   "metadata": {
-    "timestamp": "2026-05-27T13:56:08.465Z",
+    "timestamp": "2026-05-27T17:24:50.447Z",
     "lifecycles": [
       {
         "phase": "build"
@@ -19,14 +19,14 @@
       }
     ],
     "component": {
-      "bom-ref": "@blamejs/core@0.13.14",
+      "bom-ref": "@blamejs/core@0.13.16",
       "type": "application",
       "name": "blamejs",
-      "version": "0.13.14",
+      "version": "0.13.16",
       "scope": "required",
       "author": "blamejs contributors",
       "description": "The Node framework that owns its stack.",
-      "purl": "pkg:npm/%40blamejs/core@0.13.14",
+      "purl": "pkg:npm/%40blamejs/core@0.13.16",
       "properties": [],
       "externalReferences": [
         {
@@ -54,7 +54,7 @@
   "components": [],
   "dependencies": [
     {
-      "ref": "@blamejs/core@0.13.14",
+      "ref": "@blamejs/core@0.13.16",
       "dependsOn": []
     }
   ]