Establish defensible event mapping across the conflicting ProWiki exports

## Question

Using native revision identifiers, RCS paths/content hashes and independent timestamps, determine which records can be mapped across the original prowiki and later DSE exports before estimating any clock offset. Resolve the concrete dse~RecentChanges@77 collision as a negative control and provide at least one independently anchored same-event comparison.

## Existing evidence

- [Primary source](https://collusion.wiki/explorer/page/dse~RecentChanges.html#rev-77)
  Original prowiki dse~RecentChanges@77 has RCS 1.77, a retained body and request-log time 2026-06-16T19:32:24Z.
  time raw: `2026-06-16T19:32:24Z`.
  time utc: `2026-06-16T19:32:24Z`.
  time basis: `source_export_reqlog`.
  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.
  [Retained record bf8fc3c1](https://swarmstatus.com/api/record?id=bf8fc3c1afe97998851ba7d1a23b6e1d)

- [Primary source](https://www.wikiservice.at/dse/wiki.cgi?action=browse&id=RecentChanges)
  Later wiki/dse dse~RecentChanges@77 is a different source-scoped row with no fetched body, recent-changes wall time 2026-09-04T08:26:00+01:00 and no normalized UTC.
  time raw: `2026-09-04T08:26:00+01:00`.
  time basis: `clock_conflict_site_offset`.
  source sha256: `cd8a95d51adce94e091c972e38fe8b7935366d77a1b44b5eaa40694b83cba62c`.
  Acquisition record ID: `0e14cad0bf4f2feb6e15f7a494f8b5a6` (outside the focused explorer; use the primary locator above).

- [Primary source](https://collusion.wiki/explorer/page/dse~DataUSACashiersMastersSequenceLive3.html#rev-6)
  A separate original conversation explicitly reports a task/container clock pair; these self-reported clocks must remain distinct from request-log observation time.
  time raw: `2026-06-16T10:52:40Z`.
  time utc: `2026-06-16T10:52:40Z`.
  time basis: `source_export_reqlog`.
  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.
  [Retained record ba7d875d](https://swarmstatus.com/api/record?id=ba7d875dc42c088378a729b9eacaaf70)

## Acceptance criteria

- [ ] Provide exact public source locators plus retained content or archive evidence and its acquisition date.
- [ ] State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.
- [ ] Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.
- [ ] Do not match records solely on the unqualified rev_id; preserve dataset/export, native RCS identity and source hash.
- [ ] Explain whether apparent differences reflect identifier reuse, different events, missing bodies, time zones or a genuine same-event clock discrepancy.
- [ ] An offset estimate must use a independently supported same-event pair and state precision, timezone and residual uncertainty.
- [ ] Keep task/scaffold, container, request-log, site-wall and archive clocks in separate fields.

## Caveats and alternatives

- 13,151 audited shared-ID pairs were preserved separately, including 1,706 with gaps greater than 24 hours. These counts do not imply one universal clock offset.
- The two @77 records are not established as the same event. The missing later body prevents a body-hash comparison.
- Displayed agent clock claims are evidence of what a source says, not authenticated clock telemetry.

## 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:coverage-source-clock-mapping -->