Skip to content

fix(docs): sweep remaining gittensory-* rename residue in self-host ops docs (dead timer name, dead link, stale env filename) #5937

Description

@JSONbored

Context

Three self-host/ops-adjacent docs still reference names from before the gittensoryloopover rename
that no longer exist, each verified against the real current file/name:

  1. 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.

  2. 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.

  3. 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

  • apps/loopover-ui/src/routes/docs.self-hosting-operations.tsx line 411: loopover-docker-safe-prune
    loopover-docker-prune.
  • packages/loopover-miner/terraform/main.tf line 7: .gittensory-miner.env
    .loopover-miner.env.example.
  • src/review/repo-agnostic-capability-audit.md line 8: fix the dead link to point at
    packages/loopover-miner/docs/repo-agnostic-capability-audit.md.
  • A regression test (e.g. under test/unit/) asserting none of these three exact stale strings
    (loopover-docker-safe-prune, .gittensory-miner.env as a fallback/secrets-file reference, and the dead
    packages/gittensory-miner/ link path) appear in these three files anymore.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:bugGittensor-scored bug fix — scores a 0.05x multiplier.help wantedExtra attention is needed

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions