Skip to content

fix(miner): register ranked-candidates + deny-hook-synthesis in doctor/migrate store lists - #8036

Merged
loopover-orb[bot] merged 1 commit into
JSONbored:mainfrom
lourincedaging0-commits:fix/doctor-migrate-missing-stores-8008
Jul 22, 2026
Merged

fix(miner): register ranked-candidates + deny-hook-synthesis in doctor/migrate store lists#8036
loopover-orb[bot] merged 1 commit into
JSONbored:mainfrom
lourincedaging0-commits:fix/doctor-migrate-missing-stores-8008

Conversation

@lourincedaging0-commits

Copy link
Copy Markdown
Contributor

Closes #8008

What

status.ts's storeIntegrityChecks and migrate-cli.ts's STORES both enumerate every durable local SQLite store, so loopover-miner doctor reports each store's integrity and loopover-miner migrate applies pending migrations to each. Two stores were missing from both lists — ranked-candidates and deny-hook-synthesis — so doctor never checked them and migrate never migrated them, unlike every sibling store (the same class of gap #6768 fixed for four other stores).

  • Added both to storeIntegrityChecks (via resolveRankedCandidatesDbPath / resolveDenyHookSynthesisDbPath) and to STORES (with initRankedCandidatesStore / initDenyHookSynthesisStore), in the same shape/order as existing entries.
  • Updated the pinned store-list tests (count 14→16, expected names) and added a #8008 regression assertion mirroring the existing #6768 one.

Verification

Miner-lib lane, verified locally: miner-status + miner-migrate-cli suites pass (49 tests) with doctor reporting and migrate covering both new stores; both source and test files typecheck clean against the project's exact CI types. .js are gitignored (rebuilt in CI).

…r/migrate store lists

status.ts's storeIntegrityChecks and migrate-cli.ts's STORES both enumerate every durable
local SQLite store so `loopover-miner doctor` reports each store's integrity and
`loopover-miner migrate` applies pending migrations to each. Two stores were missing from
both lists: ranked-candidates and deny-hook-synthesis -- so doctor never checked them and
migrate never migrated them, unlike every sibling store.

Add both to storeIntegrityChecks (via resolveRankedCandidatesDbPath /
resolveDenyHookSynthesisDbPath) and to STORES (with their initRankedCandidatesStore /
initDenyHookSynthesisStore openers), and update the pinned store-list tests (count and
expected names) plus a JSONbored#8008 regression assertion mirroring the existing JSONbored#6768 one.

Closes JSONbored#8008
@superagent-security

Copy link
Copy Markdown
Contributor

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

@loopover-orb loopover-orb Bot added the gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier. label Jul 22, 2026
@loopover-orb

loopover-orb Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Tip

✅ LoopOver review result - approve/merge recommended

Review updated: 2026-07-22 14:34:55 UTC

4 files · 1 AI reviewer · no blockers · readiness 98/100 · CI green · clean

✅ Suggested Action - Approve/Merge

  • safe to merge

Review summary
This PR adds `ranked-candidates` and `deny-hook-synthesis` to both `status.ts`'s `storeIntegrityChecks` and `migrate-cli.ts`'s `STORES` list, mirroring the exact shape/order of existing entries and following the same pattern PR #6768 used for four other stores. Tests are updated in lockstep (14→16 stores, pinned name lists, and new #8008 regression assertions matching the existing #6768 ones). The change is narrow, mechanical, and directly closes the linked issue #8008 with no scope creep — I traced both import additions to real exported symbols (`initRankedCandidatesStore`/`resolveRankedCandidatesDbPath` and `initDenyHookSynthesisStore`/`resolveDenyHookSynthesisDbPath`) used consistently with sibling entries in the full file content.

Nits — 3 non-blocking

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 #8008
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 ✅ 25/25 PR body includes validation/test evidence.
Contributor workload ✅ 10/10 Author activity: 81 registered-repo PR(s), 32 merged, 5 issue(s).
Contributor context ✅ Confirmed Gittensor contributor lourincedaging0-commits; Gittensor profile; 81 PR(s), 5 issue(s).
Improvement ✅ Minor risk: clean · value: minor · LLM: minor
Linked issue satisfaction

Addressed
The diff adds ranked-candidates and deny-hook-synthesis to both status.ts's storeIntegrityChecks and migrate-cli.ts's STORES using the same resolve*/init* pattern as existing entries, and updates the corresponding tests to assert both stores appear with a regression check.

Review context
  • Author: lourincedaging0-commits
  • Role context: outside_contributor
  • Public audience mode: oss maintainer
  • Lane context: Repository is configured for direct PR review.
  • Public profile languages: HTML
  • Official Gittensor activity: 81 PR(s), 5 issue(s).
  • PR-specific overlap: none found.
Contributor next steps
  • Keep the PR focused and include validation evidence before maintainer review.
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-orb Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@loopover-orb
loopover-orb Bot merged commit 37369b9 into JSONbored:main Jul 22, 2026
10 checks passed
JSONbored pushed a commit that referenced this pull request Jul 24, 2026
…) (#8470)

status.ts's storeIntegrityChecks and migrate-cli.ts's STORES are both meant to
enumerate every durable local SQLite store in the package -- each file's own
comment says to keep it in sync with the other. Both listed the same sixteen
stores, but orb-export.sqlite3 (the opt-in Orb telemetry export's per-instance
HMAC secret and export cursor, #4277/#5681) was never added when it shipped.

The effect: a corrupted orb-export.sqlite3 was invisible to
`loopover-miner doctor`'s per-store integrity sweep, and `loopover-miner
migrate` never brought it up to date, unlike every other store the package
ships. Same gap class already fixed for policy-doc-cache (#7238),
ranked-candidates + deny-hook-synthesis (#8008/#8036), and four earlier
omissions (#6768).

Adds the store to both lists using each list's existing entry shape
(no restructuring): ["orb-export", resolveOrbExportDbPath(env)] in status.ts
and { name, resolveDbPath, open } in migrate-cli.ts. Both resolver/opener
signatures already match the sibling entries, so no casts are needed.

Updates the two tests that pin the lists exactly -- the migrate test's
store-name array (now seventeen, same order) and the doctor test's
store-integrity check names -- and adds a #8318 regression assertion beside
the existing #6768/#8008 ones.
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.

doctor/migrate store lists (status.ts, migrate-cli.ts) are missing ranked-candidates.ts and deny-hook-synthesis.ts

1 participant