Second Brain

Bible v18.1 → v19.1.7 framework upgrade for tableau MCP pair: shipped…

1 min read

Bible v18.1 → v19.1.7 framework upgrade for tableau MCP pair: shipped…

Decision

Bible v18.1 → v19.1.7 framework upgrade for tableau MCP pair: shipped v6.0.1 with 521 tools (514 baseline + 7 R29-verified API 3.27/3.28 capability adds), full enforcement triad (install_annotator + Contract Enforcer + G8 redact_processor), R11 cleanup, R13 cascade alignment, SIGNED via 12-Check Gate 12/12 GREEN + R32 census 0 RED.

Rationale

User directive “ensure all latest Tableau endpoints fully covered, max coverage, max performance, zero ambiguity, zero technical debt” required the full Bible 9-Phase Upgrade Playbook, not a cosmetic patch. Phase 1.5 Upstream Sync surfaced 7 verifiable gaps (TSC method existence + vendor docs URL); zero-deferred-must-adopt rule required all 7 to ship in this cycle. Two FastMCP-vs-Bible incompatibilities (R34 Pattern 3 *args wrapper, R35 banned-tool stub signature) discovered at cutover, root-cause-fixed inline (handlers already return dict; banned stub uses inspect.signature). Tier 1 deployment per R16 (single-operator personal VPS) — trivy informational HIGH OS-deps acceptable; cosign/SLSA-L3 banned as gold-plating. Live state validated end-to-end: /health surfaces version=6.0.1, framework=v19.1.7, tools=521, contract.pair_status=SIGNED.

Alternatives Rejected

Outcome

Pending

Graph View

Backlinks