3 tooling issues observed during EA Tableau brand-revamp session 03-May-2026 — full doc at `/root/aj
What
3 tooling issues observed during EA Tableau brand-revamp session 03-May-2026 — full doc at /root/aj-ea/outputs/documents/dev-handoff-3-tooling-issues-03-may-2026.md. Issue 1: vault_submit_knowledge MCP wrapper rejects tags array (passes JSON-string to Pydantic list validator — same fault-class as tableau-mcp arity bugs fixed in fadb8c7). Issue 2: /root/aj-ea/outputs/data/ is not writable from MCP container UID 999 — every Tier-2 workbook delivery currently needs a host-side cp step. Recommend mounting EA outputs path into tableau-mcp via docker-compose.yml (eliminates the staging step). Issue 3: destructive-ops-blocker hook false-positive on single-file rm -f filename.ext (no -r, no wildcard) — adds friction to every cleanup. Bonus: relocate runwal_brand_transform.py from /root/aj-ea/outputs/data/ to /opt/mcp-servers/tableau-mcp/clis/twbx/scripts/ as part of the cli-anything-tableau-twbx workbook deliver build (already in dev queue per mcp-tool-feature-gap-publish-saved-credential.md).
Why
All 3 are friction in the EA Workbook Delivery Contract (newly codified in tableau-twbx skill UNIVERSAL contract). Fixing them collapses the 8-step Tier-2 delivery flow toward the future-state CLI command and removes per-session friction. None blocking — workarounds exist — but each fix removes ambiguity / shaves time per workbook delivery. Bundle with the upcoming cli-anything-tableau-twbx workbook deliver build for one cohesive shipment.
Action Required
Read full handoff doc + 4 fixes prioritized inside it. Schedule alongside the cli-anything-tableau-twbx workbook deliver build.