[BUG]

The Microsoft Copilot Studio Kit "File synchronization" process runs overnight at 2 AM every day and the agents target by this process goes to a "draft" state after the job finish.
Because of this, if used by other agents, those agents will not be able to obtain responses while the agents in the "draft" state are not republished.

Steps to reproduce the behavior:

1. Agent X uses agent Y.
2. Agent Y have a Copilot Studio Kit file syncronization process to copy files from a sharepoint folder to the knowledge base of agent Y.
3. The job runs every day at 2am.
4. After the job runs the agent Y goes to a "draft" state.
5. Because of that when we make a prompt to agent X that are related to agent Y, agent X delegates the prompt to agent Y but he can get the answer.
6. To resolve the problem we must republish manually the agent Y every day. After that publish agent X can get the answer from agent Y.
7. The problem repeats itself every day after the nightly process of file syncronization is run.

Conclution:
It makes no sense every day we manually republish the agents in "draft" state, or have an automated process to republish each agent after the nightly synchronization process runs.
This should be handled by the Copilot Studio Kit's own synchronization process.

Start by reproducing the nightly Microsoft Copilot Studio Kit File synchronization process with an agent delegation chain and observe the target agent's state afterward. Done means synchronized agents remain usable by delegating agents without requiring manual republishing or a separate republish job.