@event4u/agent-config 16.1.0 → 16.3.0

package/src/scripts/hooks/host_lowering.yaml

@@ -23,11 +23,21 @@
 #   - src/scripts/hooks/host_semantics.ts   (VERIFIED_PLATFORMS, isBlockCapable, emission shape)
 #   - src/scripts/_lib/host_bindings.ts     (per-host bridge bindings + the install smoke probe)
 #   - src/scripts/lint_hook_manifest.ts     (schema + expiry gate)
+#   - src/scripts/check_host_docs_digest.ts (docs-drift watcher over `verified.docs_digest`)
 #
 # COLUMNS
 #   block_exit       exit code this host honours as a refusal on that slot;
 #                    `null` = this tree has not established that it honours one.
+#   answered_at      the date the pair above was last answered — REQUIRED on
+#                    every slot. A `block_exit: null` with no date is
+#                    indistinguishable from a slot nobody looked at, and that
+#                    ambiguity is what this column removes. The citation for the
+#                    answer is the row's `verified.docs_url` unless the slot
+#                    carries its own `docs_url:`.
 #   json_shape       structured-output envelope the dispatcher may emit.
+#                    `none` means this package has no native envelope for the
+#                    host, so `emitFor` keeps the legacy pass-through even when
+#                    the row is verified — see host_semantics.usesNativeEmission.
 #   entry_shape      shape of the bridge entry the installer writes.
 #   fail_policy      `propagate` = the dispatcher's exit code reaches the host;
 #                    `discard`   = the trampoline exits 0 regardless.
@@ -35,10 +45,32 @@
 #   timeout_default  host default for that timeout. `null` = not established here.
 #   verified         provenance of the row, or `null`. `expires` is mandatory
 #                    when the block is present — see lint_hook_manifest.
+#                    `docs_digest` is the sha256 of the `docs_url` body as last
+#                    ESTABLISHED for the row — recorded by a human-run fill,
+#                    never silently updated. On drift the watcher leaves it
+#                    alone and moves `expires` instead, so the field keeps
+#                    naming the body someone actually read. It is NOT paired
+#                    with `docs_at`, and the committed rows prove why: all nine
+#                    carry `docs_at: 2026-09-29` while the eight digests were
+#                    taken 2026-10-01. The two answer different questions —
+#                    `docs_at` when a human read the page for the row's ANSWERS,
+#                    `docs_digest` which body the watcher is comparing against.
+#                    `check_host_docs_digest --fetch` re-reads and flags a
+#                    difference.
 #   slots            ORDERED. Bridge entries are written in this order, so the
 #                    order is part of the generated output and must not be
 #                    sorted. `native` may be a list where one slot has two
 #                    native events (cline session_start).
+#
+# THE `expires` POLICY, STATED RATHER THAN IMPLIED. No host this package
+# supports publishes a documentation cadence, so no `expires` here is a vendor
+# commitment — each one is a review-by date this package chose. Rows established
+# by a dated documentation read carry `docs_at` + 1 year. `claude` keeps its
+# committed 2027-09-06 because that value predates this policy and nothing in
+# this change gives a reason to move it. The real drift signal is
+# `docs_digest`: when the watcher sees a changed body it sets `expires` to the
+# day BEFORE the detection date, because `lint_hook_manifest` tests `expires <
+# today` — "valid through yesterday" is how a row stops being current today.
 schema_version: 1
 
 hosts:
@@ -52,24 +84,32 @@ hosts:
         timeout_default: null
         # Transcribed from the behaviour host_semantics.ts already implements —
         # this row is a description of the status quo, not a new claim.
-        # docs_at/host_version are null because the original read was never
-        # dated; that absence is the record, and the lint reports it.
+        # `docs_at` / `host_version` were null until 2026-09-29: the original
+        # read was never dated, and the absence was the record. Both are filled
+        # now from sources this tree already carries — the 2026-09-06 live probe
+        # recorded in `host_semantics.ts` (Claude Code 2.1.263) and a fresh
+        # documentation read on 2026-09-29. `expires` is deliberately unchanged.
+        #
+        # The committed `docs_url` was `https://docs.claude.com/en/docs/claude-code/hooks`,
+        # which answers 301 and lands on the URL below. Recording the redirect
+        # target is what makes a digest reproducible.
         verified:
