@blamejs/core 0.18.47 → 0.18.49

package/CHANGELOG.md

@@ -8,6 +8,40 @@ upgrading across more than a few patches at a time.
 
 ## v0.18.x
 
+- v0.18.49 (2026-08-22) — **Comments in the shipped tree that answered a question you cannot ask.** A comment in `lib/` reaches anyone who opens the published package, and twenty of them were written for a reader who remembers the previous version or can look up an issue number that resolves nowhere outside this repository. They now say what the code does and why, in the present tense, keeping every reason they carried. No behaviour changes. **Changed:** *Comments that narrated a change now describe the code* — Fourteen comments across `lib/` were written against a version the reader has never seen: "this used to be opt-in", "it used to declare them in every profile anyway", "the legacy fallback was removed". Each is now a property of the design rather than a diff, and each keeps the reason it carried. The zero-width scan's comment still explains that an opt-in argument is an argument a caller can omit, and still names the six call sites that omitted it — it just no longer reads as a changelog entry pasted into the source.
+
+One of them was wrong in a way worth naming: a note in the gate-contract context builder said a guard "serves bytes it used to examine", which reads as a past version's behaviour. It means bytes the guard would otherwise examine, and now says so. · *Issue numbers that resolve nowhere are gone; the upstream ones stay* — Six comments cited a bare `issue #100` / `#330` / `#430` / `#532`. Opened from the published tarball those name nothing an operator can look up, and the explanation beside them was already doing the work. The references are gone and the explanations stay.
+
+The references that name their upstream are untouched and now read unambiguously: `cure53/DOMPurify issue #233` on the SVG `xlink:href` filtering, and CycloneDX spec issue #702 on the EU CRA property mapping, which is now attributed on both of its mentions rather than one.
+
+The boundary is what ships. `test/` carries 144 of the same kind of reference, most of them a `PR #nnn` on a regression test, and those are left alone: they resolve in the repository a contributor is already reading, and on a regression test the pull-request reference is often the most useful line in the comment. · *Three sentences in SECURITY.md* — A bot-guard rationale said an abuser "simply sends the header", which tells a reader the step is trivial and adds nothing to the argument. Two lists ended in `etc.` without saying where the rest was: the post-quantum algorithm-agility example now names HQC and FrodoKEM as the examples they are, and the session-risk scorer now says it scores whatever signal you have. The other six `etc.` in the file name their generating rule in the next clause and are unchanged.
+
+- v0.18.48 (2026-08-22) — **A guard option you set and a guard option that exists were not the same set.** Every `*Policy` option across the guard family now names the values it takes, and refuses everything else where options are resolved rather than at the first request that trips the scan. Holding the options to their vocabularies surfaced four places where what a guard advertised and what it did had come apart: an option documented under a name nothing read, a value that disabled a critical check without appearing in any opts block, two policies whose settings the gate's floor overrode anyway, and one declared in all three profiles and read nowhere. **Fixed:** *A guard policy refuses a value outside its vocabulary* — The two hundred and sixty-two `*Policy` options across the guard family each declare the values they accept, checked where options are resolved — boot, not the first hostile input — and on every entry point, including the `gate()` and `validate()` of guards that bind their own resolver.
+
+The failure it ends is quiet, because policies are read leniently. `duplicateKeyPolicy: "rejct"` is not `allow`, so the check still runs; it is not `reject` either, so the finding drops from critical to a warning. The operator asked to refuse a duplicate key and silently got an audit line. Nothing was let through that a stricter reading would have caught, so this was never a hole — but a setting that means something other than what it says is worth a restart to learn about.
+
+`b.gateContract.policyVocabulary(names, values, overrides?)` builds these tables: most of a guard's policies answer the same question — refuse the construct, record it, or let it through — and one or two do not. Written out per option instead, a family of nine ends up with eight that accept `audit-only` and one that does not. Each guard also exports its `POLICY_VOCABULARY`, so a caller can ask what an option takes instead of reading the source. · *An option name the guard does not have is refused rather than ignored* — A `*Policy` key that no guard option matches was kept by the option merge, read by nothing, and left the profile default in force. `b.guardMime` had shipped that way: its opts block named `riskyTypesPolicy` while the code reads `riskyTypePolicy`, so an operator following the documentation and setting it to `reject` kept the balanced profile's `audit` and had risky content types reported rather than refused, with nothing to see but the documentation that was wrong to begin with.
+
+A guard's policy set is fully described by its profiles, postures and defaults, so a near-miss is decidable and now refused by name. The rest of the option surface stays open — callbacks, caches and host wiring are not enumerable in advance.
+
+The two statements a guard makes about an option — the vocabulary it enforces and the opts block an operator reads — are now compared to each other, which is what surfaced this one. · *`kidTraversalPolicy: "allow"` turned off JWT key-path traversal detection* — `b.guardJwt` documents the `kid` traversal check as unconditional, and the header field it inspects is the one that steers key lookup — a `kid` of `../../etc/passwd` reaching a file-backed resolver is the point of the check. The code consulted `kidTraversalPolicy` for an `allow` its opts block never offered, and that value skipped the check entirely.
+
+The check no longer reads a policy, and the option accepts `reject` alone. `algNonePolicy` is likewise fixed at `reject`: `alg=none` was already refused unconditionally and the option had never been read. · *Two guardFilename policies were settings the floor already overrode* — `traversalPolicy` and `nullBytePolicy` accepted `allow` and `audit`, and both were overridden by the refusal floor the gate applies to a leaf filename. An operator setting either believed they had turned a class of finding down; the refusal stood regardless, and the two disagreed in the audit record rather than in the verdict. Both now accept `reject` alone, so the floor is visible in what the guard will take rather than only in what it does.
+
+`adsPolicy` keeps `allow` for the one place that honours it — `verifyExtractionPath`, for an operator deliberately extracting stream-suffixed names — and no longer accepts an `audit` that did nothing. · *`svgzPolicy` was declared in every profile and read nowhere* — A gzip-compressed SVG is refused on its byte signature before any parse, and `b.guardSvg.sanitize` throws on one outright. `svgzPolicy` sat in all three profiles without being consulted, so an operator writing `svgzPolicy: "allow"` got a silent no-op and a reasonable belief that SVGZ now passed. The option takes `reject` alone, which is what the guard has always done. · *Three policies do not take `audit-only`, because their code reads the literal `audit`* — `audit-only` is the family's documented synonym for `audit`, and most policies treat them identically because the disposition mapper asks one predicate. Three conditions test for the literal spelling instead, and there the two words took different branches with nothing in the option's name to say which you had picked: `pkcePolicy: "audit-only"` refused every OAuth flow missing a PKCE challenge while `"audit"` served it with a finding; `pollutionPolicy: "audit-only"` removed `__proto__` from the parsed object while `"audit"` preserved it, a difference in the data rather than in a finding; and `pathSeparatorsPolicy: "audit-only"` failed a path-shaped name that `"audit"` accepted.
+
+`b.guardOauth.pkcePolicy`, `b.guardJson.pollutionPolicy` and `b.guardFilename.pathSeparatorsPolicy` now refuse `audit-only` rather than accepting it and meaning something else by it — as `b.guardArchive.nestedArchivePolicy`, `b.guardDomain.trailingDotPolicy` and `b.guardYaml.tagPolicy` already did, for the same reason. Write `audit` on those six.
+
+A detector holds the pairing: a policy compared against the literal `"audit"` may not also advertise the synonym, so the next one is a failing gate rather than two spellings that quietly disagree. · *Which guards refuse `strip` on a character policy, in full* — 0.18.47 made repair capability a declaration rather than something inferred from the presence of a `sanitize`, and named four guards the inference had been wrong about. Fourteen refuse `strip` on the shared character policies; the list is here because the boot error lands on a caller who had a working configuration, and four names is not the set.
+
+Refuse it: `b.guardAuth`, `b.guardCidr`, `b.guardCountry`, `b.guardDomain`, `b.guardGraphql`, `b.guardJsonpath`, `b.guardJwt`, `b.guardMime`, `b.guardOauth`, `b.guardRegex`, `b.guardShell`, `b.guardTemplate`, `b.guardTime`, `b.guardUuid`. Accept it: `b.guardEmail`, `b.guardFilename`, `b.guardHtml`, `b.guardJson`, `b.guardMarkdown`, `b.guardSvg`, `b.guardText`, `b.guardXml`, `b.guardYaml`.
+
+All fourteen refuse the character rather than removing it. Feed `b.guardUuid.sanitize` an identifier with a zero-width character in it and it throws `uuid.zero-width`, because a UUID with the character removed is a different identifier — and the same holds for a CIDR block, a country code, a domain, a JSONPath, a media type, a timestamp, a GraphQL document, an OAuth flow and an auth bundle. There is no repaired form to route a `strip` to.
+
+`b.guardAuth`, `b.guardOauth` and `b.guardGraphql` are the clearest case for making capability a declaration rather than an inference: each carries a `sanitizeTransform` that is the identity function, because an auth bundle and an OAuth flow are composed of values the framework must not rewrite — forging a JWT `alg` or editing a `state` parameter would disarm the token the guard exists to catch. Inferring "can repair" from the presence of a `sanitize` read all three as repairing.
+
+`b.guardCsv`, `b.guardImage` and `b.guardPdf` expose no shared character policy at all. guardCsv repairs characters through its own `bidiCharPolicy`, `controlCharPolicy` and `homoglyphPolicy`, and those still take `strip`. · *Twenty opts-block lines offered a repair the guard cannot perform* — `b.guardUuid`, `b.guardCountry`, `b.guardTime`, `b.guardMime`, `b.guardShell`, `b.guardRegex`, `b.guardJsonpath` and `b.guardTemplate` documented `strip` on their character policies. None of them repairs a character — a UUID with a zero-width character in it is not a UUID with the character removed, it is a different identifier — so the value was refused at construction while the documentation offered it. The lines now name what the guards accept.
+
 - v0.18.47 (2026-08-22) — **A misspelled character policy was accepted at boot and quietly meant something else.** `bidiPolicy: "rejct"` was accepted by every door the framework offers — the guard's own option resolver and the gate built from it — and then read leniently at runtime: the scan runs because the value is not `allow`, an issue is raised, and the disposition falls through to refuse. Nothing is let through, so it was never a hole; the operator simply asked for one disposition, got another, and was told nothing at the moment a boot error would have cost them a restart. Ninety-three settings across the guard family behaved that way. **Fixed:** *A character policy refuses a value outside its vocabulary* — The five character-threat policies every guard shares — `bidiPolicy`, `nullBytePolicy`, `controlPolicy`, `zeroWidthPolicy`, `tagsPolicy` — now accept only `allow`, `audit`, `audit-only`, `reject`, and `strip` where the guard can carry a repair out. Anything else is refused where options are resolved, which is boot, not the first request that trips the scan. Every entry point takes the check: the generated resolver, and the `gate()` and `validate()` of the guards that bind their own.
 
 The check is derived from each guard's own declared defaults rather than hand-listed per guard, for the same reason the size caps beside it are. Hand-listing is what produced the gap: `b.guardCountry` added this for its own three options after `{ reservedPolicy: "rejcet" }` served a reserved country code and reported success, and the other two hundred and fifty-nine policy options across the family never followed. A guard that declares its own vocabulary explicitly still wins, so that one is unchanged.

