Deploying force-app in one go fails on Summer '26 orgs (AiAuthoringBundle limit) #140

Summary

Since my PR #134 was merged, force-app has 26 agent bundles. On Summer '26 orgs a single deploy accepts at most 50 AiAuthoringBundle instances, and each bundle counts twice, so deploying force-app in one go now fails there. This breaks the README install steps and bin/install-scratch.sh/.bat on Summer '26 orgs.

On the current release the limit is 100 instances (50 bundles), so a fresh scratch org accepts the deploy today, but every org will hit the limit once the repo reaches 50 bundles.

CI on main failed at the "Deploy employee agent recipes" step on the #134 merge, which looks like the same limit, but I can't see the job log to confirm. A re-run may pass now.

I have a fix that deploys in two batches (16 and 10 bundles). I tested it end to end in a scratch org (all CI steps, 103/103 Apex tests) and I'm happy to open a PR.

Salesforce Org Type

Developer Edition Org

Steps To Reproduce

1. Use a Developer Edition org on Summer '26 (API version 67.0).
2. Check out main.
3. Run sf project deploy start --source-dir force-app --dry-run --test-level NoTestRun -o <org>

Current Behavior

The deploy is rejected before any component is deployed. At the commit before #134 (25 bundles) the same command succeeds. At the #134 merge (26 bundles) it fails.

Expected Behavior

force-app deploys on Summer '26 orgs, and keeps deploying as new recipes are added.

Relevant Log Output

You attempted to deploy 52 instances of AiAuthoringBundle, more than the maximum limit of 50 allowed by the system. Please contact your administrator for more information.

Code of Conduct

• I agree to follow this project's Code of Conduct