-          docs_at: null
-          docs_url: https://docs.claude.com/en/docs/claude-code/hooks
-          probe_at: null
-          host_version: null
+          docs_at: 2026-09-29
+          docs_url: https://code.claude.com/docs/en/hooks.md
+          docs_digest: 9dd68316c1111c118e3ddb82861ac6271a8cd164cee0d371b26165efff35fe88
+          probe_at: 2026-09-06
+          host_version: 2.1.263
           expires: 2027-09-06
         slots:
-          session_start:      { native: SessionStart,      block_exit: null }
-          session_end:        { native: SessionEnd,        block_exit: null }
-          stop:               { native: Stop,              block_exit: 2 }
-          user_prompt_submit: { native: UserPromptSubmit,  block_exit: 2 }
-          pre_tool_use:       { native: PreToolUse,        block_exit: 2 }
-          post_tool_use:      { native: PostToolUse,       block_exit: null }
-          pre_compact:        { native: PreCompact,        block_exit: null }
-          subagent_start:     { native: SubagentStart,     block_exit: null }
-          subagent_stop:      { native: SubagentStop,      block_exit: null }
+          session_start:      { native: SessionStart,      block_exit: null, answered_at: 2026-09-29 }
+          session_end:        { native: SessionEnd,        block_exit: null, answered_at: 2026-09-29 }
+          stop:               { native: Stop,              block_exit: 2,    answered_at: 2026-09-29 }
+          user_prompt_submit: { native: UserPromptSubmit,  block_exit: 2,    answered_at: 2026-09-29 }
+          pre_tool_use:       { native: PreToolUse,        block_exit: 2,    answered_at: 2026-09-29 }
+          post_tool_use:      { native: PostToolUse,       block_exit: null, answered_at: 2026-09-29 }
+          pre_compact:        { native: PreCompact,        block_exit: null, answered_at: 2026-09-29 }
+          subagent_start:     { native: SubagentStart,     block_exit: null, answered_at: 2026-09-29 }
+          subagent_stop:      { native: SubagentStop,      block_exit: null, answered_at: 2026-09-29 }
 
   augment:
     surfaces:
@@ -81,13 +121,30 @@ hosts:
         fail_policy: discard
         timeout_unit: unknown
         timeout_default: null
-        verified: null
+        # Established by a documentation read on 2026-09-29, not by a live
+        # probe — `probe_at` stays null and says so.
+        verified:
+          docs_at: 2026-09-29
+          docs_url: https://docs.augmentcode.com/cli/hooks.md
+          docs_digest: e500823be8303717020c1823f670e06d100108f6e3ac4b8d12a46d91fd1898fa
+          probe_at: null
+          host_version: null
+          expires: 2027-09-29
+        # THE FINDING THIS ROW CARRIES. Augment's own documentation states that
+        # `PreToolUse` can block tool execution and shows `exit 2` doing it. The
+        # `block_exit: null` below is therefore NOT a claim that the host cannot
+        # refuse — this file's header says a row never makes that claim. It is a
+        # fact about this package: `augment-dispatcher.sh` exits 0
+        # unconditionally (`fail_policy: discard`), so no verdict this package
+        # produces can reach the host at all. Arming it means changing the
+        # trampoline, which is an enforcement expansion and belongs to its own
+        # change with its own ratification — not to a dating pass.
         slots:
-          session_start:  { native: SessionStart,  block_exit: null }
-          session_end:    { native: SessionEnd,    block_exit: null }
-          stop:           { native: Stop,          block_exit: null }
-          pre_tool_use:   { native: PreToolUse,    block_exit: null }
-          post_tool_use:  { native: PostToolUse,   block_exit: null }
+          session_start:  { native: SessionStart,  block_exit: null, answered_at: 2026-09-29 }
+          session_end:    { native: SessionEnd,    block_exit: null, answered_at: 2026-09-29 }
+          stop:           { native: Stop,          block_exit: null, answered_at: 2026-09-29 }
+          pre_tool_use:   { native: PreToolUse,    block_exit: null, answered_at: 2026-09-29 }
+          post_tool_use:  { native: PostToolUse,   block_exit: null, answered_at: 2026-09-29 }
 
   cursor:
     surfaces:
