GitHub mirror is fully frozen (main + tags + releases at July 1 / v0.5.8): no live sync path after mirror-to-github removal #646

New issue

Open

opened 2026-07-07 22:49:10 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-07 22:49:10 +00:00

Member

Follow-up to #477 (contract half landed in 3290adc).

What #477 fixed

The documented-vs-observed contradiction is resolved in-repo: AGENTS.md no longer claims mirror-to-github.yml mirrors refs, and the dangling references to the removed workflow / deleted docs/github-mirror.md were scrubbed from release.yml, pyproject.toml, and the GitHub issue config.

What could NOT be done from a container, and why

The observable half of #477's done-condition (mirror shows zero-stale-or-matching releases, plus a pointer on the mirror) is not met, and cannot be met by any warded container:

The GitHub mirror's main HEAD is stuck at 4c8e694 (2026-07-01 11:18), tags at v0.5.8 (36 total), releases at v0.5.8 (all github-actions[bot]-authored). Not just the releases page - the whole mirror is frozen, because the only thing that pushed it (mirror-to-github.yml) went PAT-less ~July 1 and was then removed entirely (b55f69f).
A container has no write path to the mirror: no gh, no GITHUB_TOKEN in env (only FORGEJO_TOKEN), the read MCP surface has no delete-release tool, and create_or_update_file returns 403 (integration is read-only for this repo). This is the same human-credential wall that blocked the three prior #477 attempts.

Human action needed (pick one)

Restore a live ref sync - either provision GITHUB_MIRROR_PAT (push + repo/release scope) in ward -> Settings -> Actions -> Secrets and reinstate a minimal ref-push, or configure a native Forgejo push mirror (repo Settings -> Mirror) so main + tags stay current without an Actions secret.
One-time scrub the stranded github-actions[bot] v0.5.x release objects (v0.4.0 -> v0.5.8) so the Releases page stops reading "latest v0.5.8". Deleting a release does not delete its tag.
Add a mirror-README banner pointing at the canonical Forgejo release page (the "one line on the mirror" from #477). I drafted this but the 403 blocked the write.

Until (1)+(2) or at least (2)+(3) land, a github-only-dev cold read still sees a Releases page ~230 versions stale.

Severity: major-friction (unchanged from #477). Related: #438, #454.

Follow-up to #477 (contract half landed in 3290adc). ## What #477 fixed The documented-vs-observed contradiction is resolved in-repo: AGENTS.md no longer claims `mirror-to-github.yml` mirrors refs, and the dangling references to the removed workflow / deleted `docs/github-mirror.md` were scrubbed from release.yml, pyproject.toml, and the GitHub issue config. ## What could NOT be done from a container, and why The observable half of #477's done-condition (mirror shows zero-stale-or-matching releases, plus a pointer on the mirror) is **not** met, and cannot be met by any warded container: - The GitHub mirror's `main` HEAD is stuck at `4c8e694` (2026-07-01 11:18), tags at v0.5.8 (36 total), releases at v0.5.8 (all `github-actions[bot]`-authored). Not just the releases page - the whole mirror is frozen, because the only thing that pushed it (`mirror-to-github.yml`) went PAT-less ~July 1 and was then removed entirely (b55f69f). - A container has no write path to the mirror: no `gh`, no `GITHUB_TOKEN` in env (only `FORGEJO_TOKEN`), the read MCP surface has no delete-release tool, and `create_or_update_file` returns 403 (integration is read-only for this repo). This is the same human-credential wall that blocked the three prior #477 attempts. ## Human action needed (pick one) 1. **Restore a live ref sync** - either provision `GITHUB_MIRROR_PAT` (push + repo/release scope) in ward -> Settings -> Actions -> Secrets and reinstate a minimal ref-push, or configure a **native Forgejo push mirror** (repo Settings -> Mirror) so main + tags stay current without an Actions secret. 2. **One-time scrub** the stranded `github-actions[bot]` v0.5.x release objects (v0.4.0 -> v0.5.8) so the Releases page stops reading "latest v0.5.8". Deleting a release does not delete its tag. 3. **Add a mirror-README banner** pointing at the canonical Forgejo release page (the "one line on the mirror" from #477). I drafted this but the 403 blocked the write. Until (1)+(2) or at least (2)+(3) land, a `github-only-dev` cold read still sees a Releases page ~230 versions stale. Severity: major-friction (unchanged from #477). Related: #438, #454.

coilyco-ops referenced this issue

2026-07-07 22:49:46 +00:00

GitHub mirror's releases/tags are frozen at v0.5.8 (36 tags) while canonical is v0.242.0, contradicting the documented mirror-main+tags contract #477

coilyco-ops referenced this issue

2026-07-08 03:33:07 +00:00

Config-driven ward: channels become download-and-verify of one prebuilt artifact (#650-5) #657

coilyco-ops referenced this issue

2026-07-08 03:33:46 +00:00

[epic] Config-driven ward: one precompiled binary, personal config resolved live from a git ref (supersedes the build-variant matrix) #650

coilyco-ops referenced this issue

2026-07-08 04:49:15 +00:00

[epic] Config-driven ward: one precompiled binary, personal config resolved live from a git ref (supersedes the build-variant matrix) #650