From aa1aabbb412ba1e741ccd74b9f5c377eb1b50431 Mon Sep 17 00:00:00 2001
From: rrs <276464689+robotrocketscience@users.noreply.github.com>
Date: Sun, 3 May 2026 08:05:05 -0700
Subject: [PATCH] docs(v2-reentry-queue): point H1 row at split issue #374
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

#199 split into #373 (H3, ships at v2.0) and #374 (H1, deferred bench-gated)
per docs/v2_enforcement.md. H2 dropped per spec § H2. Update the H1 queue
row from "issue #199 sub-track" to the actual issue (#374) so the queue
links to a live tracking issue rather than the closed umbrella.
---
 docs/V2_REENTRY_QUEUE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/V2_REENTRY_QUEUE.md b/docs/V2_REENTRY_QUEUE.md
index 0ab273f77..b68903840 100644
--- a/docs/V2_REENTRY_QUEUE.md
+++ b/docs/V2_REENTRY_QUEUE.md
@@ -25,7 +25,7 @@ Each row references its public spec memo and the GitHub issue that tracks re-ent
 - **Gate:** ≥3pp improvement on a classification-accuracy or onboard-quality `aelf bench` number, **and** a PRIVACY.md rewrite documenting per-provider trust surface and consent gate.
 - **Why deferred:** privacy regression (outbound to *N* providers vs. 1), determinism regression (non-deterministic by construction), *N×* per-onboard token cost, no published evidence that cross-model consensus measurably improves classification quality. Substrate-decision (#196 Option B) removed the strongest historical justification.
 
-### Directive detection (enforcement H1) — issue #199 sub-track
+### Directive detection (enforcement H1) — issue #374
 
 - **Spec:** [`docs/v2_enforcement.md`](v2_enforcement.md) § H1
 - **Disposition:** defer to v2.x. (H3 selective injection ships at v2.0; H2 compliance audit is dropped, not deferred.)