Salesforce MCP v7.1.0 must implement R26 Complete-Capability Invariant…

Decision

Salesforce MCP v7.1.0 must implement R26 Complete-Capability Invariant — all profile/permission-set operator-intent tools deliver in one round-trip; MCP absorbs reader/writer asymmetry, name validation, and dependency closure resolution; only Salesforce official-endpoint limits are acceptable refusal cases. 19-permission tightening on System Administrator Clone profile is parked until v7.1.0; no manual UI workaround per zero-limitation policy.

Rationale

v7.0.2 fixed test_level rejection on production deploys but exposed three deeper gaps: (1) no symmetric Profile reader for the writer (sf_retrieve_metadata succeeds but doesn’t surface zip contents; sf_get_profile_permissions returns only ~16 of ~250 flat columns); (2) no permission-name validator (3 retired names discovered by trial — ManageMobileConfigurations, UploadPackaging, ManageEncryptionKeys); (3) no dep-closure resolver (Salesforce returns one dep error per deploy attempt, forcing O(N) round-trips). All three gaps map to FULLY-AVAILABLE Salesforce endpoints — they are MCP composition gaps, not platform limits. AJ directive 05-May-2026 mandates zero-limitation: MCP absorbs all complexity, no caller iteration, no manual UI fallback. Roadmap captures 6-priority v7.1.0 (P1 sf_get_profile_full_metadata via mdapi.retrieve includeZip; P2 sf_validate_user_permissions via Profile/PermissionSet describe; P3 sf_resolve_permission_dependencies via bundled JSON + live API + empirical bootstrap; P4 sf_update_profile_metadata auto-resolve defaults; P5 sf_disable_profile_permissions one-shot operator API; P6 PermissionSet/MutingPermissionSet mirrors). Tool count 673 to 682. Acceptance regression: P5 must succeed against System Administrator Clone in one call against production with 1 active user retaining 8 keep-list permissions.

Alternatives Rejected

Outcome

Pending