feat(github): authoritative .gittensory.yml gate config (config-as-code)

[JSONbored]

Phase B (foundation): config-as-code gate policy

Lets maintainers declare the Gittensory Gate's blocker policy in .gittensory.yml under gate:, layered over the dashboard repository settings — the CodeRabbit-style config-as-code model none of the in-flight gate PRs cover. Builds directly on the confirmed-contributor model from #644.

gate:
  duplicates: block            # block | advisory | off
  readiness:
    mode: advisory             # block | advisory | off
    minScore: 60
  # linkedIssue: advisory      # optional; falls back to the dashboard setting when unset

What it does

• Extends the existing repo focus-manifest loader (src/signals/focus-manifest.ts / -loader.ts) with a gate: section — linkedIssue, duplicates, readiness: { mode, minScore }, each off | advisory | block. Reuses the loader's fetch + 6h cache + graceful-fallback (a broken/missing manifest degrades to deterministic signals, never throws). Unset fields stay null.
• Precedence: .gittensory.yml > DB RepositorySettings > safe defaults, resolved in gateCheckPolicy (src/queue/processors.ts). The manifest is loaded only on the enabled-gate path (cached), so the ~all gate-off repos pay no fetch cost.
• Single evaluation path preserved. It only chooses which deterministic blockers are active — turning the gate on/off stays a repository setting (gateCheckMode), and the fix(github): block only confirmed Gittensor contributors in the PR Gate #644 invariant holds: only confirmed Gittensor contributors are ever hard-blocked, regardless of the manifest (verified by test).
• Dogfood: the repo's own .gittensory.yml (+ bundled mirror, kept byte-aligned) now declare a gate: block; CONTRIBUTING documents the schema + precedence. The chosen values match current effective behavior, so this repo's gate is unchanged.

Tests / validation (from repo root)

• parseFocusManifest gate config: valid / invalid (warns, never throws) / partial / readiness block / clamping / non-mapping / gateConfigToJson cache round-trip / YAML.
• gateCheckPolicy precedence: manifest overrides each mode; per-field fallback to DB; end-to-end evaluateGateCheck proving a manifest linkedIssue: block blocks a confirmed author's no-issue PR even when DB is advisory, the inverse relief, and that a non-confirmed author still resolves to neutral.
• npm run typecheck clean · full vitest green · npm run test:coverage — 97.02% branches (≥97% gate) · git diff --check clean.

Scope note

This is the config-as-code foundation. The deterministic slop-risk blocker stays tracked in #635 (contributor PR) — once it's rebased onto #644's single path, it plugs straight into this config (gate.slop). Enabling the gate purely via yml (vs. the dashboard) is deferred to avoid a manifest fetch on every gate-off repo.

[ghost]

Note

Gittensory Gate skipped

PR closed before full evaluation. No late first comment was created.

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#647 is no longer open.	No action.

---

💰 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.

[superagent-security]

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

[ghost]

gittensory · advisory review

Reviewed 13 changed file(s) — two independent AI reviewers.

Suggested action: ✅ Safe to merge — both reviewers found no blocking issues.

Reviewer A · gpt-oss-120b — recommends ✅ merge
This PR adds full config‑as‑code support for .gittensory.yml, including gate, settings, and review overrides, and integrates them throughout the pipeline with new parsing, resolution, and comment generation logic. The changes are comprehensive, well‑tested, and respect the public‑safe sanitization constraints.

Suggestions

• Verify that the function sanitizePanelText used in buildPublicPrIntelligenceComment exists and applies the same public‑safe checks as sanitizePublicComment.
• Add a unit test that confirms a non‑public‑safe footer or note is dropped and logged as a warning.
• Run the full test suite to ensure no other callers of buildPublicPrIntelligenceComment need the new review argument (the default is safe).

Worth double-checking

• If sanitizePanelText is missing or behaves incorrectly, public‑unsafe content could be emitted.
• Any existing code that constructs a FocusManifest manually must now include the new fields; missed updates could cause undefined behavior.

Reviewer B · nemotron-3-120b-a12b — recommends ✅ merge
This PR introduces config-as-code via .gittensory.yml to authoritative override repository settings (gate behavior, review panel customization, etc.) while preserving the confirmed-contributor-only blocking invariant. Changes are extensive but cohesive, with proper layering (.gittensory.yml > DB > defaults), thorough tests, and maintained public/private safety boundaries. The implementation correctly handles manifest parsing, caching, and effective settings resolution.

Suggestions

• Consider adding a comment in resolveRepositorySettings clarifying that the manifest is loaded per-webhook (with caching) to avoid confusion about freshness.
• In src/signals/focus-manifest.ts, the parsePublicSafeText function could use a constant for MAX_ITEM_LENGTH instead of a magic number (though it's imported, verifying consistency is good).
• The gateCheckPolicy function export in queue/processors.ts might benefit from a JSDoc comment explaining its role in the gate evaluation pipeline.

Worth double-checking

• Ensure the TTL for cached manifests is appropriate so newly added .gittensory.yml files are picked up promptly (currently relies on persistRepoFocusManifest TTL).
• Verify that all public-facing text from manifest (footerText, note) runs through sanitizePublicComment/isFocusManifestPublicSafe - the code shows this is done.
• Confirm that the review.fields show/hide functionality doesn't accidentally hide critical gate/security information (it's cosmetic only per comments).