fix(miner)!: full-cutover rename gittensory-miner config dir + Prometheus metric names

[JSONbored]

Summary

Phase 1 (#5707) renamed GITTENSORY_MINER_*/GITTENSORY_* env vars but missed two things the env var still fell back to when unset:

• The default local-store config directory (~/.config/gittensory-miner) via local-store.js's shared resolveLocalStoreDbPath() helper, used by governor-state/ledger/plan/prediction/portfolio-queue/run-state/claim-ledger/event-ledger/ranked-candidates stores, laptop-init, status, repo-clone, and worktree-allocator — now ~/.config/loopover-miner.
• 8 Prometheus textfile-exporter metric names (gittensory_miner_events_total, gittensory_miner_portfolio_queue_{items,oldest_in_progress_lease_age_seconds}, gittensory_miner_governor_{rate_limit_remaining_ratio,cap_usage_ratio}, gittensory_miner_prediction{s,_correct,_incorrect}_total) and their matching prometheus/rules/alerts.yml expressions — left unrenamed, the alert rules would silently query metric names that no longer exist.

Also renames the miner-ui's own local dev-server auth cookie (gittensory_miner_ui_token -> loopover_miner_ui_token, apps/gittensory-miner-ui) — a localhost-only dev cookie, not the core product's production session cookie (tracked separately).

Found and fixed a related pre-existing test bug along the way: alerts-miner-*.test.ts's "never references any loopover_* server metric" guard used a bare /loopover_/ regex, which broke once miner metrics themselves gained the loopover_ prefix — narrowed to /loopover_(?!miner_)/ so it still correctly flags a miner rule accidentally referencing a server metric.

BREAKING CHANGE: the miner's default config directory and every gittensory_miner_* Prometheus metric name changed; no dual-read/alias, per the epic's full-cutover mandate (#5705). A self-hoster's existing ~/.config/gittensory-miner state does not migrate automatically.

Explicitly NOT touched (separate, larger, higher-risk scopes — flagged for follow-up):

• packages/gittensory-miner/bin/gittensory-miner-mcp.js's gittensory_miner_* MCP tool names and packages/gittensory-mcp's own tool names (Phase 4: MCP server + 96 tool names, external-client breaking change).
• The .gittensory-miner.yml per-repo config filename and its ~30 references across the miner's goal-spec/config-precedence system (new gap discovered while investigating this fix; needs its own dedicated pass, mirroring the .gittensory.yml -> .loopover.yml rename already done for the core product).
• packages/gittensory-miner/ as a directory/package name, and the gittensory-miner CLI binary name (Phase 3/5).

Test plan

• npx vitest run test/unit/miner-*.test.ts test/unit/alerts-miner-*.test.ts apps/gittensory-miner-ui/src/auth.test.ts — 152 files / 1883 tests pass
• npm run typecheck clean
• npm run miner:env-reference:check / npm run docs:drift-check clean
• Confirmed every remaining gittensory-miner/gittensory_miner_ reference is legitimately out of scope (MCP tool names, CLI usage strings, packages/gittensory-miner/ directory path, .gittensory-miner.yml filename)

[superagent-security]

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

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	loopover-ui	913e620	Commit Preview URL Branch Preview URL	Jul 14 2026, 07:49 AM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.06%. Comparing base (a6c8f1d) to head (3b05e44).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5721      +/-   ##
==========================================
+ Coverage   95.05%   95.06%   +0.01%     
==========================================
  Files         581      581              
  Lines       46164    46164              
  Branches    14810    14810              
==========================================
+ Hits        43880    43886       +6     
+ Misses       1523     1517       -6     
  Partials      761      761              

Flag	Coverage Δ
shard-1	43.97% <47.36%> (ø)
shard-2	35.72% <52.63%> (+0.01%)	⬆️
shard-3	32.28% <42.10%> (ø)
shard-4	33.02% <78.94%> (+<0.01%)	⬆️
shard-5	31.59% <52.63%> (ø)
shard-6	44.47% <78.94%> (ø)

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

Files with missing lines	Coverage Δ
.../gittensory-engine/src/miner-prediction-metrics.ts	100.00% <100.00%> (ø)
...ckages/gittensory-miner/lib/deny-hook-synthesis.js	96.61% <100.00%> (+10.16%)	⬆️
packages/gittensory-miner/lib/event-ledger-cli.js	98.27% <100.00%> (ø)
packages/gittensory-miner/lib/governor-ledger.js	98.36% <100.00%> (ø)
...kages/gittensory-miner/lib/governor-metrics-cli.js	100.00% <100.00%> (ø)
packages/gittensory-miner/lib/laptop-init.js	98.26% <100.00%> (ø)
packages/gittensory-miner/lib/local-store.js	100.00% <100.00%> (ø)
packages/gittensory-miner/lib/orb-export.js	98.47% <100.00%> (ø)
packages/gittensory-miner/lib/plan-store.js	92.45% <100.00%> (ø)
...ckages/gittensory-miner/lib/portfolio-queue-cli.js	94.50% <100.00%> (ø)
... and 4 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]

Important

🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪

🔍 LoopOver is reviewing…

AI analysis is in progress. This comment will update when the review is complete.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed · 🟪 Reviewing}