@@ -97,13 +154,19 @@ hosts:
         fail_policy: propagate
         timeout_unit: unknown
         timeout_default: null
-        verified: null
+        verified:
+          docs_at: 2026-09-29
+          docs_url: https://cursor.com/docs/hooks.md
+          docs_digest: 7294a2d63b19d79a5283c948afe174cba8b06a7585563d34a2c41b90f5df0d39
+          probe_at: null
+          host_version: null
+          expires: 2027-09-29
         slots:
-          session_start:      { native: sessionStart,        block_exit: null }
-          session_end:        { native: sessionEnd,          block_exit: null }
-          stop:               { native: stop,                block_exit: null }
-          user_prompt_submit: { native: beforeSubmitPrompt,  block_exit: null }
-          post_tool_use:      { native: postToolUse,         block_exit: null }
+          session_start:      { native: sessionStart,        block_exit: null, answered_at: 2026-09-29 }
+          session_end:        { native: sessionEnd,          block_exit: null, answered_at: 2026-09-29 }
+          stop:               { native: stop,                block_exit: null, answered_at: 2026-09-29 }
+          user_prompt_submit: { native: beforeSubmitPrompt,  block_exit: null, answered_at: 2026-09-29 }
+          post_tool_use:      { native: postToolUse,         block_exit: null, answered_at: 2026-09-29 }
 
   cline:
     surfaces:
@@ -115,13 +178,27 @@ hosts:
         fail_policy: discard
         timeout_unit: unknown
         timeout_default: null
-        verified: null
+        # SECOND FINDING FROM THE 2026-09-29 READ. `docs.cline.bot`'s hooks page
+        # is now a one-line pointer to its SDK-plugins page and names none of
+        # the `TaskStart` / `TaskResume` / `TaskComplete` / `TaskCancel` events
+        # the slots below bind. The row is dated against the page that exists,
+        # and the digest watcher is what will surface the next move; re-deriving
+        # the event names from a page that no longer lists them is a separate
+        # piece of work, and inventing a citation for them here would be the
+        # defect this file was built to remove.
+        verified:
+          docs_at: 2026-09-29
+          docs_url: https://docs.cline.bot/customization/hooks.md
+          docs_digest: ef87561721f4cb80fe6d682b6866d638a4952dd416d36cd5ab398426ce64084b
+          probe_at: null
+          host_version: null
+          expires: 2027-09-29
         slots:
-          session_start:      { native: [TaskStart, TaskResume], block_exit: null }
-          session_end:        { native: TaskComplete,            block_exit: null }
-          stop:               { native: TaskCancel,              block_exit: null }
-          user_prompt_submit: { native: UserPromptSubmit,        block_exit: null }
-          post_tool_use:      { native: PostToolUse,             block_exit: null }
+          session_start:      { native: [TaskStart, TaskResume], block_exit: null, answered_at: 2026-09-29 }
+          session_end:        { native: TaskComplete,            block_exit: null, answered_at: 2026-09-29 }
+          stop:               { native: TaskCancel,              block_exit: null, answered_at: 2026-09-29 }
+          user_prompt_submit: { native: UserPromptSubmit,        block_exit: null, answered_at: 2026-09-29 }
+          post_tool_use:      { native: PostToolUse,             block_exit: null, answered_at: 2026-09-29 }
 
   windsurf:
     surfaces:
@@ -131,11 +208,20 @@ hosts:
         fail_policy: propagate
         timeout_unit: unknown
         timeout_default: null
-        verified: null
+        # THIRD FINDING FROM THE 2026-09-29 READ. `docs.windsurf.com` now
+        # redirects to `docs.devin.ai`; the redirect target is recorded so the
+        # digest is reproducible.
+        verified:
+          docs_at: 2026-09-29
+          docs_url: https://docs.devin.ai/desktop/cascade/hooks.md
+          docs_digest: 460ffe7aa91998804920f6722c0153b9948eadd5edafa19582298475a19835a2
+          probe_at: null
+          host_version: null
+          expires: 2027-09-29
         slots:
