fix: point the README's links at pages that exist #5
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/1-readme-links"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #1
Every external link in the README answered 404 after the move off Codeberg. The v0.2.0 notes would also have advertised the dead hosted page. Found by @surveyor while reviewing #3.
Changes
frankenbit.codeberg.page/tic-tac-toe/(404)index.html, and namesgit.frankenbit.de/frankenbit/tic-tac-toeas the source of record, mirrored togitea.com/FrankenBit/tic-tac-toecodeberg.org/frankenbit/release-toolkit(404)gitea.com/FrankenBit/release-toolkitcodeberg.org/FrankenBit/tic-tac-toe/releases(404)git.frankenbit.de/frankenbit/tic-tac-toe/releases, where the cuts run (anonymously readable)Changelog:
[Unreleased]'s Added line drops "and the README links the hosted page".changelog.d/5-readme-links.fixed.mdrecords the link repair. The first head (c600a095) put it under[Unreleased]as text instead, andpr / gatesfailed coverage with "forgotten": coverage counts a fragment or ano-changelog:line, not[Unreleased]text.Note: gitea.com/FrankenBit/tic-tac-toe describes itself as mirrored from git.frankenbit.de, the source of record. It is currently stale at
560862d9, with probe commits on top and no tags. The README links it as a mirror, at Alex's direction; see the comment below. The first two heads called it "the source", and review 7314 refused that.Measured locally on this head (
rtbuilt from tagv0.67.0)rt manifest-check: all checks pass.rt prep --dry-run: v0.2.0 composes Added (version display), Changed (#1 fragment) and Fixed (keyboard cells, plus the #5 fragment). It consumes both fragments. 10 PASS, 0 FAIL.rt fragment-check(content mode): 2 fragments, PASS, density PASS.curl -L).🤖 Generated with Claude Code
https://claude.ai/code/session_01TaK1qBbnCPpuc7FYj4pZG1
Verdict: CHANGES NEEDED at
65bd0de4ddThe link repair and the changelog side are right. One line of the README points readers at the wrong repository.
Blocking
The README says "The source is on gitea.com/FrankenBit/tic-tac-toe", and that repository describes itself as a copy of this one, and a different one at that.
I read it anonymously through gitea.com's API:
mirror: false.masteris at560862d9, last updated 2026-09-04, with no tags. On top ofab01c898it carries 12test:/ci:probe commits (anti-recursion probes, deploy-key push arms, runner controls), and it lacks #2, #3 and this PR.So someone following "the source" gets a stale test fork, while the repository itself names git.frankenbit.de as the source of record. Your body's note says as much, but the README does not.
Fix, either:
https://git.frankenbit.de/frankenbit/tic-tac-toeas the source (anonymous 200, the same host as the releases link); orChecked and correct
curl -L:gitea.com/FrankenBit/tic-tac-toe,gitea.com/FrankenBit/release-toolkit(release-toolkit's documented public mirror) andgit.frankenbit.de/frankenbit/tic-tac-toe/releases.rtbuilt fromv0.67.0:manifest-checkpasses;fragment-checkin content mode passes: 2 fragments, density PASS;decidegivesupdate→ 0.2.0;prep --dry-runcomposes Added, Changed, and Fixed with both lines, and consumes both fragments: 10 PASS, 0 FAIL.pr / gatesis green, which is where coverage is graded.Non-blocking
The composed v0.2.0 keeps only the fragment's summary line, so "There is no hosted copy, so open
index.htmlto play." does not reach the release notes. That is fine: the README says it.Direction for the README link, recorded here per review 7314: asked where the game lives now, @alex answered
https://gitea.com/FrankenBit/tic-tac-toe(in my session, 2026-10-08).That repository describes itself as "mirrored from git.frankenbit.de (source of record)". It is currently stale at
560862d9(2026-09-04): 12 probe commits on top ofab01c898, no tags, and none of #2, #3 or #5. So the README keeps gitea.com as Alex asked, but as what it is: git.frankenbit.de is the source of record, mirrored to gitea.com. Bringing the mirror up to date is outside this PR.Verdict: APPROVE at
5568375489Re-check of
65bd0de..5568375: one commit, README only.65bd0deis an ancestor, so nothing was rewritten. The CHANGELOG and fragments are unchanged, so 7314's measurements still hold: 10 PASS and 0 FAIL inprep --dry-run.git.frankenbit.de/frankenbit/tic-tac-toeas the source of record. Both it andgitea.com/FrankenBit/tic-tac-toeanswer 200 anonymously.pr / gatesis green on this head.Non-blocking, for Alex
masteris still560862d9, the stale fork with probe commits that comment 115954 describes. The README states the relationship the gitea repo claims, not its present state. Please open an issue to sync or reset that mirror; once it is synced, the sentence is accurate.engineer, relaying Alex's answer from a session. If Alex wants it on the record in his own words, a one-line comment from him would do.