diff --git a/AGENTS.md b/AGENTS.md
index e010b4a6c3..22f11869af 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -499,8 +499,8 @@ Even inside your own worktree, operate defensively:
 
    **Re-arm awareness** — none of these is a reason to avoid the queue; all are reasons to
    confirm a PR is still *in* it: a red queue build **ejects** your entry and drops
-   auto-merge, often on a package your PR never touched (the queue runs the full suite; the
-   PR ran affected-only) — diagnose against `merge-queue-triage.yml`'s comment, recognise a
+   auto-merge, often on a package your PR never touched (it runs the merge group's affected
+   set, not just yours) — diagnose against `merge-queue-triage.yml`'s comment, recognise a
    known-flaky signature, then re-arm once, never reflexively; **collateral eviction is
    silent** (triage comments only on `failure`, so an entry cancelled because something
    *ahead* failed gets nothing) — neither on `main` nor in the queue means dropped, re-arm;
diff --git a/scripts/check-cross-package-test-inputs.mjs b/scripts/check-cross-package-test-inputs.mjs
index ea7da9c6bb..5f6e5a9b18 100644
--- a/scripts/check-cross-package-test-inputs.mjs
+++ b/scripts/check-cross-package-test-inputs.mjs
@@ -22,9 +22,9 @@
 //
 //   Layer B -- turbo's task cache. `test` declares `inputs: ["$TURBO_DEFAULT$",
 //     ...]`, which is PACKAGE-LOCAL. `@objectstack/spec#test` therefore hashes
-//     the same before and after any change outside `packages/spec`, so even the
-//     merge-queue and push builds -- which deliberately partition the FULL
-//     package list, not the affected subset -- replay a cached green.
+//     the same before and after any change outside `packages/spec`, so even a
+//     build that partitions the FULL package list -- `push` on `main` today,
+//     the merge queue too until #16453 -- replays a cached green.
 //     Measured: `turbo run test --filter=@objectstack/spec` after the
 //     platform-objects edit printed `>>> FULL TURBO`, 42ms, replaying the
 //     previous run's log, while `--force` on the same tree failed the scan.