Skip to content

fix(rebrand): full-cutover rename miner/AMS per-repo and operator config filenames - #5765

Merged
JSONbored merged 1 commit into
mainfrom
rebrand-phase8-miner-config
Jul 14, 2026
Merged

fix(rebrand): full-cutover rename miner/AMS per-repo and operator config filenames#5765
JSONbored merged 1 commit into
mainfrom
rebrand-phase8-miner-config

Conversation

@JSONbored

Copy link
Copy Markdown
Owner

Summary

  • Rebrand epic Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705, Phase 8a follow-up: renames the two remaining unrenamed config-file surfaces in the miner package — .gittensory-miner.yml/.json (per-target-repo miner goal spec, MINER_GOAL_SPEC_FILENAMES) and .gittensory-ams.yml/.json (operator-local AMS execution policy, AMS_POLICY_SPEC_FILENAMES) — to .loopover-miner.* / .loopover-ams.*.
  • Includes the .env sibling and all four checked-in .example files, .gitignore entries, and — the one genuinely functional gap — docker-compose.miner.yml's env_file: directive, which was still pointing at the old bare filename.
  • Fixes directly-adjacent stale prose in prometheus/rules/alerts.yml (a runbook CLI-command example and .gittensory-ams.yml path mentions) discovered while verifying.

Deliberately not touched (distinct, larger-blast-radius surfaces, left for a dedicated follow-up):

  • The Prometheus rule group names (gittensory-miner-prediction/-portfolio-queue/-governor) and the up{job="gittensory"} scrape-job label in the same file
  • The ~150+ gittensory-miner mentions in test describe()/tmpdir-prefix strings across the suite (cosmetic, non-functional)

Test plan

  • npm run typecheck clean
  • npx vitest run — 838 files / 16257 tests passed (2 pre-existing skips)
  • full npm run test:ci gate green end-to-end
  • npm run docs:drift-check / npm run manifest:drift-check clean

…fig filenames

Renames the two remaining unrenamed config-file surfaces in the miner
package: .gittensory-miner.yml/.json (per-target-repo miner goal spec,
MINER_GOAL_SPEC_FILENAMES) and .gittensory-ams.yml/.json (the
operator-local AMS execution policy, AMS_POLICY_SPEC_FILENAMES) become
.loopover-miner.* / .loopover-ams.*, along with their .env sibling and
all four checked-in .example files, .gitignore entries, and the
docker-compose.miner.yml env_file directive that actually loads one of
them at runtime.

Also fixes directly-adjacent stale prose in prometheus/rules/alerts.yml
(a runbook CLI-command example and .gittensory-ams.yml path mentions).

Deliberately not touched: the Prometheus rule *group* names
(gittensory-miner-prediction/-portfolio-queue/-governor) and the
up{job="gittensory"} scrape-job label in the same file, and the ~150+
"gittensory-miner" mentions in test describe()/tmpdir-prefix strings
across the suite -- distinct, larger-blast-radius surfaces than a
config-filename rename, left for a dedicated follow-up.
@superagent-security

Copy link
Copy Markdown
Contributor

Superagent didn't find any vulnerabilities or security issues in this PR.

@codecov

codecov Bot commented Jul 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.07%. Comparing base (210a8b1) to head (73aba24).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5765   +/-   ##
=======================================
  Coverage   95.07%   95.07%           
=======================================
  Files         582      582           
  Lines       46183    46183           
  Branches    14812    14812           
=======================================
  Hits        43907    43907           
  Misses       1516     1516           
  Partials      760      760           
Flag Coverage Δ
shard-1 43.95% <50.00%> (ø)
shard-2 35.74% <100.00%> (ø)
shard-3 32.26% <50.00%> (ø)
shard-4 32.94% <100.00%> (ø)
shard-5 31.74% <100.00%> (ø)
shard-6 44.66% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
packages/loopover-engine/src/ams-policy-spec.ts 100.00% <100.00%> (ø)
packages/loopover-engine/src/fleet-run-manifest.ts 100.00% <ø> (ø)
packages/loopover-engine/src/focus-manifest.ts 99.10% <ø> (ø)
...ckages/loopover-engine/src/governor/action-mode.ts 90.00% <ø> (ø)
...ckages/loopover-engine/src/governor/kill-switch.ts 100.00% <ø> (ø)
...oopover-engine/src/governor/reputation-throttle.ts 100.00% <ø> (ø)
packages/loopover-engine/src/miner-goal-spec.ts 100.00% <ø> (ø)
...ckages/loopover-engine/src/miner/iterate-policy.ts 12.50% <ø> (ø)
...ges/loopover-engine/src/phase7-calibration-loop.ts 44.38% <ø> (ø)
packages/loopover-miner/lib/ams-policy.js 93.33% <100.00%> (ø)
... and 9 more
🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@loopover-orb loopover-orb Bot added the gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier. label Jul 14, 2026
@JSONbored
JSONbored merged commit c93569d into main Jul 14, 2026
18 checks passed
@JSONbored
JSONbored deleted the rebrand-phase8-miner-config branch July 14, 2026 13:05
This was referenced Jul 14, 2026
This was referenced Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant