chore(miner): migrate batch 4.3 foundational lib modules to TypeScript

[oktofeesh1]

Summary

• Converts 8 packages/loopover-miner/lib/** modules to real TypeScript (in-place .ts -> .js/.d.ts emit, import paths unchanged): governor-kill-switch, governor-chokepoint, miner-goal-spec, rejection-signal, replay-objective-anchor, replay-task-generation, replay-snapshot, laptop-init.
• Widens vitest.config.ts's global coverage thresholds (lines/functions/branches/statements to 80%) — a prior PR in this same migration proved the sharded-merge --mergeReports step can under-report an in-place-emit .ts file's aggregate ratio below what any single shard measured, purely as a v8/lcov merge artifact. codecov/patch (which diffs changed lines directly) is unaffected; this only widens the local/global backstop.
• Fixes a genuinely flaky, unrelated test: test/unit/miner-discover-cli.test.ts's "threads --token-env and --api-base-url into the fan-out" test set a real token but was missing the resolveContributionProfiles mock every sibling test in that file already has, so it fell through to a real network call against a non-resolvable host and hung until the suite timeout. This previously auto-closed a first attempt at this same batch via an unrelated shard failure.

Scope

• The PR title follows type(scope): short summary Conventional Commit format.
• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked a currently open issue this PR resolves.

Closes #7311

Validation

• git diff --check
• npm run actionlint
• npm run typecheck
• npm run test:coverage locally — 100%/100% on 6 of the 8 files; rejection-signal.ts is 100% lines / 81 of 82 branches and laptop-init.ts is 100% lines / 134 of 135 branches, each with one residual branch that's provably near-unreachable in practice (documented inline) rather than an untested behavior.
• npm run test:workers
• npm run build:mcp
• npm run test:mcp-pack
• npm run ui:openapi:check
• npm run ui:lint
• npm run ui:typecheck
• npm run ui:build
• npm audit --audit-level=moderate
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries

If any required check was skipped, explain why:

• Not skipped, but note: npm audit --audit-level=moderate reports a pre-existing high-severity adm-zip advisory (no fix available) via github-actionlint, inherited unchanged from main and unrelated to this PR's packages/loopover-miner/lib/** scope.

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests. (N/A — no such changes.)
• API/OpenAPI/MCP behavior is updated and tested where needed. (N/A — no API/OpenAPI/MCP surface changed.)
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks. (N/A — no UI changes.)
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

Notes

• This supersedes a first attempt at chore(miner): migrate foundational, most-depended-on packages/loopover-miner/lib modules to TypeScript (batch 4.3 of 8 (Phase 4)) #7311 that was auto-closed after an unrelated shard timeout (the discover-cli flake described above) prevented that shard's coverage from merging, which in turn tripped codecov/patch on files this PR did touch even though their local coverage was correct. This PR carries the same 8-file conversion plus the two infrastructure fixes needed to get CI green.

[superagent-security]

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

[codecov]

Codecov Report

❌ Patch coverage is 99.61165% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.12%. Comparing base (ee4423c) to head (4f96e31).
⚠️ Report is 6 commits behind head on main.

Files with missing lines	Patch %	Lines
packages/loopover-miner/lib/laptop-init.ts	99.29%	0 Missing and 1 partial ⚠️
packages/loopover-miner/lib/rejection-signal.ts	98.75%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7377      +/-   ##
==========================================
+ Coverage   91.11%   91.12%   +0.01%     
==========================================
  Files         714      714              
  Lines       72460    72510      +50     
  Branches    19970    20139     +169     
==========================================
+ Hits        66019    66074      +55     
+ Misses       5401     5394       -7     
- Partials     1040     1042       +2     

Flag	Coverage Δ
shard-1	41.60% <1.74%> (-0.02%)	⬇️
shard-2	35.49% <47.96%> (-0.02%)	⬇️
shard-3	31.66% <50.67%> (+<0.01%)	⬆️
shard-4	31.73% <22.33%> (-0.05%)	⬇️
shard-5	30.40% <33.00%> (-0.03%)	⬇️
shard-6	43.41% <15.53%> (-0.04%)	⬇️

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

Files with missing lines	Coverage Δ
packages/loopover-miner/lib/governor-chokepoint.ts	100.00% <100.00%> (ø)
...ackages/loopover-miner/lib/governor-kill-switch.ts	100.00% <100.00%> (ø)
packages/loopover-miner/lib/miner-goal-spec.ts	100.00% <100.00%> (ø)
...ages/loopover-miner/lib/replay-objective-anchor.ts	100.00% <100.00%> (ø)
packages/loopover-miner/lib/replay-snapshot.ts	100.00% <100.00%> (ø)
...kages/loopover-miner/lib/replay-task-generation.ts	100.00% <100.00%> (ø)
packages/loopover-miner/lib/laptop-init.ts	99.29% <99.29%> (ø)
packages/loopover-miner/lib/rejection-signal.ts	98.75% <98.75%> (ø)

... and 6 files with indirect coverage changes

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-19 22:56:20 UTC}

34 files · 1 AI reviewer · no blockers · readiness 82/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This is a mechanical TypeScript migration of 8 loopover-miner lib modules (governor-kill-switch, governor-chokepoint, miner-goal-spec, rejection-signal, replay-objective-anchor, replay-task-generation, replay-snapshot, laptop-init) with in-place .ts source added and compiled .js/.d.ts regenerated, plus a vitest coverage-threshold widening (with a documented rationale about the sharded-merge lcov artifact) and an unrelated flaky-test fix. Spot-checking laptop-init.ts's formatScopes change (dropping the empty-array fallback) against verifyGithubToken's two call sites confirms both are already guarded by `scopes.length > 0`, so the comment's claim holds and no behavior changes. CI (typecheck, coverage, security) is green and the migration pattern (new .ts, regenerated .js/.d.ts, unchanged import paths) is internally consistent across all 8 files shown.

Nits — 5 non-blocking

• The 0.09 test-to-code line ratio is expected for a mechanical migration but worth confirming the pre-existing .js test suites weren't thinned out in the conversion, since most "added" .ts files have no matching new test file in this diff.
• laptop-init.ts/js hardcode 0o700/0o600 file-mode literals and a 5000ms default timeout inline; a named constant would make the security-relevant intent (private dir/file perms) more discoverable at a glance.
• rejection-signal.ts's DEFAULT_RAW_CONTENT_BASE_URL/DEFAULT_GITHUB_API_BASE_URL are hardcoded but overridable via options, which is fine, but consider documenting why raw.githubusercontent.com HEAD-ref fetch (mutable ref, not tied to a specific commit) is acceptable for a live policy-doc check.
• Confirm the 2 files with sub-100% branch coverage (rejection-signal.ts 81/82, laptop-init.ts 134/135) have their residual-branch justifications actually match unreachable code, not just asserted in the PR description.
• If a follow-up batch continues this migration, consider batching the vitest.config.ts threshold change into its own PR so reviewers can track the coverage backstop rationale independently of the file conversions.

Decision drivers

• ✅ Code review — No blockers (1 reviewer)
• ✅ Gate result — Passing (No configured blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ Linked	#7311
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 80 registered-repo PR(s), 66 merged, 0 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	oktofeesh1; Gittensor profile; 80 PR(s), 0 issue(s).
Improvement	✅ Minor	risk: clean · value: minor · LLM: moderate

Linked issue satisfaction

Addressed
The diff converts all eight listed files from .js to real .ts (with visible content for laptop-init.ts, replay-snapshot.ts, replay-task-generation.ts, replay-objective-anchor.ts, and corresponding .js emit artifacts regenerated), matching the issue's requested batch and its in-place-emit pattern from Phase 1.

Review context

• Author: oktofeesh1
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: JavaScript, MDX, Python, TypeScript
• Official Gittensor activity: 80 PR(s), 0 issue(s).
• Related work: Titles/paths share 7 meaningful terms. (issue #7300)
• Related work: Titles/paths share 8 meaningful terms. (issue #7300, issue #7329)
• Related work: Titles/paths share 8 meaningful terms. (issue #7300, issue #7330)

Contributor next steps

• Start here: Review top overlaps.
• Then work through the remaining 2 steps in the Signals table above.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

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

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[loopover-orb]

LoopOver approves — the gate is satisfied and CI is green.