T8's turndown sweep (tools/beads/import_github.py) posted 'tracking moved: <bd-id> <url>' comments on every closed GitHub issue using _DASHBOARD_BASE = http://159.89.200.95:8765 — a base that is now dead from outside (DO cloud firewall blocks :8765; the dashboard is at https://nfold.dev, see tools/web_frontend/README.md 'Where the live dashboard is served'). The constant itself was fixed for future runs in the nfold.dev-awareness PR; this task is the one-off scripted pass over the ~272 already-posted comments (gh api PATCH per comment, matching the 'tracking moved:' marker) rewriting the base to https://nfold.dev/issue/<bd-id>;. Purely mechanical; the archive keeps working as a set of pointers into the live tracker.
None.
PR #1207 open: https://github.com/cfsh/ninefold/pull/1207 — https://nfold.dev/issue/nf-nqek
Ran live: all 272 stale "tracking moved:" comments rewritten to the https://nfold.dev base. Re-verified idempotent (a second dry-run against GitHub reports no stale links left).
reviewer: PASS at a9d25f7. Blocked on human approval — the PR touches tools/nflib/fakes.py, tools/nflib/gh.py, tools/nflib/gh_test.py, all outside the auto-merge perimeter (governance). approval:human label set, aedanpope requested as reviewer.
Heads-up from nf-abda (session bork), because it changes what this pass
should rewrite *to*.
nf-abda collapses the dashboard-URL definition into one place
(nflib.bdlink.dashboard_url), shared by dev.py pr's new **Beads:** line
and the MessageDisplay linkify hook — and in doing so changes
import_github._dashboard_url from /issue/<id> to the bare short link:
https://nfold.dev/nf-abc (not .../issue/nf-abc)
Why the shape changed, not just the host: /issue/<epic-id> renders an error
page — the single-issue view has no body for an epic — and the turndown sweep
does not know which kind of twin it is holding. The short-link route (#1198)
302s /nf-abc to /issue/nf-abc or /board/nf-abc, so the server
decides. Verified live 2026-08-21: /nf-758.9 -> 302 /issue/nf-758.9;
/nf-758 -> 302 /board/nf-758.
So this issue's one-off pass over the ~272 already-posted comments has a
choice worth making deliberately: rewriting
http://159.89.200.95:8765/issue/<id> to https://nfold.dev/<id> fixes the
dead host and the epic case in the same PATCH, and leaves every
tracking moved: comment matching what the code now emits. Rewriting only
the base leaves ~272 comments in a shape the tool no longer produces, and
any of them pointing at an epic still lands on an error page.
Both forms resolve, so nothing is broken either way — this is only about which one the archive ends up holding. Your call; no action needed on nf-abda.
CLAIM