fix(review): correct predicted_gate_calls migration ref to 0137

[bitfathers94]

fix(review): correct predicted_gate_calls migration ref to 0137

Both predicted-gate-calls.ts and predicted-gate-agreement.ts carried a
comment pointing the predicted_gate_calls table at migrations/0132, which
actually creates the unrelated impact_map_query_cache table. The table is
created by migrations/0137_predicted_gate_calls.sql, so a reader tracing
the table's migration history was misdirected to the wrong file.

Closes #8675

[superagent-security]

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.58%. Comparing base (b6c9f3b) to head (ff859dc).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8695      +/-   ##
==========================================
+ Coverage   90.56%   90.58%   +0.02%     
==========================================
  Files          96       98       +2     
  Lines       22490    22548      +58     
  Branches     3884     3901      +17     
==========================================
+ Hits        20367    20425      +58     
  Misses       1945     1945              
  Partials      178      178              

Flag	Coverage Δ
backend	100.00% <ø> (?)

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

Files with missing lines	Coverage Δ
src/review/predicted-gate-agreement.ts	100.00% <ø> (ø)
src/review/predicted-gate-calls.ts	100.00% <ø> (ø)

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-25 23:51:24 UTC}

2 files · 1 AI reviewer · no blockers · readiness 93/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This PR fixes a stale comment in predicted-gate-calls.ts that incorrectly attributed the predicted_gate_calls table to migrations/0132 (which actually creates impact_map_query_cache) instead of the correct migrations/0137_predicted_gate_calls.sql. Cross-checking the full file content confirms migrations/0137 does indeed create this exact table, so the fix is accurate. The predicted-gate-agreement.ts file shown as '0 changes' already correctly references migrations/0137 in its own header comment, so no edit was needed there despite being listed as modified.

Nits — 3 non-blocking

• The PR description says predicted-gate-agreement.ts also carried the wrong migration reference, but the diff shows 0 changes for that file and its current content already correctly cites migrations/0137 — worth confirming the description wasn't overstating the fix's scope.
• No code action needed; this is purely a comment-accuracy fix and the reference is now correct per migrations/0137_predicted_gate_calls.sql.
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.

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	#8675
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (1 linked issue).
Validation posture	⚠️ 20/25	Preflight is ready, but the PR body does not name the validation run.
Contributor workload	✅ 10/10	Author activity: 40 registered-repo PR(s), 25 merged, 0 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	bitfathers94; Gittensor profile; 40 PR(s), 0 issue(s).
Improvement	ℹ️ None detected	risk: low · value: none · LLM: minor

Linked issue satisfaction

Partially addressed
The predicted-gate-calls.ts fix is clearly shown in the diff and correctly changes 0132 to 0137, but the predicted-gate-agreement.ts change has no visible patch content, so it cannot be confirmed that the second required file was actually fixed.

Review context

• Author: bitfathers94
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: TypeScript
• Official Gittensor activity: 40 PR(s), 0 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Start here: Add validation command/output.

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.