Roadmap: align global vs. per-repo Gittensory config naming, values, and functional scope

[JSONbored]

Config & naming drift alignment — roadmap

An audit (2026-07-12) of the Gittensory self-host fleet found 23 confirmed places where the global config, the 3 per-repo private configs (gittensory / metagraphed / awesome-claude), and the product's own naming/docs disagree with each other or with what the code actually does. Every finding was independently re-verified against the current codebase before being tracked here.

Why this matters

This class of bug has already caused real operational pain once: gate.enabled: false was believed to be a full AI-spend kill switch but only ever controlled whether a check-run published — real AI spend kept running invisibly. Several sub-issues below are the same shape (a setting whose name promises more than it delivers), just not yet caught.

Scope

• Section 1 — Duplicate config-template files (2 sub-issues)
• Section 2 — Live global vs. per-repo config value drift (9 sub-issues — VPS-only operational edits, not PRs)
• Section 3 — Naming drift across yml / TypeScript / DB / GitHub UI (3 sub-issues)
• Section 4 — Functional-scope drift: coarse toggles that don't do what their name implies (8 sub-issues)
• Section 5 — Config-as-code coverage gaps (1 sub-issue)

Recommended fix order

1. Disclose that agentDryRun does not stop AI/LLM spend #5286 — agentDryRun doesn't stop AI spend (High)
2. Fix requireLinkedIssue docs and generated contributor docs that overclaim enforcement #5287 — requireLinkedIssue doesn't block (High)
3. Fix docs that describe checkRunMode/reviewCheckMode backwards #5283 — checkRunMode/reviewCheckMode docs backwards (High)
4. Restore 2026-07-09 gate incident-response fields to global.gittensory.yml (VPS) #5274 — Global gate: block missing the 2026-07-09 restoration (High)
5. Retire the dead blockedPaths key and fix stale templates that document it as live #5294 — Dead blockedPaths key + stale templates (Medium)

Everything else is real and verified but lower-urgency — no live functional impact today, each a small, isolated, low-risk fix.

Sub-issues

Section 1 — Duplicate config-template files

• Document the shared.gittensory.yml (_shared) layer across templates and docs #5273 — Document the shared.gittensory.yml (_shared) layer across templates and docs

Section 2 — Live global vs. per-repo config value drift (VPS-only, not PRs)

• Restore 2026-07-09 gate incident-response fields to global.gittensory.yml (VPS) #5274 — Restore 2026-07-09 gate incident-response fields to global.gittensory.yml
• Align or document gittensory's screenshotTableGate presence-only mode vs metagraphed's matrix #5275 — Align or document gittensory's screenshotTableGate presence-only mode vs metagraphed's matrix
• Fix global.gittensory.yml's gittensor:priority label-propagation mapping (VPS) #5276 — Fix global.gittensory.yml's gittensor:priority label-propagation mapping
• Promote regateSweepOrderMode: oldest-first into global.gittensory.yml (VPS) #5277 — Promote regateSweepOrderMode: oldest-first into global.gittensory.yml
• Relocate misplaced hardGuardrailGlobs rationale comment in gittensory's config (VPS) #5278 — Relocate misplaced hardGuardrailGlobs rationale comment in gittensory's config
• Add rationale comment to awesome-claude's gate.linkedIssue: advisory (VPS) #5279 — Add rationale comment to awesome-claude's gate.linkedIssue: advisory
• Add rationale comment to gittensory/metagraphed's aiReview.closeConfidence: 0.95 (VPS) #5280 — Add rationale comment to gittensory/metagraphed's aiReview.closeConfidence: 0.95
• Add "experimental" to config-lint.ts's TOP_LEVEL_FIELDS allowlist #5281 — Add "experimental" to config-lint.ts's TOP_LEVEL_FIELDS allowlist
• Promote fleet-unanimous features.* and issueDiscoveryPolicy to global.gittensory.yml (VPS) #5282 — Promote fleet-unanimous features.* and issueDiscoveryPolicy to global.gittensory.yml

Section 3 — Naming drift across yml / TypeScript / DB / GitHub UI

• Fix docs that describe checkRunMode/reviewCheckMode backwards #5283 — Fix docs that describe checkRunMode/reviewCheckMode backwards
• Fix stale doc comment claiming review.linkedIssueSatisfaction is unconsumed #5284 — Fix stale doc comment claiming review.linkedIssueSatisfaction is unconsumed
• Document the engine-layer readinessMode/readinessMinScore rename #5285 — Document the engine-layer readinessMode/readinessMinScore rename

Section 4 — Functional-scope drift: coarse toggles that don't do what their name implies

• Disclose that agentDryRun does not stop AI/LLM spend #5286 — Disclose that agentDryRun does not stop AI/LLM spend
• Fix requireLinkedIssue docs and generated contributor docs that overclaim enforcement #5287 — Fix requireLinkedIssue docs and generated contributor docs that overclaim enforcement
• Document that publicSurface: off does not suppress either check-run #5288 — Document that publicSurface: off does not suppress either check-run
• Clarify that moderationGateMode: off does not disable the four anti-abuse mechanisms #5289 — Clarify that moderationGateMode: off does not disable the four anti-abuse mechanisms
• Fix stale reviewEvasionProtection default claim and disclose always-on counter #5290 — Fix stale reviewEvasionProtection default claim and disclose always-on counter
• Cross-reference gateDryRun and agentDryRun so they aren't assumed to be one system #5291 — Cross-reference gateDryRun and agentDryRun so they aren't assumed to be one system
• Retire or correctly disclose the inert firstTimeContributorGrace dashboard toggle #5292 — Retire or correctly disclose the inert firstTimeContributorGrace dashboard toggle
• Document that autoLabelEnabled only gates the base gittensorLabel #5293 — Document that autoLabelEnabled only gates the base gittensorLabel

Section 5 — Config-as-code coverage gaps

• Retire the dead blockedPaths key and fix stale templates that document it as live #5294 — Retire the dead blockedPaths key and fix stale templates that document it as live

---

Tracking issue only — no code changes land here directly. See each sub-issue for its own context, requirements, deliverables, and expected outcome.

[linear-code]

JSO-3763