-          session_start:      { native: post_setup_worktree,   block_exit: null }
-          user_prompt_submit: { native: pre_user_prompt,       block_exit: null }
-          stop:               { native: post_cascade_response, block_exit: null }
+          session_start:      { native: post_setup_worktree,   block_exit: null, answered_at: 2026-09-29 }
+          user_prompt_submit: { native: pre_user_prompt,       block_exit: null, answered_at: 2026-09-29 }
+          stop:               { native: post_cascade_response, block_exit: null, answered_at: 2026-09-29 }
 
   gemini:
     surfaces:
@@ -149,14 +235,21 @@ hosts:
         # 0.50.0 in an isolated scratch workspace and could not run: the CLI
         # aborts with IneligibleTierError before any turn begins, so no tool
         # call and therefore no BeforeTool hook is reachable. An unrunnable
-        # probe establishes nothing, so this stays null.
-        verified: null
+        # probe establishes nothing, which is why `probe_at` is still null —
+        # the block below rests on the 2026-09-29 documentation read alone.
+        verified:
+          docs_at: 2026-09-29
+          docs_url: https://geminicli.com/docs/hooks/reference.md
+          docs_digest: 06d37f2f66812ee78bb46c37a112203376f0bae4d3b8b44ac79d0bda4b86a118
+          probe_at: null
+          host_version: null
+          expires: 2027-09-29
         slots:
-          session_start:      { native: SessionStart, block_exit: null, matcher: "" }
-          session_end:        { native: SessionEnd,   block_exit: null, matcher: "" }
-          stop:               { native: AfterAgent,   block_exit: null, matcher: "" }
-          user_prompt_submit: { native: BeforeAgent,  block_exit: null, matcher: "" }
-          post_tool_use:      { native: AfterTool,    block_exit: null, matcher: ".*" }
+          session_start:      { native: SessionStart, block_exit: null, answered_at: 2026-09-29, matcher: "" }
+          session_end:        { native: SessionEnd,   block_exit: null, answered_at: 2026-09-29, matcher: "" }
+          stop:               { native: AfterAgent,   block_exit: null, answered_at: 2026-09-29, matcher: "" }
+          user_prompt_submit: { native: BeforeAgent,  block_exit: null, answered_at: 2026-09-29, matcher: "" }
+          post_tool_use:      { native: AfterTool,    block_exit: null, answered_at: 2026-09-29, matcher: ".*" }
 
   cowork:
     surfaces:
@@ -168,7 +261,18 @@ hosts:
         fail_policy: discard
         timeout_unit: unknown
         timeout_default: null
-        verified: null
+        # `docs_url` is null and that is the answer, not a gap: the 2026-09-29
+        # sweep found no public hook documentation for this host to cite. What
+        # the row records is this tree's own finding, restated above the
+        # `slots: {}` below — nothing is bound, so there is no pair to date.
+        # `docs_digest` is null for the same reason: there is no body to hash.
+        verified:
+          docs_at: 2026-09-29
+          docs_url: null
+          docs_digest: null
+          probe_at: null
+          host_version: null
+          expires: 2027-09-29
         slots: {}
 
   copilot:
@@ -181,5 +285,117 @@ hosts:
         timeout_default: null
         # `fallback_only: true` in hook_manifest.yaml. This package binds
         # nothing here and has measured nothing here.
