Route sf_update_profile_metadata through Metadata REST PATCH (relative…
Decision
Route sf_update_profile_metadata through Metadata REST PATCH (relative path) and add a single shared source_slice helper to gate all large-source readers’ token usage; do NOT widen scope to fix metadata_router.metadata_rest* double-prefix in same change.
Rationale
Surgical fix discipline: each tool’s bug fixed at its own call site, avoiding cross-cutting refactor that would (a) widen blast radius beyond the user’s reported issues, (b) risk regressions on other Metadata-REST-routed types (WorkflowRule, ApprovalProcess, SharingRules, etc.) that haven’t been load-tested with the corrected path. Profile via Metadata REST verified live (404 cleanly resolved against fullcopy). Source_slice helper consolidates slicing logic into one chokepoint with full unit-test coverage (9 cases including 4,000-line synthetic body). Backward-compatible — defaults preserve full-body return. Codex hard-gate caught a URL double-prefix bug at design time → reinforces value of cross-model review for surgical changes touching unfamiliar API patterns.
Alternatives Rejected
Outcome
Pending
Related
- plan-v2-is-not-foolproof-without-5-mitigations-added-for-the
- snowflake-mcp-v2203-upgrade-quality-audit-full-pass-bible-v1
- ship-tableau-mcp-v602-groupitem-hydration-fix-and-hand-back
- for-apex-test-class-deployment-via-salesforce-mcp-split-mono
- salesforce-mcp-skill-upgrade-scoped-to-sales-cloud-service-c