package/lib/ai-model-manifest.js

@@ -178,8 +178,8 @@ function build(opts) {
     }
   }
 
-  // Hyperparameters → CycloneDX properties[] kv pairs per spec
-  // issue #702 EU CRA alignment.
+  // Hyperparameters → CycloneDX properties[] kv pairs, per CycloneDX spec
+  // issue #702 (EU CRA alignment).
   var properties = [];
   if (opts.hyperparameters && typeof opts.hyperparameters === "object") {
     var keys = Object.keys(opts.hyperparameters);

package/lib/audit-sign.js

@@ -85,8 +85,8 @@ var _err = AuditSignError.factory;
 // via opts.algorithm — e.g. `auditSigning: { algorithm: "ml-dsa-87" }`
 // for throughput-sensitive deployments. Every key file MUST carry the
 // `algorithm` field on disk — the framework refuses to load a key file
-// that lacks it. The legacy implicit-default-to-ml-dsa-87 fallback was
-// removed as part of the pre-v1 compat-shim sweep.
+// that lacks it. There is no implicit default: a key file whose algorithm has
+// to be guessed is a key file whose signatures cannot be attributed.
 var DEFAULT_SIGNING_ALG = "slh-dsa-shake-256f";
 // ml-dsa-65 (FIPS 204 Category 3, ~192-bit symmetric security) is opt-
 // in alongside ml-dsa-87 — same code path (both auto-detected by
@@ -102,7 +102,7 @@ var SIGNING_KEY_SCHEMA = {
   properties: {
     publicKey:  { type: "string" },
     privateKey: { type: "string" },
-    algorithm:  { type: "string" },     // load-time-required — _initPlaintext + _initWrapped both throw KEY_FILE_MISSING_ALG / UNWRAPPED_MISSING_ALG when the field is absent (legacy implicit-default-to-ml-dsa-87 was removed in the pre-v1 compat-shim sweep). Schema's `required` keeps publicKey + privateKey only so the runtime checks fire with the precise error codes operators have wired alerting on.
+    algorithm:  { type: "string" },     // load-time-required — _initPlaintext + _initWrapped both throw KEY_FILE_MISSING_ALG / UNWRAPPED_MISSING_ALG when the field is absent, rather than defaulting to an algorithm the file never named. Schema's `required` keeps publicKey + privateKey only so the runtime checks fire with the precise error codes operators have wired alerting on.
   },
 };
 

package/lib/auth/passkey.js

@@ -986,7 +986,7 @@ function _requireCredentialIdMatches(response, authoritativeId, why) {
   // _credentialDescriptors deliberately supports -- while the browser returns
   // the unpadded spelling. Two spellings of ONE credential must not read as
   // two credentials, or the compatibility this binding sits next to would
-  // lock out exactly the deployments it was added for.
+  // lock out exactly the deployments it exists for.
   var expected = _canonicalBase64Url(authoritativeId);
   var fields = ["id", "rawId"];
   var stated = 0;

package/lib/backup/index.js

@@ -1697,8 +1697,8 @@ function bundleAdapterStorage(opts) {
       // "unknown" rather than risk a full payload load. For
       // rewrap, we already have to load the payload (to unwrap),
       // so fall back to a sniffEnvelope on the loaded sealed
-      // bytes — fixes the regression where adapters satisfying
-      // the minimum contract couldn't use rewrapBundle.
+      // bytes, which keeps rewrapBundle reachable for an adapter
+      // that satisfies only the minimum contract.
       if (envelopeKind === "unknown") {
         envelopeKind = archiveLazy().sniffEnvelope(sealed);
       }

package/lib/client-hints.js

@@ -136,8 +136,7 @@ function _parseSfBrandList(s) {
   // sf-list members don't allow parenthesized inner-list values in
   // the Sec-CH-UA grammar (only sf-string + parameters), so the
   // simple top-level comma split suffices — no `depth` tracking
-  // needed (the earlier inline shape carried defensive paren
-  // tracking left over from a generic sf-list walker prototype).
+  // needed.
   var pieces = structuredFields.splitTopLevel(t, ",");
   var out = [];
   for (var i = 0; i < pieces.length; i += 1) {

package/lib/codepoint-class.js

@@ -860,11 +860,12 @@ function detectCharThreats(text, opts, codePrefix) {
   // zero-width-only input under `strip` reaches the sanitizer instead of being
   // served unchanged.
   //
-  // This used to be OPT-IN via a `zeroWidthSeverity` argument, which meant a
-  // caller that forgot it disabled the scan no matter what the operator's
-  // policy said — and six did, including the shared gate path, so seven guards
-  // declared `zeroWidthPolicy: "reject"` and never applied it. Six more passed
-  // a hardcoded "warn", which dispositions to serve, so they reported the
+  // Not opt-in, and deliberately: an argument the caller has to pass in order
+  // for the scan to run is an argument a caller can omit, and omitting it
+  // disables the scan no matter what the operator's policy says. Six call
+  // sites omitted it, the shared gate path among them, so seven guards declared
+  // `zeroWidthPolicy: "reject"` and never applied it. Six more passed a
+  // hardcoded "warn", which dispositions to serve, so they reported the
   // character and shipped it anyway.
   //
   // Severity follows the resolved POLICY, not a per-caller constant — the same

package/lib/gate-contract.js

@@ -305,7 +305,7 @@ function validateGateShape(gate, label, errorClass) {
 //   - `Object.assign({}, base, ...)` copies OWN enumerable properties, so a
 //     class instance whose fields come from prototype getters arrives with them
 //     missing. A guard reading an absent subject as nothing-to-inspect then
-//     serves bytes it used to examine.
+//     serves bytes it would otherwise examine.
 //   - `Object.create(base)` fixes that but makes inherited getters run with the
 //     DERIVED object as `this`, so a getter returning a private field throws
 //     and a valid context is refused.
@@ -2160,6 +2160,75 @@ var CHAR_POLICY_KEYS = Object.freeze([
 ]);
 var CHAR_POLICY_BASE = Object.freeze(["allow", "audit", "audit-only", "reject"]);
 
+// The vocabularies a guard's own policies keep reaching for. Named because
+// most of a guard's policies answer the same question — refuse this construct,
+// record it, or let it through — and because a hand-written array per option
+// is where a family of nine drops `audit-only` from one of them.
+var POLICY_VALUES = Object.freeze({
+  // Refuse the construct, record it, or let it through. `audit-only` is the
+  // family's documented synonym for `audit`.
+  rejectAuditAllow:      Object.freeze(["reject", "audit", "audit-only", "allow"]),
+  // The same, where the guard can also remove the construct and still produce
+  // a usable document. Only for a finding the sanitizer genuinely repairs:
+  // routing one to a repair that never happens serves the input as sanitized.
+  rejectStripAuditAllow: Object.freeze(["reject", "strip", "audit", "audit-only", "allow"]),
+});
+
+/**
+ * @primitive  b.gateContract.policyVocabulary
+ * @signature  b.gateContract.policyVocabulary(names, values, overrides?)
+ * @since      0.18.48
+ * @status     stable
+ * @related    b.gateContract.charPolicyEnums, b.gateContract.defineGuard
+ *
+ * An `enumOpts` table where `names` all take `values`, with `overrides` merged
+ * over the top for the options that differ. Most of a guard's policies share
+ * one vocabulary and one or two do not, and writing the shared one out per
+ * option is how a family of nine ends up with eight that accept `audit-only`
+ * and one that does not.
+ *
+ * @example
+ *   var POLICY_ENUM = gateContract.policyVocabulary(
+ *     ["doctypePolicy", "entityPolicy", "cdataPolicy"],
+ *     gateContract.POLICY_VALUES.rejectAuditAllow,
+ *     { xmlDsigPolicy: ["audit", "audit-only", "allow"] });
+ *   POLICY_ENUM.entityPolicy;   // → ["reject", "audit", "audit-only", "allow"]
+ *   POLICY_ENUM.xmlDsigPolicy;  // → ["audit", "audit-only", "allow"]
+ */
+function policyVocabulary(names, values, overrides) {
+  if (!Array.isArray(names) || !Array.isArray(values) || values.length === 0) {
+    throw GateContractError.factory("gate-contract/bad-opt",
+      "gateContract.policyVocabulary: names and values must both be arrays " +
+      "and values must be non-empty");
+  }
+  // Frozen a level down, and from a copy. A guard publishes this table as its
+  // `POLICY_VOCABULARY` while the resolver checks against the same arrays, so
+  // an introspection caller that pushed onto one would be editing the rule, not
+  // reading it: `POLICY_VOCABULARY.symlinkPolicy.push("bogus")` and the guard
+  // accepts "bogus". Copying also keeps the caller's own array theirs.
+  var out = {};
+  var shared = Object.freeze(values.slice());
+  names.forEach(function (name) {
+    out[name] = shared;
+  });
+  if (overrides && typeof overrides === "object") {
+    Object.keys(overrides).forEach(function (name) {
+      // A non-array override would be dropped by the resolver's own
+      // `Array.isArray` test and leave the option unconstrained — the option
+      // would read as declared while accepting anything, which is the state
+      // this whole mechanism exists to end. It is an author mistake, so it
+      // belongs where the author is looking.
+      if (!Array.isArray(overrides[name]) || overrides[name].length === 0) {
+        throw GateContractError.factory("gate-contract/bad-opt",
+          "gateContract.policyVocabulary: override for " + JSON.stringify(name) +
+          " must be a non-empty array of values");
+      }
+      out[name] = Object.freeze(overrides[name].slice());
+    });
+  }
+  return Object.freeze(out);
+}
+
 /**
  * @primitive  b.gateContract.charPolicyEnums
  * @signature  b.gateContract.charPolicyEnums(defaults, opts?)
@@ -2682,10 +2751,77 @@ function resolveProfileAndPosture(opts, cfg) {
       }
     });
   }
+  // The same failure with the NAME wrong instead of the value, which is
+  // quieter because there is no value to inspect: the merge keeps the key,
+  // nothing reads it, and the profile default stays in force. An operator who
+  // sets `riskyTypesPolicy: "reject"` on a guard whose option is
+  // `riskyTypePolicy` keeps the balanced profile's "audit" and gets no sign
+  // the setting was dropped.
+  //
+  // Only `*Policy` keys are decidable this way: a guard's policy set is fully
+  // described by its profiles, postures and defaults, so anything else with
+  // that suffix is a near-miss. The rest of the opts surface stays open by
+  // design — callbacks, caches and host wiring are not enumerable in advance.
+  _refuseUnknownPolicyKeys(opts, resolved, cfg, ErrorClass, prefix);
   return resolved;
 }
 
 
+// A published copy of an enumOpts table, frozen a level down so a caller
+// reading it cannot reorder the guard's own vocabulary underneath it.
+function _freezeVocabulary(enumOpts) {
+  var out = {};
+  if (enumOpts && typeof enumOpts === "object") {
+    Object.keys(enumOpts).forEach(function (k) {
+      out[k] = Array.isArray(enumOpts[k]) ? Object.freeze(enumOpts[k].slice()) : enumOpts[k];
+    });
+  }
+  return Object.freeze(out);
+}
+
+// Every `*Policy` name this guard answers to: whatever its defaults carry, plus
+// whatever any profile or posture overlay can introduce, plus the vocabularies
+// declared for it. The union matters — a policy that only a strict profile sets
+// is still a real option, and `tagsPolicy` is governed through the family's
+// derivation without appearing in any defaults block.
+function _knownPolicyKeys(cfg) {
+  var known = Object.create(null);
+  function absorb(o) {
+    if (!o || typeof o !== "object") return;
+    Object.keys(o).forEach(function (k) {
+      if (/Policy$/.test(k)) known[k] = true;
+    });
+  }
+  absorb(cfg.defaults);
+  absorb(cfg.enumOpts);
+  [cfg.profiles, cfg.compliancePostures].forEach(function (table) {
+    if (!table || typeof table !== "object") return;
+    Object.keys(table).forEach(function (name) { absorb(table[name]); });
+  });
+  return known;
+}
+
+// Refuses a caller-supplied `*Policy` the guard has no such option for. Reads
+// the caller's own opts rather than the merged result, so a guard's internal
+// wiring is never the thing that fails, and stays silent for a guard that has
+// no policies at all — there, the suffix carries no meaning to trade on.
+function _refuseUnknownPolicyKeys(opts, resolved, cfg, ErrorClass, prefix) {
+  if (!opts || typeof opts !== "object") return;
+  var supplied = Object.keys(opts).filter(function (k) {
+    return /Policy$/.test(k) && opts[k] !== undefined;
+  });
+  if (!supplied.length) return;
+  var known = _knownPolicyKeys(cfg);
+  var names = Object.keys(known);
+  if (!names.length) return;
+  for (var i = 0; i < supplied.length; i += 1) {
+    if (known[supplied[i]]) continue;
+    throw ErrorClass.factory(prefix + ".bad-opt",
+      prefix + ": no option named " + JSON.stringify(supplied[i]) +
+      " — this guard's policies are " + names.sort().join(", "));
+  }
+}
+
 // The own enumerable properties of `o` that were actually given a value. A key
 // present with the value `undefined` is treated as absent, so it cannot erase
 // a default it was never meant to touch.
@@ -3458,6 +3594,14 @@ function defineGuard(spec) {
     // "non-negative integer", because derivation cannot tell a cap from a
     // tolerance. Exposed so the family tests can tell the two apart.
     INT_OPTS:            Object.freeze(Array.isArray(spec.intOpts) ? spec.intOpts.slice() : []),
+    // The value each policy option accepts, after the family's character
+    // policies are folded in. Exposed for the same reason as INT_OPTS: the
+    // family sweep has to ask each guard what it takes rather than assume one
+    // vocabulary for all of them. Where a guard pins a policy to a single
+    // value — guardFilename's traversal, guardJwt's alg=none — the answer is a
+    // one-element list, and a sweep that assumed otherwise would report the
+    // pinning as a regression.
+    POLICY_VOCABULARY:   _freezeVocabulary(_withCharPolicyEnums(defaults, spec)),
     validate:            spec.validate,
     resolveOpts:         _resolveGuardOpts,
     buildProfile:        buildProfileFn,
@@ -3821,6 +3965,8 @@ module.exports = {
   // list cannot drift away from them.
   capKeysOf:                capKeysOf,
   charPolicyEnums:          charPolicyEnums,
+  policyVocabulary:         policyVocabulary,
+  POLICY_VALUES:            POLICY_VALUES,
   identitySanitize:         identitySanitize,
   ctxValueFrom:             ctxValueFrom,
   runIssueValidator:  runIssueValidator,

package/lib/guard-archive.js

@@ -115,11 +115,12 @@ var MAGIC_SIGNATURES = Object.freeze([
 
 // Character-class policy for an entry NAME comes from `filenameProfile`, which
 // routes the name through b.guardFilename — this guard never reads a
-// bidi/control/null/zero-width policy of its own. It used to declare them in
-// every profile anyway, so an operator passing `zeroWidthPolicy` here was
-// configuring nothing and had no way to find that out. The declarations are
-// gone rather than wired, because `filenameProfile` is already the one place
-// that decides it and two spellings of the same setting is how they disagree.
+// bidi/control/null/zero-width policy of its own, and does not declare them in
+// its profiles either. Declaring an option nothing reads leaves an operator
+// setting `zeroWidthPolicy` here configuring nothing, with no way to find that
+// out. Wiring them instead would give the same setting two spellings, which is
+// how the two come to disagree, and `filenameProfile` is already the one place
+// that decides it.
 var PROFILES = Object.freeze({
   "strict": {
     traversalPolicy:           "reject",
@@ -197,6 +198,20 @@ var INT_OPTS = ["maxEntries", "maxTotalBytes", "maxEntryBytes",
 // DERIVED from DEFAULTS rather than written out, because a hand-kept list is
 // what drifted away from the defaults it was meant to mirror and left limits
 // unchecked across the family.
+// Each policy's vocabulary, so a misspelling is a boot error rather than a
+// runtime surprise. Read leniently, a typo takes whichever branch is not the
+// strict one: `symlinkPolicy: "rejct"` is not "allow", so the check runs, and
+// it is not "reject" either, so the finding drops from critical to warn.
+//
+// `audit-only` is deliberately absent, unlike elsewhere in the family:
+// nestedArchivePolicy tests for "audit" exactly, so the synonym would fall
+// past both branches and record nothing at all.
+var POLICY_ENUM = gateContract.policyVocabulary([
+  "traversalPolicy", "absolutePathPolicy", "symlinkPolicy", "hardlinkPolicy",
+  "nestedArchivePolicy", "duplicateNamePolicy", "caseInsensitiveCollisionPolicy",
+  "encryptionPolicy", "sparseEntryPolicy",
+], ["reject", "audit", "allow"]);
+
 function _resolveOpts(opts) {
   return gateContract.resolveProfileAndPosture(opts, {
     profiles:           PROFILES,
@@ -206,6 +221,7 @@ function _resolveOpts(opts) {
     errCodePrefix:      "archive",
     intOpts:            INT_OPTS,
     nonNegativeOpts:    gateContract.capKeysOf(DEFAULTS),
+    enumOpts:           POLICY_ENUM,
   });
 }
 
@@ -866,6 +882,9 @@ module.exports = {
   // ---- guard-* family registry exports (consumed by b.guardAll) ----
   NAME:                "archive",
   KIND:                "entries",                                                 // archive-entries guard (consumes ctx.entries)
+  // The value each policy accepts. Named here rather than derived, because
+  // this guard binds its own resolver instead of going through defineGuard.
+  POLICY_VOCABULARY:   POLICY_ENUM,
   INTEGRATION_FIXTURES: Object.freeze({
     kind:           "entries",
     contentType:    "application/zip",

package/lib/guard-auth.js

@@ -393,7 +393,35 @@ var INTEGRATION_FIXTURES = Object.freeze({
 // surface (validate / sanitize / bespoke gate) passed through verbatim.
 // The custom KIND ("auth-bundle") is accepted because the bespoke gate
 // reads its own ctx fields (ctx.authBundle / ctx.auth).
+// The policies this wrapper accepts on the wrapped guard's behalf, with the
+// wrapped guard's own vocabulary for each. Derived rather than restated: a
+// second copy of guardOauth's values here would be free to drift from the ones
+// the child actually enforces, and the operator would meet whichever of the
+// two happened to be wrong.
+//
+// Without this, forwarding `codeReusePolicy` through the wrapper failed at the
+// wrapper's own resolver, because the name belongs to the child and this
+// guard's profiles never mention it.
+//
+// The character policies are excluded even though they are forwarded: their
+// vocabulary is derived per guard from whether that guard can repair a
+// character, and this guard cannot. Taking the child's answer would hand this
+// one a `strip` it has no way to carry out the moment the two differ — the
+// substitution that accepting-then-refusing was introduced to stop.
+var CHILD_OWNED_POLICIES = Object.freeze([
+  "bidiPolicy", "controlPolicy", "nullBytePolicy", "zeroWidthPolicy", "tagsPolicy",
+]);
+var FORWARDED_POLICY_ENUM = Object.freeze(
+  OAUTH_FORWARDED_OPTS.reduce(function (acc, key) {
+    if (CHILD_OWNED_POLICIES.indexOf(key) !== -1) return acc;
+    var vocabulary = guardOauth.POLICY_VOCABULARY &&
+                     guardOauth.POLICY_VOCABULARY[key];
+    if (Array.isArray(vocabulary)) acc[key] = vocabulary;
+    return acc;
+  }, {}));
+
 var _guard = module.exports = gateContract.defineGuard({
+  enumOpts:    FORWARDED_POLICY_ENUM,
   name:        "auth",
   kind:        "auth-bundle",
   errorClass:  GuardAuthError,

package/lib/guard-cidr.js

@@ -494,10 +494,29 @@ var INTEGRATION_FIXTURES = gateContract.identifierFixtures("8.8.8.0/24", "10.0.0
 // standard serve -> audit-only -> refuse chain — reading ctx.identifier ||
 // ctx.cidr via ctxFields. No sanitize action: an allowlist gate never
 // rewrites the operator's stored network range.
+// Each policy's vocabulary, so a misspelling is a boot error rather than a
+// runtime surprise. Read leniently, a typo takes whichever branch is not the
+// strict one: `reservedRangesPolicy: "rejct"` is not "allow", so the check
+// runs, and it is not "reject" either, so the finding drops to a warning — the
+// operator asked to refuse a reserved range and silently got an audit.
+//
+// requireMaskPolicy carries its own spellings because the question is about the
+// mask rather than a threat disposition. `audit-only` rides with `audit` on the
+// three that take one, matching how the framework treats the two everywhere
+// else.
+var POLICY_ENUM = gateContract.policyVocabulary([
+  "networkAlignmentPolicy", "reservedRangesPolicy", "ipv4MappedIpv6Policy",
+], gateContract.POLICY_VALUES.rejectAuditAllow, {
+  // Names its own values because the finding is an absence — a bare address
+  // where a mask was expected — so "reject" alone would not say what of.
+  requireMaskPolicy: ["allow-bare-ip", "audit-bare-ip", "reject-bare-ip"],
+});
+
 module.exports = gateContract.defineGuard({
   name:        "cidr",
   kind:        "identifier",
   errorClass:  GuardCidrError,
+  enumOpts:    POLICY_ENUM,
   profiles:    PROFILES,
   base:        128,
   integrationFixtures: INTEGRATION_FIXTURES,

package/lib/guard-country.js

@@ -348,10 +348,10 @@ function _detectIssues(input, opts) {
  * @opts
  *   profile:            "strict"|"balanced"|"permissive",
  *   compliancePosture:  "hipaa"|"pci-dss"|"gdpr"|"soc2",
- *   bidiPolicy:         "reject"|"strip"|"audit"|"allow",
- *   controlPolicy:      "reject"|"strip"|"allow",
- *   nullBytePolicy:     "reject"|"strip"|"allow",
- *   zeroWidthPolicy:    "reject"|"strip"|"allow",
+ *   bidiPolicy:         "reject"|"audit"|"allow",
+ *   controlPolicy:      "reject"|"audit"|"allow",
+ *   nullBytePolicy:     "reject"|"audit"|"allow",
+ *   zeroWidthPolicy:    "reject"|"audit"|"allow",
  *   reservedPolicy:     "reject"|"audit"|"allow",
  *   userAssignedPolicy: "reject"|"audit"|"allow",
  *   formerlyUsedPolicy: "reject"|"audit"|"allow",

package/lib/guard-csv.js

@@ -639,7 +639,7 @@ function _stripIssues(text, opts) {
  * twice does not stack prefixes.
  *
  * @opts
- *   formulaInjectionPolicy: "prefix-tab"|"prefix-quote"|"wrap-with-quotes-and-prefix"|"reject"|"allowlist",
+ *   formulaInjectionPolicy: "prefix-tab"|"prefix-quote"|"wrap-with-quotes-and-prefix"|"reject"|"allowlist"|"audit-only"|"allow",
  *   formulasAllowlist:      string[],   // when policy === "allowlist"
  *   bidiCharPolicy:         "reject"|"strip"|"audit"|"allow",
  *   controlCharPolicy:      "reject"|"strip"|"allow",
@@ -1047,7 +1047,7 @@ function serialize(rows, opts) {
  *   controlCharPolicy:     "reject"|"strip"|"allow",
  *   nullByteHandling:      "reject"|"strip"|"allow",
  *   homoglyphPolicy:       "audit"|"strip"|"allow",
- *   formulaInjectionPolicy: "prefix-tab"|"prefix-quote"|"wrap-with-quotes-and-prefix"|"reject"|"audit-only"|"allow",
+ *   formulaInjectionPolicy: "prefix-tab"|"prefix-quote"|"wrap-with-quotes-and-prefix"|"reject"|"allowlist"|"audit-only"|"allow",
  *   dangerousFunctions:    string[],
  *   dialectPolicy:         "strict"|"permissive",
  *
@@ -1409,7 +1409,36 @@ var INTEGRATION_FIXTURES = Object.freeze({
 // extras (serialize / escapeCell / detect / schema / FORMULA_PREFIXES /
 // DANGEROUS_FUNCTIONS) passed through verbatim. The bespoke `gate` carries
 // CSV's sanitize-reparse-reserialize chain unchanged.
+// Each policy's vocabulary, so a misspelling is a boot error rather than a
+// runtime surprise. Read leniently, a typo takes whichever branch is not the
+// strict one: `formulaInjectionPolicy: "prefix-tabb"` is neither "allow" nor
+// "audit-only", so a mitigation is attempted, and it is not a spelling the
+// mitigation recognises — the operator asked for a tab prefix and got something
+// else without being told.
+//
+// The sets are the UNION of what the code compares, what the opts blocks
+// document and what the shipped profiles select, because no single source was
+// complete: the two opts blocks disagreed with each other, one listing
+// `allowlist` and the other `audit-only` / `allow`, while the code compares all
+// three. Both blocks now carry the full set.
+//
+// The last four are MODE settings rather than threat dispositions — a dialect,
+// a numeric rendering, whether whitespace is kept — so they share nothing with
+// the disposition vocabulary and are listed on their own terms.
+var POLICY_ENUM = Object.freeze({
+  formulaInjectionPolicy:   ["prefix-tab", "prefix-quote", "wrap-with-quotes-and-prefix",
+                             "reject", "allowlist", "audit-only", "allow"],
+  bidiCharPolicy:           ["reject", "strip", "audit", "allow"],
+  controlCharPolicy:        ["reject", "strip", "allow"],
+  homoglyphPolicy:          ["audit", "strip", "allow"],
+  trailingWhitespacePolicy: ["trim", "preserve", "reject"],
+  dialectPolicy:            ["strict", "permissive"],
+  numericPrecisionPolicy:   ["decimal-string-above-safe-int", "scientific", "reject-bigint"],
+  piiPolicy:                ["preserve", "redact"],
+});
+
 module.exports = gateContract.defineGuard({
+  enumOpts:    POLICY_ENUM,
   name:        "csv",
   kind:        "content",
   errorClass:  GuardCsvError,

package/lib/guard-domain.js

@@ -657,7 +657,29 @@ var INTEGRATION_FIXTURES = gateContract.identifierFixtures("example.com", "192.1
 // standard serve -> audit-only -> refuse chain — reading ctx.identifier ||
 // ctx.domain via ctxFields. No sanitize action: an allowlist gate never
 // rewrites the operator's stored allowlist key.
+// Each policy's vocabulary, taken from this guard's own documented opts above,
+// so a misspelling is a boot error rather than a runtime surprise. Read
+// leniently, a typo takes whichever branch is not the strict one:
+// `punycodePolicy: "rejct"` is not "allow", so the check runs, and it is not
+// "reject" either, so the finding drops to a warning — the operator asked to
+// refuse punycode and silently got an audit.
+//
+// trailingDotPolicy is deliberately different on both counts: it takes
+// `normalize` rather than `allow`, and it does NOT take `audit-only`, because
+// its check compares `=== "audit"` exactly and the synonym would not be
+// honoured. A shared list would have advertised it.
+var POLICY_ENUM = gateContract.policyVocabulary([
+  "ldhPolicy", "punycodePolicy", "mixedScriptPolicy", "specialUsePolicy",
+  "ipLiteralPolicy", "wildcardPolicy", "singleLabelPolicy", "underscorePolicy",
+  "dgaPolicy",
+], gateContract.POLICY_VALUES.rejectAuditAllow, {
+  // No `allow`, and no `audit-only`: a trailing dot is either removed or
+  // reported, and the code compares for "audit" exactly.
+  trailingDotPolicy: ["normalize", "audit", "reject"],
+});
+
 module.exports = gateContract.defineGuard({
+  enumOpts:    POLICY_ENUM,
   name:        "domain",
   kind:        "identifier",
   errorClass:  GuardDomainError,

package/lib/guard-email.js

@@ -1115,7 +1115,24 @@ var INTEGRATION_FIXTURES = Object.freeze({
 // the address/message entries (validateAddress / validateMessage) passed
 // through verbatim. The bespoke `gate` validates via validateMessage and
 // carries the serve->audit-only->refuse chain unchanged.
+// Each policy's vocabulary, so a misspelling is a boot error rather than a
+// runtime surprise. Read leniently, a typo takes whichever branch is not the
+// strict one: `crlfHeaderInjectionPolicy: "rejct"` is not "allow", so the
+// check runs, and it is not "reject" either, so a header-injection attempt
+// drops to a warning.
+//
+// The character policies are absent on purpose — they are derived for the
+// whole guard family, and an entry here would shadow that derivation.
+var POLICY_ENUM = gateContract.policyVocabulary([
+  "multiAtPolicy", "ipLiteralPolicy", "punycodePolicy", "mixedScriptPolicy",
+  "addressCommentPolicy", "crlfHeaderInjectionPolicy", "bareCrPolicy",
+  "bareLfPolicy", "smtpSmugglingPolicy", "displayNameSpoofPolicy",
+], gateContract.POLICY_VALUES.rejectAuditAllow, {
+  bomPolicy: gateContract.POLICY_VALUES.rejectStripAuditAllow,
+});
+
 module.exports = gateContract.defineGuard({
+  enumOpts:    POLICY_ENUM,
   name:        "email",
   kind:        "content",
   charRepair:  true,