Context
Three self-host/ops-adjacent docs still reference names from before the gittensory → loopover rename
that no longer exist, each verified against the real current file/name:
-
apps/loopover-ui/src/routes/docs.self-hosting-operations.tsx line 411 — the disk-cleanup section
says: "The loopover-docker-safe-prune systemd timer (below)...". No unit named loopover-docker-safe-prune
exists anywhere in the repo. The real timer, installed a few lines later in the same file's own
install snippet (lines 491-495) and shipped at systemd/loopover-docker-prune.timer.example, is
loopover-docker-prune (no -safe-). This is a self-inconsistent doc: it names one timer and then
instructs the operator to install a differently-named one.
-
packages/loopover-miner/terraform/main.tf line 7 — the module's header comment tells an operator:
"After terraform apply: SSH in, drop your secrets into a .gittensory-miner.env...". The real env
file, confirmed via git ls-tree and used consistently by this same module's own README.md (which
correctly says ../.loopover-miner.env.example) and by DEPLOYMENT.md, is
packages/loopover-miner/.loopover-miner.env.example. Only this one inline comment in main.tf still
has the old name.
-
src/review/repo-agnostic-capability-audit.md line 8 — links to
[...](../../packages/gittensory-miner/docs/repo-agnostic-capability-audit.md). That directory was
renamed; the file now lives at packages/loopover-miner/docs/repo-agnostic-capability-audit.md (confirmed
via git ls-tree). The link is dead — following it 404s on GitHub.
All three are isolated, single-line, unambiguous rename-residue fixes with a verified correct replacement
already established elsewhere in the same file or a sibling file — no design judgment involved.
Requirements
- Fix each reference to point at the real, current name/path, exactly as it already appears correctly
elsewhere in the repo (cited above for each).
- Do not touch any other rename-in-progress references outside these three specific spots — this repo is
mid-rename and many gittensory-* strings are either historical (changelog entries, issue titles) or still
intentionally live (e.g. gittensory.aethereal.dev, the still-unrenamed hosted domain) and out of scope
here.
Deliverables
Test Coverage Requirements
apps/loopover-ui/src/routes/** is UI code outside src/**'s Codecov coverage.include; the terraform
comment and the markdown doc are also outside src/**. Codecov patch coverage does not gate this change
directly. Add a real Vitest test (grep-based, following the pattern of other config-drift tests like
test/unit/miner-docker-compose.test.ts) that reads all three files and asserts the stale strings are gone
and the correct replacements are present, so each fix has a real regression check.
Expected Outcome
An operator reading the self-hosting-operations doc, the miner Terraform module's own header comment, or the
repo-agnostic capability audit doc sees only real, currently-correct names — no dead links, no
self-contradictory timer names, no stale env-file names.
Links & Resources
Context
Three self-host/ops-adjacent docs still reference names from before the
gittensory→loopoverrenamethat no longer exist, each verified against the real current file/name:
apps/loopover-ui/src/routes/docs.self-hosting-operations.tsxline 411 — the disk-cleanup sectionsays: "The
loopover-docker-safe-prunesystemd timer (below)...". No unit namedloopover-docker-safe-pruneexists anywhere in the repo. The real timer, installed a few lines later in the same file's own
install snippet (lines 491-495) and shipped at
systemd/loopover-docker-prune.timer.example, isloopover-docker-prune(no-safe-). This is a self-inconsistent doc: it names one timer and theninstructs the operator to install a differently-named one.
packages/loopover-miner/terraform/main.tfline 7 — the module's header comment tells an operator:"After
terraform apply: SSH in, drop your secrets into a.gittensory-miner.env...". The real envfile, confirmed via
git ls-treeand used consistently by this same module's ownREADME.md(whichcorrectly says
../.loopover-miner.env.example) and byDEPLOYMENT.md, ispackages/loopover-miner/.loopover-miner.env.example. Only this one inline comment inmain.tfstillhas the old name.
src/review/repo-agnostic-capability-audit.mdline 8 — links to[...](../../packages/gittensory-miner/docs/repo-agnostic-capability-audit.md). That directory wasrenamed; the file now lives at
packages/loopover-miner/docs/repo-agnostic-capability-audit.md(confirmedvia
git ls-tree). The link is dead — following it 404s on GitHub.All three are isolated, single-line, unambiguous rename-residue fixes with a verified correct replacement
already established elsewhere in the same file or a sibling file — no design judgment involved.
Requirements
elsewhere in the repo (cited above for each).
mid-rename and many
gittensory-*strings are either historical (changelog entries, issue titles) or stillintentionally live (e.g.
gittensory.aethereal.dev, the still-unrenamed hosted domain) and out of scopehere.
Deliverables
apps/loopover-ui/src/routes/docs.self-hosting-operations.tsxline 411:loopover-docker-safe-prune→loopover-docker-prune.packages/loopover-miner/terraform/main.tfline 7:.gittensory-miner.env→.loopover-miner.env.example.src/review/repo-agnostic-capability-audit.mdline 8: fix the dead link to point atpackages/loopover-miner/docs/repo-agnostic-capability-audit.md.test/unit/) asserting none of these three exact stale strings(
loopover-docker-safe-prune,.gittensory-miner.envas a fallback/secrets-file reference, and the deadpackages/gittensory-miner/link path) appear in these three files anymore.Test Coverage Requirements
apps/loopover-ui/src/routes/**is UI code outsidesrc/**'s Codecovcoverage.include; the terraformcomment and the markdown doc are also outside
src/**. Codecov patch coverage does not gate this changedirectly. Add a real Vitest test (grep-based, following the pattern of other config-drift tests like
test/unit/miner-docker-compose.test.ts) that reads all three files and asserts the stale strings are goneand the correct replacements are present, so each fix has a real regression check.
Expected Outcome
An operator reading the self-hosting-operations doc, the miner Terraform module's own header comment, or the
repo-agnostic capability audit doc sees only real, currently-correct names — no dead links, no
self-contradictory timer names, no stale env-file names.
Links & Resources
systemd/loopover-docker-prune.service.example/systemd/loopover-docker-prune.timer.example— the realtimer files.
packages/loopover-miner/terraform/README.md— already correctly says.loopover-miner.env.example.packages/loopover-miner/docs/repo-agnostic-capability-audit.md— the real target of the dead link.broken cross-reference" class of bug, three different files not covered by those.