Adding a shared connected-agent bot to a solution pulls in all parent bots, no way to exclude?

I'm trying to add a single Copilot Studio bot to a solution, and it's pulling in every other bot that references it as a connected agent with no prompt and no way to include just the one bot.

Repro:

1. Created a brand-new, empty solution (single publisher, no components added yet).

2. Objects → Add existing → Bot → selected only "agent_1"

3. No "include required components" dialog appeared the add just happened.

Expected: the solution contains only the selected bot (at most, plus its own connection references).

Actual: the solution jumped to 238 objects, 6 agents, 229 agent components, 3 connection references. It pulled in every other bot in the environment that has a connected-agent action pointing at "agent_1" (5 parent bots), plus their own further connected-agent dependencies.

This makes it impossible to build a scoped solution around one client-facing agent when it shares a connected-agent bot with unrelated agents elsewhere in the tenant. Normal Dataverse solution dependencies pull in what a component requires; this also seems to pull in everything that depends on it, in reverse, with no override.

Questions:

1. Is this expected/intended behavior for connected-agent solution dependency tracking?

2. Is there any supported way UI, PAC CLI, or Dataverse API to add a shared connected-agent bot to a solution without including every bot that references it?