-        verified: null
+        #
+        # THE PHASE-2 FINDING, RECORDED WHERE IT IS READ. The 2026-09-29
+        # documentation check found that the host DOES document lifecycle hooks
+        # — `sessionStart`, `sessionEnd`, `userPromptSubmitted`, `preToolUse`,
+        # `postToolUse`, `agentStop`, `subagentStop`, `errorOccurred` — at
+        # `~/.copilot/hooks/*.json`. So the roadmap's dated zero does NOT apply
+        # to this host, and the row below is a dated statement about this
+        # package, not about the host: nothing is bound, so `slots:` stays
+        # empty.
+        #
+        # CORRECTED 2026-10-01, and the correction is the point of this file.
+        # This comment previously ended "...with `preToolUse` fail-closed on
+        # exit 2". **The cited page does not say that.** It was re-fetched on
+        # 2026-10-01 — hashing byte-identical to the `docs_digest` below, so the
+        # body read is provably the body pinned — and it contains NO exit-code
+        # semantics at all: no `exit 2`, no non-zero convention, no stderr
+        # contract. What it documents is the CAPABILITY — `preToolUse` "can
+        # approve or deny tool executions" — and a `version`/`type`/`bash`/
+        # `cwd`/`env`/`timeoutSec` config shape. The mechanism is undocumented
+        # on that page.
+        #
+        # A capability is not a contract, and writing the contract in anyway is
+        # precisely the "statement about what a host can do that the tree has
+        # not established" this file's header forbids. The claim was inherited
+        # rather than invented here, and it survived two readings before a
+        # review fetched the page and grepped it; that is the whole argument for
+        # `docs_digest` existing, so it is recorded rather than quietly deleted.
+        #
+        # WHY `probe_at` IS STILL NULL ON 2026-10-01, STATED SO IT IS NOT READ
+        # AS AN OVERSIGHT. The sibling `codex` row was probed on that date
+        # because `codex` is installed on the machine that ran the pass. The
+        # Copilot CLI is not installed and `~/.copilot` carries no binary, so
+        # there was no host to run a deny against. That is an absence of
+        # opportunity, not an absence of effort, and it is the one thing
+        # blocking this row from carrying what the codex row now carries.
+        #
+        # The codex probe is also the reason this row should NOT be armed from
+        # its documentation alone — though the argument is WEAKER than it first
+        # read, and the weaker version is the true one. On the sibling host a
+        # documented exit-2 refusal did not reproduce on the installed build.
+        # Here there is no documented exit-2 contract to arm in the first place
+        # (see the correction above), so this host is further from a binding
+        # than codex, not equally close. Either way the gate is the same: a
+        # probe, never a re-read.
+        verified:
+          docs_at: 2026-09-29
+          docs_url: https://docs.github.com/en/copilot/concepts/agents/hooks.md
+          docs_digest: bfd40aa93ad62133efc17a50f189034f01594dc89a5d31a13a0c541d691acede
+          probe_at: null
+          host_version: null
+          expires: 2027-09-29
+        slots: {}
+
+  codex:
+    surfaces:
+      any:
+        entry_shape: none
+        json_shape: none
+        fail_policy: discard
+        timeout_unit: unknown
+        timeout_default: null
+        # THE OTHER HALF OF THE PHASE-2 FINDING. Until 2026-09-29 this file had
+        # no `codex` row at all, and `docs/enforcement-by-host.md` called that
+        # "the third kind of absence" — no row because no `platforms:` key. The
+        # documentation check replaced the absence with an answer: Codex
+        # documents `SessionStart`, `SessionEnd`, `SubagentStart`,
+        # `SubagentStop`, `PreToolUse`, `PermissionRequest`, `PostToolUse`,
+        # `PreCompact`, `PostCompact`, `UserPromptSubmit`, `Stop` and
+        # `Interrupt` at `~/.codex/hooks.json`, in a config shape and with an
+        # `exit 2` + `hookSpecificOutput` contract that match Claude Code's.
+        #
+        # The row exists so the fact is dated and citable. `slots: {}` is the
+        # honest state of THIS package: no `platforms.codex` block, no
+        # trampoline, nothing installed. A row with slots the installer does
+        # not write would be the claim-without-evidence this file refuses.
+        #
+        # LIVE PROBE, 2026-10-01 — AND IT DID NOT REPRODUCE THE DOCUMENTED
+        # DENY. The paragraph above ends "...a contract that match Claude
+        # Code's", which was read off the vendor page and had never been run.
+        # It has now been run, against the installed `codex-cli 0.148.0`:
+        #
+        #   - An isolated `CODEX_HOME` was given a `hooks.json` binding
+        #     `PreToolUse` with `matcher: "Bash"` to a script that writes to
+        #     stderr and exits 2 — the documented refusal path, verbatim.
+        #   - `codex exec --sandbox read-only "Run the shell command: echo …"`
+        #     executed the shell call and returned its output. The call was
+        #     NOT refused.
+        #   - The feature is not switched off: `codex features list` reports
+        #     `hooks  stable  true` on this build.
+        #
+        # WHAT THAT ESTABLISHES, AND WHAT IT EXPLICITLY DOES NOT. It establishes
+        # that `block_exit` must stay null: this package has no demonstrated
+        # refusal path on this host, which is exactly what a null means here. It
+        # does NOT establish that Codex cannot refuse — this file's header
+        # forbids that reading, and two unexcluded explanations remain. The
+        # installed build is 0.148.0 against a current 0.159.3, and the page
+        # that was read describes the current one; and the probe never
+        # distinguished "the hook fired and was ignored" from "the matcher never
+        # matched", because the instrumented re-run (a hook that records its own
+        # input before refusing) was refused by the harness this probe ran
+        # under. A marker-file re-run on >= 0.159.3 is the one cheap experiment
+        # that would separate them, and it is named here rather than guessed at.
+        #
+        # The practical consequence is that a docs-only reading would have
+        # armed a refusal this tree cannot demonstrate. The row records the
+        # negative instead.
+        verified:
+          docs_at: 2026-09-29
+          docs_url: https://developers.openai.com/codex/hooks.md
+          docs_digest: 724881d81f1a9fdb35ea42d4851a11b1f6606bbc6e9d2d05c1e8c466fc25c630
+          probe_at: 2026-10-01
+          host_version: 0.148.0
+          expires: 2027-09-29
         slots: {}

