feat(miner): add gate verdict calibration signal

[joaovictor91123]

Summary

• Adds a default-off config resolver for opt-in structured gate-verdict calibration sharing.
• Adds safe ingestion for structured per-dimension gate verdicts, including mid-flight opt-out rejection and public-safe dimension normalization.
• Adds weighted composite scoring with objective-anchor and pairwise calibration signals plus a deterministic Markdown audit report.
• Fixes feat(miner): opt-in cross-product calibration signal from the maintainer review stack #3015

Scope

• The PR title follows type(scope): short summary Conventional Commit format, for example fix(api): restore profile access checks.
• 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 an issue, or this is small enough that the summary explains why an issue is not needed.

Validation

• git diff --check HEAD~1..HEAD
• npm run actionlint
• npm run typecheck
• npm run test:coverage locally; codecov/patch requires >=99% coverage of the lines AND branches you changed (aim for 100% on your diff so CI variance does not fail near the threshold). Global coverage is a non-blocking trend with a loose 90% backstop, not the gate.
• 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:

• npm test --workspace @jsonbored/gittensory-engine passed after rebase: 124 tests.
• npm run build:miner passed after rebase.
• npm run db:migrations:check and npm run db:schema-drift:check passed before the final rebase; this PR has no DB or migration changes.
• npm run test:coverage is not rerun locally because the previous Windows runs in this workspace repeatedly timed out and ended with EPIPE after the session killed the output pipe, not with a reported assertion failure.
• UI checks were not run because this PR changes only the engine package and its package README.

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.
• API/OpenAPI/MCP behavior is updated and tested where needed.
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks.
• Visible UI changes include a UI Evidence section below with JPG/JPEG or PNG screenshots arranged as organized, captioned, clickable thumbnails. SVG screenshots are not used as review evidence. Review-only screenshots or recordings are not committed to the repository.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

UI Evidence

N/A - no visible UI, frontend, or extension change.

Notes

• The engine package owns the deterministic default-off opt-in, structured ingestion, score composition, and audit rendering logic. Live review-stack wiring can supply the currently resolved per-repo opt-in state.

[superagent-security]

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

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-04 17:35:32 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This adds a pure engine surface for opt-in structured gate-verdict calibration, including config resolution, ingestion normalization, composite scoring, audit Markdown rendering, barrel exports, tests, and README coverage. The visible implementation keeps the default-off behavior, rejects malformed ids/empty rows, renormalizes absent optional signals, and CI has already passed on this commit. I did not find a reachable correctness blocker in the provided changed files.

Nits — 5 non-blocking

• nit: packages/gittensory-engine/src/gate-verdict-calibration.ts:334 reports malformed top-level alias values as `miner.calibration...`, which is misleading when the bad value came from `calibration.shareStructuredGateVerdicts`; either include the resolved source path in the warning or use a path-neutral warning.
• nit: packages/gittensory-engine/src/gate-verdict-calibration.ts:412 accepts a prebuilt `GateVerdictCalibrationIngestion` with only a shallow `{ accepted: array, rejected: array }` check, so JS callers can bypass the repo/id/dimension normalization that `ingestGateVerdictCalibrationSignals()` enforces; document that this overload is trusted-only or validate the accepted rows before auditing.
• nit: packages/gittensory-engine/src/gate-verdict-calibration.ts:220 treats an `unknown` outcome as a valid zero-scoring dimension instead of dropping it as unavailable signal, which is defensible but worth making explicit in tests/docs because it changes the composite score rather than merely withholding signal.
• nit: packages/gittensory-engine/README.md:210 says the accepted dimensions include `correctness`, `tests`, `security`, `scope`, `freshness`, `ci`, and `policy`, but omits `maintainability` even though the engine accepts it; keep the public contract list complete.
• packages/gittensory-engine/src/gate-verdict-calibration.ts:329: track whether `optInRaw`/`weightRaw` came from `miner.calibration` or the top-level alias and emit that exact path in `warnings`, or change the text to `shareStructuredGateVerdicts must be...`.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#3015
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	❌ 5/25	Preflight is holding this PR: the review lane is unavailable, so it is not ready for automated review.
Contributor workload	✅ 10/10	Author activity: 96 registered-repo PR(s), 52 merged, 8 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	joaovictor91123; Gittensor profile; 96 PR(s), 8 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: joaovictor91123
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 96 PR(s), 8 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Await review-lane availability.
• Refresh registry data or choose a registered active repo.

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.

_{🟩 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 Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[loopover-orb]

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