From 5a7e256e11965033dbf287c66ad058493b9ce641 Mon Sep 17 00:00:00 2001
From: dhgoal <153369624+dhgoal@users.noreply.github.com>
Date: Wed, 15 Jul 2026 23:16:10 +0200
Subject: [PATCH] docs(miner): fix stale header comment in
 submission-freshness-check

The header described the freshness -> prepareOpenPrSubmission -> Governor
composition as something "a future real call site" would wire together.
That call site already exists: attempt-runner.js composes runIterateLoop ->
checkSubmissionFreshness -> prepareOpenPrSubmission ->
evaluateGovernorChokepointGatePersisted in exactly that order (its own
module comment documents the same ordering, and it calls
checkSubmissionFreshness directly before prepareOpenPrSubmission).

Comment-only; no behavior change.

Closes #6163
---
 packages/loopover-miner/lib/submission-freshness-check.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/loopover-miner/lib/submission-freshness-check.js b/packages/loopover-miner/lib/submission-freshness-check.js
index be164cbb8..2d90b0d78 100644
--- a/packages/loopover-miner/lib/submission-freshness-check.js
+++ b/packages/loopover-miner/lib/submission-freshness-check.js
@@ -5,7 +5,7 @@
 // replacing, the claim-time check (src/miner/soft-claim.ts) -- so a stale submission never reaches the Governor
 // chokepoint (governor-chokepoint.js) as a live write attempt: check freshness first, THEN prepareOpenPrSubmission
 // (harness-submission-trigger.js), THEN the Governor. These are separate, sequentially-composed units, not nested
-// calls -- a future real call site wires them together in that order.
+// calls -- attempt-runner.js (#2337) is the real call site that wires them together in that order.
 //
 // READ-ONLY BY CONTRACT: never writes anything except its own abort-reason audit event (on staleness only, not
 // on every check -- mirrors this issue's own "log the abort reason" wording, not a per-decision audit trail).