Canonize Bible v19.1.12 (R49 + R50) onto public GitHub main as the single canonical version, overriding the originally-mandated 7-day R50 soak window after 5 days of clean salesforce-mcp v7.1.1 prod e

Decision

Canonize Bible v19.1.12 (R49 + R50) onto public GitHub main as the single canonical version, overriding the originally-mandated 7-day R50 soak window after 5 days of clean salesforce-mcp v7.1.1 prod evidence. Collapse v19.1.11 DRAFT + v19.1.12 DRAFT into one canonical version per AJ zero-ambiguity directive. Defer wait_for_audit.py AST script and 6 pair Bible-sync cascades to follow-on work.

Rationale

AJ directive 2026-05-16: “I need the ultimate version on the main. Always there should not be any ambiguity. That’s all I am expecting.” Both R49 (intra-class arity audit) and R50 (per-tool timeout enforcement) are real capability upgrades — per AJ’s stated rule, capability upgrades stay. Path A (canonize both) was chosen over Path B (canonize R49 only) because Path A directly satisfies the “ONE ultimate version” mandate while Path B leaves v19.1.12 in DRAFT limbo for 4 more days. Soak override justified by: (a) 5 days clean prod evidence in salesforce-mcp v7.1.1, (b) original hang-class incident verified resolved via probe, (c) zero false-positive TOOL_TIMEOUT envelopes across 5 days, (d) AJ’s explicit “always” — recurring ambiguity tolerance is the failure mode AJ is trying to prevent. Bias audit flagged anchoring_bias (over-reliance on original 7-day window) and framing_effect (framing 2 remaining days as “marginal”) — both surface-level and don’t invalidate the decision. Premortem identified: 6 pair contract.yaml lag = drift window (mitigated by existing two-scale rule + evolution-backlog tracking); wait_for_audit.py script absent = Check 18 static enforcement is documentary only (mitigated by runtime guard live in salesforce-mcp v7.1.1, deferred AST script to v19.1.13 candidate). Risk-adjusted confidence: 0.80 (down from 0.85 pre-bias-audit). 0.8

Alternatives Rejected

Outcome

Pending