Document that autoLabelEnabled only gates the base gittensorLabel

[JSONbored]

Context

autoLabelEnabled (src/types.ts:907, no doc comment) reads like a master label switch. Its only real consumers (shouldApplyPrLabel/willLabel, settings-preview.ts:37,108) gate exclusively the single base gittensorLabel context label — zero effect on TYPE/taxonomy labels (typeLabelsEnabled), moderation/blacklist labels, or review-state labels. This is a deliberate, well-documented design elsewhere — typeLabelsEnabled's own doc (types.ts:910-920) and schema.ts:104 both explicitly cross-reference the scoping, and config/examples/gittensory.full.yml:707-714 has an explicit "#label-decoupling, #label-scoping... Four independent label families, none of which gates or silently disables another" comment. The genuinely under-documented spot is the dashboard: maintainer-settings.tsx:424 renders the toggle as plain "Auto-label PRs" with no scoping hint — the most likely place a real maintainer (who hasn't read types.ts or yml comments) would be misled.

Requirements

• Do not rename the field — breaking change to a public yml key + DB column + OpenAPI field, disproportionate to a naming-clarity nit.

Deliverables

• Add a doc comment above autoLabelEnabled (types.ts:907) mirroring the cross-reference style already used by typeLabelsEnabled.
• Add a short subtext/tooltip to the "Auto-label PRs" dashboard toggle (maintainer-settings.tsx:424), reusing the scoping language already written for docs.tuning.tsx:484-487.

Expected Outcome

A maintainer using the dashboard toggle understands it governs only the base context label, not the full label system.

Links & Resources

• Evidence: src/types.ts:907,910-920; src/signals/settings-preview.ts:37,108; src/db/schema.ts:104; apps/gittensory-ui/src/components/site/app-panels/maintainer-settings.tsx:424

---

Part of #5270 (roadmap epic).

[linear-code]

JSO-3785