Decide whether to allow a narrow scheduling test gate for the remaining UrlResolver deferred-cap race. Two independent audits found no existing public deterministic boundary; the testing guide bars adding an internal bridge without an explicit exception.
Owner decision needed on a narrow scheduling gate for the deferred-cap regression; two public-API audits found no existing deterministic boundary.
Written 2026-10-23 11:12 UTC.
RE-VERIFY: This is an unanswered owner decision at write time. Recheck the parent conversation before acting; no approval may be inferred from elapsed time.
The remaining cap race in https://github.com/CodexCoder21Organization/UrlResolver/pull/1499 removes a deferred snapshot descriptor under one lock and reinserts it after an out-of-lock held-peer read. Concurrent admissions can fill the freed slot and the active limit, so reinsertion can exceed the deferred cap.
Two independent audits found no existing public deterministic callback in the required interval. Clock, public bookkeeping, queue pauses and diagnostics occur outside it; registry/relay reads are final concrete implementations and the raw Host is private. The source/API audit is at https://github.com/CodexCoder21Organization/UrlResolver/tree/wip/FIX1499-evidence-20261023/lane-evidence (FIX1499-cap-boundary.md and FIX1499-cap-boundary-review.md).
The required Testing Architecture says "Visibility should never be increased purely for testing" and bars internal test bridges. A machine-dependent concurrency run would not force the exact contract condition and is also prohibited by the lane's reliable-reproducer rule.
Question: may the implementation add a narrowly scoped scheduling gate solely to force the cap regression, as an explicit exception to that testing rule? The recommended option is to permit that limited exception so the old failure can be demonstrated deterministically before changing the atomic transaction. The alternative is to keep this item open until an existing public deterministic schedule or a separately justified public module/API is available. No gate or cap fix has been added.
After the decision, the remaining work is a failing-first public behavior assertion driven by the approved ordering mechanism, an atomic promotion fix, a mutation control, independent review, a full locked local suite and the final PR source push/required-check watch. The validated other fixes are at https://github.com/CodexCoder21Organization/UrlResolver/tree/wip/FIX1499-fixes-20261023, head344dc34fecf992a17d519fc296a252a9b1b564fe. No merge, enqueue, publishing, deployment or restart is authorized.
Recorded agent work, including concurrent agents
No model usage has been recorded for this handoff yet.
Record work with handoff-cli usage report hf-2026-10-23-decide-whether-the-deferred-cap-regression-may-use-a-narrow-scheduling-gate.
No status reports yet.
Moves it out of every priority list and into ArchiveArea.