feat(miner): SqliteDriver store seam + migrate run-state (Advances #7175)

[RealDiligent]

Summary

• Introduces packages/loopover-miner/lib/store-db-adapter.js (mirrors ORB src/selfhost/d1-adapter.ts: SqliteDriver, nodeSqliteDriver, createD1Adapter).
• Adds openLocalStoreAdapter beside openLocalStoreDb.
• Migrates run-state CRUD onto driver.query while keeping the sync public API and node:sqlite self-host default.

Advances #7175 (part 1 of N) — does not close the issue. Remaining: other ~12 stores, async D1 call sites, createPgAdapter / Postgres, interactive batchClaim/runOn, lease-expiry-by-time.

Test plan

• npx vitest run test/unit/miner-store-db-adapter.test.ts
• npx vitest run test/unit/miner-run-state.test.ts (functional cases)
• CI green

[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 93.77%. Comparing base (e2ea2d2) to head (204077e).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7192   +/-   ##
=======================================
  Coverage   93.77%   93.77%           
=======================================
  Files         694      695    +1     
  Lines       68975    69014   +39     
  Branches    18799    18799           
=======================================
+ Hits        64679    64718   +39     
  Misses       3302     3302           
  Partials      994      994           

Flag	Coverage Δ
shard-1	43.47% <80.43%> (-0.41%)	⬇️
shard-2	37.13% <39.13%> (-0.01%)	⬇️
shard-3	33.12% <39.13%> (+0.02%)	⬆️
shard-4	32.92% <0.00%> (-1.63%)	⬇️
shard-5	32.87% <43.47%> (+0.66%)	⬆️
shard-6	46.12% <43.47%> (+0.30%)	⬆️

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

Files with missing lines	Coverage Δ
packages/loopover-miner/lib/local-store.js	100.00% <100.00%> (ø)
packages/loopover-miner/lib/run-state.js	100.00% <100.00%> (ø)
packages/loopover-miner/lib/store-db-adapter.js	100.00% <100.00%> (ø)

[loopover-orb]

Caution

🛑 LoopOver review result - reject/close recommended

_{Review updated: 2026-07-18 09:52:26 UTC}

6 files · 1 AI reviewer · 2 blockers · CI green · clean

🛑 Suggested Action - Reject/Close

Review summary
Adds a small SqliteDriver/D1 adapter seam mirroring ORB's d1-adapter.ts, and migrates run-state.js's CRUD onto `driver.query` while keeping the DatabaseSync open for schema migrations/purge and the public API synchronous. The read/write dispatch in `nodeSqliteDriver.query` (columns().length > 0 => read) is correct for every statement actually migrated in this PR (plain INSERT/SELECT, no RETURNING), and the new test file exercises prepare/bind/all/first/raw/batch-rollback plus the openLocalStoreAdapter wiring against a real temp file. This is a clean, narrowly-scoped part 1 of #7175 with real tests behind the new surface.

Nits — 5 non-blocking

• packages/loopover-miner/lib/store-db-adapter.js:83-95 — `nodeSqliteDriver.query`'s read/write heuristic (`columns().length > 0` => read) will silently misclassify any future `INSERT/UPDATE/DELETE ... RETURNING` statement as a read (changes/lastInsertRowid dropped) — claim-ledger.js already relies on RETURNING for release/expire, so flag this loudly (e.g. a doc comment or a follow-up TODO) before that store migrates onto this same driver.
• packages/loopover-miner/lib/run-state.js — `driver.query` re-prepares the SQL string via `db.prepare(sql)` on every call instead of caching prepared statements once as the old code did (`getStatement`/`setStatement`); worth confirming this reparse cost is negligible at run-state's call volume before it becomes the pattern other stores copy.
• External nesting-depth flag on store-db-adapter.js:107 (depth 6) — `createD1Adapter`'s `batch()` try/catch/inner-try/catch is a bit deep; consider extracting the rollback into a small helper for readability.
• packages/loopover-miner/lib/store-db-adapter.js — `exec()`'s returned `count` (`(sql.match(/;/g) ?? []).length || 1`) is a rough heuristic that undercounts trailing-semicolon-less multi-statement scripts; fine since nothing reads this field yet, but worth a comment noting it's a stub.
• Add a one-line comment on `nodeSqliteDriver.query` calling out the RETURNING caveat so the next store migration (claim-ledger.js) doesn't hit it silently.

Why this is blocked

• No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.
• Maintainer requires a linked issue — Link the relevant issue (for example Closes #123) before opening the PR.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

2. Maintainer requires a linked issue — Link the relevant issue (for example `Closes #123`) before opening the PR.

Decision drivers

• ❌ Code review — 2 blockers (1 reviewer)
• ❌ Gate result — Blocking (Repo-configured hard blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
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 (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 407 registered-repo PR(s), 209 merged, 35 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	RealDiligent; Gittensor profile; 407 PR(s), 35 issue(s).
Improvement	✅ Minor	risk: clean · value: minor · LLM: moderate

Review context

• Author: RealDiligent
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 407 PR(s), 35 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Start here: Explain no-issue PR.
• Then work through the remaining 1 step 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 is closing this pull request on the maintainer's behalf (No linked issue detected; Maintainer requires a linked issue). This is an automated maintenance action — to pursue this change, please open a new pull request with the issues resolved. Closed PRs may be analyzed later to improve review accuracy, but they are not automatically reopened or re-reviewed.