fix(ci): allowlist COMBO_LOOP_SAFETY_TIMEOUT_MS as a doc-only source constant

The env/docs contract gate had a SECOND violation on the release tip, added after
this branch was cut: #13857's comboTimeoutMs narrative in ENVIRONMENT.md cites
COMBO_LOOP_SAFETY_TIMEOUT_MS, which is a source constant
(open-sse/services/combo/comboPredicates.ts:35 — `10 * 60 * 1000`), not an
operator-facing env var. The doc regex captured the SHOUTY_NAME and reported it
as documented-but-missing-from-.env.example.

DOC_ONLY_ALLOWLIST already exists for exactly this class (see CLI_COMPAT_OMITTED_PROVIDER_IDS,
LOCAL_ONLY_API_PREFIXES, VACUUM). Gate now reports all three directions in sync.
This commit is contained in:
diegosouzapw
2026-09-18 04:08:43 -03:00
parent 29ce2267cc
commit f44eea2cdf

View File

@@ -272,6 +272,10 @@ const DOC_ONLY_ALLOWLIST = new Set([
// SQL keyword mentioned in the new VACUUM scheduler docs (#4437).
// The check's regex picks up the bare word in description text.
"VACUUM",
// Source-code constant (open-sse/services/combo/comboPredicates.ts:35 —
// `export const COMBO_LOOP_SAFETY_TIMEOUT_MS = 10 * 60 * 1000`), cited in the
// comboTimeoutMs narrative added by #13857. Not operator-configurable.
"COMBO_LOOP_SAFETY_TIMEOUT_MS",
]);
// Vars present in .env.example but intentionally absent from ENVIRONMENT.md.