GenAiPlugin-only deploy reports Succeeded but has no effect on the running agent — planner bundle is the actual carrier and requires an inactive agent

CLI Version:
@salesforce/cli/2.149.9

Architecture:
win32-arm64

Node Version:
node-v24.14.1

Plugin Version:
@oclif/plugin-autocomplete 3.2.56 (core)
@oclif/plugin-commands 4.1.63 (core)
@oclif/plugin-help 6.2.58 (core)
@oclif/plugin-not-found 3.2.93 (core)
@oclif/plugin-plugins 5.4.87 (core)
@oclif/plugin-search 1.2.54 (core)
@oclif/plugin-update 4.7.59 (core)
@oclif/plugin-version 2.2.57 (core)
@oclif/plugin-warn-if-update-available 3.1.73 (core)
@oclif/plugin-which 3.2.61 (core)
@salesforce/cli 2.149.9 (core)
agent 2.0.5 (user)
apex 4.1.0 (core)
api 2.0.9 (core)
auth 5.0.6 (core)
code-analyzer 5.12.0 (user)
data 5.1.5 (core)
deploy-retrieve 4.1.2 (core)
info 4.0.9 (core)
limits 4.0.3 (core)
marketplace 2.0.5 (core)
org 6.0.9 (core)
packaging 3.0.5 (core)
schema 4.0.5 (core)
settings 3.0.5 (core)
sobject 2.0.5 (core)
telemetry 4.0.5 (core)
templates 57.0.9 (core)
trust 4.0.9 (core)
user 5.0.1 (core)

OS and Version:
Windows_NT 10.0.26200

Shell:
powershell

### Summary

Deploying a modified `GenAiPlugin` (topic instructions) to an org reports
`Succeeded`, but the running agent's behavior does not change — not even
after `sf agent deactivate` / `sf agent activate`. Instruction changes take
effect only when the `GenAiPlannerBundle` is deployed alongside, and that
deploy is refused while the agent is active
("Cannot update record as Agent is Active").

The result is a silent-success footgun: a metadata deploy that validates,
succeeds, and changes nothing observable. Verified with a canary edit — a
standing price in a topic instruction changed from 6.95 to 9.95, deploy
Succeeded, agent bounced, and the agent continued answering 6.95 until the
planner bundle was redeployed (with the agent deactivated), at which point
the change appeared immediately.

### Steps to reproduce

1. Create and activate an agent whose topic instructions contain a
distinctive fact (e.g. a price).
2. Edit the fact in the `GenAiPlugin` metadata; `sf project deploy start
--source-dir .../genAiPlugins` → Succeeded.
3. `sf agent deactivate` + `sf agent activate`; ask the agent for the fact:
it answers the OLD value.
4. Deactivate; deploy genAiPlugins **and** genAiPlannerBundles; activate:
it answers the NEW value.

### Expected result

Any of: the plugin deploy updates the live agent; the deploy emits a
warning that changes will not take effect until the planner bundle is
republished; or the deployment/docs make the planner-bundle dependency and
the active-agent gate explicit. Today the dependency is discoverable only
by observing that a succeeded deploy did nothing.

### Environment

- sf CLI:
- Org: Agentforce Developer Edition (`orgfarm-*.develop.my.salesforce.com`)

Reproduce the behavior with `sf project deploy start --source-dir .../genAiPlugins`, then compare it with a deployment including `genAiPlannerBundles` while the agent is deactivated. Start from the deploy command and agent activate/deactivate flows described in the issue. Done means the CLI updates the live agent or clearly warns about the planner-bundle dependency and active-agent requirement.

Written by the indexing model from the issue text.