package/src/scripts/hooks/host_semantics.ts

@@ -60,6 +60,34 @@ export interface Emission {
  */
 export const VERIFIED_PLATFORMS: ReadonlySet<string> = verifiedPlatforms();
 
+/**
+ * Does this platform have a NATIVE emission shape this package can produce?
+ *
+ * WHY THIS IS A SECOND PREDICATE AND NOT JUST `VERIFIED_PLATFORMS`. The set
+ * above answers "has anyone dated this row", and until 2026-09-29 exactly one
+ * host carried a `verified` block, so the two questions had the same answer and
+ * one predicate served both. Dating the other seven rows separated them: those
+ * rows are cited now, and every one of them declares `json_shape: none` —
+ * this package has no structured envelope for them. Gating `emitFor` on
+ * verified-ness alone would therefore have started writing Claude Code's
+ * `hookSpecificOutput` JSON onto hosts that parse no such thing, as a side
+ * effect of a documentation read. That is precisely the "speculative mapping"
+ * this module's header calls the same class of bug it exists to remove.
+ *
+ * So the emission branch reads the shape, and the shape is what the table says.
+ * Both halves are required: an expired citation falls back exactly as an absent
+ * one does, and a row with no envelope falls back however current its citation.
+ */
+export function usesNativeEmission(platform: string): boolean {
+    if (!VERIFIED_PLATFORMS.has(platform)) return false;
+    // An ABSENT row reads as no envelope, not as one. The optional chain must
+    // not fall through to `undefined !== "none"`, which is true and would make
+    // a missing row the most permissive answer in the function — the inversion
+    // this module's header calls speculative mapping.
+    const shape = surfaceRow(platform, DEFAULT_SURFACE, loadHostLowering())?.json_shape ?? "none";
+    return shape !== "none";
+}
+
 /** Internal event name -> host-native event name, for structured output. */
 function nativeEventName(platform: string, event: string): string {
     return surfaceRow(platform, DEFAULT_SURFACE, loadHostLowering())?.slots.get(event)?.native[0] ?? event;
@@ -187,7 +215,7 @@ export function claudePermissionDecision(
  * copy one module away is a copy that drifts.
  */
 export function emissionCarriesReasons(platform: string, severity: Severity): boolean {
-    if (!VERIFIED_PLATFORMS.has(platform)) return false;
+    if (!usesNativeEmission(platform)) return false;
     return severity !== "allow";
 }
 
@@ -219,7 +247,7 @@ export function emitFor(
     legacyExit: number,
     permission?: PermissionEmission | null,
 ): Emission {
-    if (!VERIFIED_PLATFORMS.has(platform)) {
+    if (!usesNativeEmission(platform)) {
         return { exit: legacyExit, stdout: "", stderr: "" };
     }
     const reason = _joinReasons(reasons);

package/src/scripts/hooks/injection_budget.ts

@@ -67,7 +67,7 @@ import * as fs from "node:fs";
 import * as path from "node:path";
 
 import { log_dispatch_issue } from "./dispatch_issues.js";
-import { VERIFIED_PLATFORMS, emissionCarriesReasons, type Severity } from "./host_semantics.js";
+import { emissionCarriesReasons, usesNativeEmission, type Severity } from "./host_semantics.js";
 
 /**
  * The event that STARTS a turn, and therefore the one that resets the per-turn
@@ -605,7 +605,14 @@ function _sessionKey(ctx: ShapingContext): string | null {
  * whose turn boundary cannot be observed, must never become a budget of zero.
  */
 export function resolveVolumeCap(ctx: ShapingContext): number | null {
-    if (!VERIFIED_PLATFORMS.has(ctx.platform)) return null;
+    // NOT `VERIFIED_PLATFORMS`: a row being dated says someone read the host's
+    // page, never that this package has an envelope to put on it. Since
+    // 2026-09-29 every row is dated, so the verified set is no longer the set
+    // whose emission carries anything — `usesNativeEmission` is. Reading the
+    // wider set here would have started metering bytes on six hosts that
+    // receive none, and a ceiling charged for undelivered output drops the
+    // NEXT advisory, which does get delivered.
+    if (!usesNativeEmission(ctx.platform)) return null;
     if (_sessionKey(ctx) === null) return null;
     if (!_turnStartBound(ctx.packageRoot, ctx.platform)) return null;
     try {

package/src/scripts/hooks/interruption_ledger_hook.ts

@@ -60,8 +60,7 @@ import { derive_session_tag } from '../chat_history.js';
 import { unwrap, type JsonObject, type JsonValue } from './envelope.js';
 import { readHookStdin } from './hook_stdin.js';
 import { HANDBACK, finalParagraph, readTranscriptTail } from './turn_end_gate_hook.js';
-
-const EXIT_OK = 0;
+import { EXIT_ALLOW as EXIT_OK } from './exit_codes.js';
 
 /** Same cap the turn-end gate reads its tail under. */
 const TRANSCRIPT_READ_MAX_BYTES = 2 * 1024 * 1024;

package/src/scripts/hooks/journal_record_hook.ts

@@ -102,8 +102,7 @@ import {
 } from '../_lib/runtime_journal.js';
 import { readHookStdin } from './hook_stdin.js';
 import { is_replay_mode } from './state_io.js';
-
-const EXIT_ALLOW = 0;
+import { EXIT_ALLOW } from './exit_codes.js';
 
 /** The `.agent-settings.yml` section under `hooks:` that arms this concern. */
 export const SETTINGS_SECTION = 'runtime_journal';

package/src/scripts/hooks/memory_recall_hook.ts

@@ -68,13 +68,12 @@ import { COMMAND_TOOLS } from '../before_complete_hook.js';
 import { unwrap, type JsonObject, type JsonValue } from './envelope.js';
 import { readHookStdin } from './hook_stdin.js';
 import { atomic_write_json } from './state_io.js';
+import { EXIT_ALLOW, EXIT_WARN } from './exit_codes.js';
 
-const EXIT_ALLOW = 0;
 /**
  * Severity comes from the exit code, not from the `decision` field. See the
  * header: this never blocks, and never returns 1 on any path.
  */
-const EXIT_WARN = 2;
 
 /** Hard ceiling on `reason` + `additional_context`, matching the registered row. */
 export const CAP_BYTES = 768;