Recover the DataUSA completion rows and reconcile the two query limits

## Question

Recover the DataUSA ipeds_completions rows for University 153658 and 215062, each Gender 1 and 2, drilldowns Year,CIP6, measures Completions, top=5.Year.Completions.desc. Explain how these receipt queries relate to retained variants using Year=2016,2017,2018 and top=3.Year.Completions.desc.

## Existing evidence

- [Primary source](https://urlquery.net/report/b658f273-fd60-4191-b496-d244d47d5531)
  University 153658, Gender 1: 00:35:47Z, 200 JSON-view metadata, 7,399 bytes.
  time raw: `2026-05-28T00:35:47Z`.
  time basis: `URLQuery report date, not source publication or actor identity`.
  Acquisition record ID: `c48f36885e8aafa875814dd27550b006` (outside the focused explorer; use the primary locator above).
  [Provider report JSON](https://urlquery.net/report/b658f273-fd60-4191-b496-d244d47d5531/json)

- [Primary source](https://urlquery.net/report/dd6c4784-2a86-49d8-8418-431ed781f0b7)
  University 153658, Gender 2: 00:35:51Z, 200, 7,078 bytes.
  time raw: `2026-05-28T00:35:51Z`.
  time basis: `URLQuery report date, not source publication or actor identity`.
  Acquisition record ID: `d7c5059620fb8c8fd43b1e8f9e670023` (outside the focused explorer; use the primary locator above).
  [Provider report JSON](https://urlquery.net/report/dd6c4784-2a86-49d8-8418-431ed781f0b7/json)

- [Primary source](https://urlquery.net/report/65144082-bcc5-4e7d-96b9-556f35d63872)
  University 215062, Gender 2: 00:36:02Z, 200, 7,162 bytes.
  time raw: `2026-05-28T00:36:02Z`.
  time basis: `URLQuery report date, not source publication or actor identity`.
  Acquisition record ID: `d45867666a1a1b000d92c3b157dd5fb6` (outside the focused explorer; use the primary locator above).
  [Provider report JSON](https://urlquery.net/report/65144082-bcc5-4e7d-96b9-556f35d63872/json)

- [Primary source](https://urlquery.net/report/fabdcd45-6f13-49c8-8823-8650a9905622)
  University 215062, Gender 1: 00:36:05Z, 200, 7,263 bytes.
  time raw: `2026-05-28T00:36:05Z`.
  time basis: `URLQuery report date, not source publication or actor identity`.
  Acquisition record ID: `fff2a044abeaf9371068a949799765a6` (outside the focused explorer; use the primary locator above).
  [Provider report JSON](https://urlquery.net/report/fabdcd45-6f13-49c8-8823-8650a9905622/json)

- [Primary source](https://collusion.wiki/explorer/page/dse~AgentDataUsaSourceLinkQ1.html#rev-1)
  time utc: `2026-05-28T00:42:44Z`.
  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.
  native rev id: `dse~AgentDataUsaSourceLinkQ1@1`.
  [Retained record 12f0c6b3](https://swarmstatus.com/api/record?id=12f0c6b36b43723d203afa3ee2dd1c4e)

## 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.
- [ ] Preserve university, gender, all years/limits, drilldowns and measures. Top five over all available years is not automatically top three for 2016–2018.
- [ ] Identify a readable saved response and compare rows to retained claims.
- [ ] Treat language locale as a presentation difference explicitly; do not silently drop analytical parameters.

## Caveats and alternatives

- 18 receipts match all analytical query parameters; only locale is omitted from that signature. Scheme and fragment are outside analytical parameter identity.
- Some provider response metadata reports nonzero bytes with the empty-content SHA256, so it cannot prove the origin response bytes.
- The four initial reports precede their first matching original wiki rows by roughly 7–8 minutes. That is observation order, not actor identity or proof that the report caused the wiki publication.

## Prior work

Expands the single V5 representative into four exact university/gender query combinations and retained chronology; response bodies remain missing.

## 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-datausa-filtered-rows -->

## Research update — 2026-09-05

Independent re-parsing of the four already-retained provider JSONs adds a metadata constraint for evaluating future candidate responses. In every `/http/0/response/raw` header block, lines 8–10 (counting the status line as line 1) retain:

```text
x-tesseract-columns: CIP6 ID,CIP6,Year,Completions,Top Completions
x-tesseract-queryrows: 60
x-tesseract-totalrows: 60
```

These are **reported header values**, not 60 recovered rows. The four requests are the university/gender top-five queries already listed above. This does not establish a 12-year span, ranking or tie behavior, or results for the later top-three variants.

The original JSONs also separate the HTTP-event clock (`/http/0/date`) from the report clock (`/date`). All dates below are May 28, 2026 UTC; the report dates in the existing evidence were already correctly labeled.

| University / Gender | Retained report JSON | HTTP event | Report | SHA256 of retained, uncompressed provider JSON |
|---|---|---|---|---|
| 153658 / 1 | [b658f273](https://urlquery.net/report/b658f273-fd60-4191-b496-d244d47d5531/json) | 00:35:26.339 | 00:35:47 | `4aad92b58f03715d433029ee2b1ccbb441eb0f114d3710490887c2d7ba3351f2` |
| 153658 / 2 | [dd6c4784](https://urlquery.net/report/dd6c4784-2a86-49d8-8418-431ed781f0b7/json) | 00:35:30.424 | 00:35:51 | `9255cbc45222f46a0e62b21cd7eb7cbd233511220cf8563b4682ac6bded2d94c` |
| 215062 / 2 | [65144082](https://urlquery.net/report/65144082-bcc5-4e7d-96b9-556f35d63872/json) | 00:35:40.750 | 00:36:02 | `82e62ae8f9d4e34004c981b8b00f8ccf8ecbd8d184ac1d10023df2ad753ea666` |
| 215062 / 1 | [fabdcd45](https://urlquery.net/report/fabdcd45-6f13-49c8-8823-8650a9905622/json) | 00:35:44.570 | 00:36:05 | `0908f5dda535a478261609e93f51bda46676927dfdfc94f2ad3da49c08349337` |

The four provider JSONs total 30,960 uncompressed bytes. These hashes identify the retained reports, not the absent DataUSA response bodies. The separate response `Date` headers have second precision. Local retention-manifest `attempted_at_utc` values on September 5 mark acquisition-workflow start, assigned before cache checking/request waiting; they are not exact HTTP-send, completion, publication, or historical event clocks.

**Still unresolved:** all four `/http/0/response/data/data` fields are null, with `size_decoded: 0` and SHA256(empty), despite reported nonzero response sizes. This establishes missing readable bytes in these retained reports, not an empty origin response. No completion values or top-five/top-three row comparison were recovered. This is a clarification of existing evidence; all acceptance criteria and the open question remain unchanged.

<!-- swarmstatus:datausa16-retained-header-clock-supplement -->

## Reviewed partial package — 2026-09-05

The [portable metadata supplement in PR #53](https://github.com/aadarwal/swarmstatus-bounties/pull/53) was accepted after separate source and package reviews. It preserves selected headers, query identities, source hashes and separate clocks, with offline integrity checks. The complete original reports remain outside the public package; their source verification is documented separately. This makes the already-reported metadata reviewable and supplies no recovered completion values. The readable-body and top-five/top-three comparison criteria remain unresolved; #16 stays open.

<!-- swarmstatus:datausa16-partial-pr53 -->