Diagnose Agentforce Planner Configuration

1. Traces the runtime or commit error to the planner wiring. In one case a Slack agent failed with a generic error because of cross-plugin contamination in the planner. In another, a version commit error came from a redundant function junction record, auto-created when a Data Library was connected through the UI.
2. Cleans the planner bundle so it stands alone, removes a duplicate action definition, updates the BotVersion role through a metadata deploy, then redeploys and reactivates the agent.
3. Deletes redundant junction and orphan instruction records, reactivates the agent and confirms that grounding and topics still work.
4. When Tooling API patches do not reach the published version and redeploying creates empty planners, writes a prompt document so the edits can be made by hand in the UI.

For failures inside a single action, see Diagnose Agentforce Action Failures.