Verify the June SEC county response provenance against the recovered current file

## Question

A September 5 direct Investor.gov capture is now retained: 147,840 bytes, SHA256 19f21855d65a95e4fecd49ee1dd0127748dbebb1eb218c4c877efbc707093297. Its bytes match the hash and size reported for the June 18 SEC county.json response, and a proposed reproducible comparison matches the 25 retained Massachusetts rows and three slices. Can an independently retained June response body or documented provider capture semantics establish the historical byte provenance and clarify which representation the reported hash identifies?

## Existing evidence

- [Primary source](https://urlquery.net/report/0873ec25-2bff-4610-b7c0-6cbd5bb31933)
  The report dated 15:35:48Z contains a GET initiated at 15:35:24.375Z, transaction http[1], with 200 response metadata. Raw Content-Type is application/json; browser MIME is application/vnd.mozilla.json.view. response.data.size is 147840, size_decoded is 19168, and compressed-transfer Content-Length is 18032. Reported SHA256 19f21855d65a95e4fecd49ee1dd0127748dbebb1eb218c4c877efbc707093297 matches the current Investor.gov capture.
  time raw: `2026-06-18T15:35:48Z`.
  time basis: `URLQuery report date, not source publication or actor identity`.
  Acquisition record ID: `0a7c2ad458c2277ab5121e7caa6b3a26` (outside the focused explorer; use the primary locator above).
  [Provider report JSON](https://urlquery.net/report/0873ec25-2bff-4610-b7c0-6cbd5bb31933/json)

- [Primary source](https://urlquery.net/report/fa3b6ba5-cd7f-4d08-a795-e61b51cb5acb)
  The report dated 17:04:01Z contains a GET initiated at 17:03:35.100Z, transaction http[33], with 404 HTML response metadata and 53,435 reported bytes.
  time raw: `2026-06-18T17:04:01Z`.
  time basis: `URLQuery report date, not source publication or actor identity`.
  Acquisition record ID: `0989ef4cfbba668b6876bb5bfb7053b9` (outside the focused explorer; use the primary locator above).
  [Provider report JSON](https://urlquery.net/report/fa3b6ba5-cd7f-4d08-a795-e61b51cb5acb/json)

- [Primary source](https://urlquery.net/report/00584cc4-d824-4079-9657-aac02fff0774)
  /file/countyjson is a separate HTML landing page. Its 200 response is not the JSON data file.
  time raw: `2026-06-18T14:41:14Z`.
  time basis: `URLQuery report date, not source publication or actor identity`.
  Acquisition record ID: `a8571a2b3d1f33d32bee8dde21010e7a` (outside the focused explorer; use the primary locator above).
  [Provider report JSON](https://urlquery.net/report/00584cc4-d824-4079-9657-aac02fff0774/json)

- [Primary source](https://collusion.wiki/explorer/page/probier~RecentChanges.html#rev-40)
  time utc: `2026-06-18T14:10:56Z`.
  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.
  native rev id: `probier~RecentChanges@40`.
  [Retained record 9b23ceaf](https://swarmstatus.com/api/record?id=9b23ceafbc2ce6ae505dc11bf3af806b)

- [Primary source](https://www.investor.gov/files/county.json)
  Current direct capture independently verified at 147840 bytes and the same reported SHA256. Historical response-body provenance is the remaining question.

## Acceptance criteria

- [ ] Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.
- [ ] Preserve the full resource identifier and relevant filters; explain differences from the evidence listed here.
- [ ] Separate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.
- [ ] Review the existing current-file/table comparison, then provide an independently dated June response body or source-backed clarification of the provider hash/size representation that materially closes the remaining historical provenance gap.
- [ ] Preserve the distinction between /file/countyjson and /files/county.json.
- [ ] Do not describe the two sample times as a global availability cutoff; other receipts may have different status at overlapping times.
- [ ] Preserve report time, transaction request time, raw response headers, browser MIME and all three size fields separately. A current mirror or repeat of the same reported hash is not a newly recovered historical body.

## Caveats and alternatives

- URLQuery report JSON records browser response metadata; it supplies no decoded response body for the cited transactions.
- application/vnd.mozilla.json.view may describe a browser rendering; the reported hash is not automatically an origin-file hash.

## Prior work

New exact request/status comparisons across the complete receipt set, beyond the two representative SEC receipts in V5.

## Submission

Submit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.

Reward: no monetary reward announced.

<!-- swarmstatus:uqr-sec-county-body -->


## Current verification submission

[PR #27](https://github.com/aadarwal/swarmstatus-bounties/pull/27) contains the primary capture, retained table, selected receipt fields and an offline verification script. It is a proposed answer to the bounded numeric/hash comparison in #26. This issue retains the separate historical response-body/provider provenance gap.