feat(autonomy): parallel execution scales to 10+ concurrent subplans #1201

Merged
brent.edwards merged 1 commits from feature/m6-parallel-scaling into master 2026-03-31 23:57:40 +00:00

1 Commits

Author SHA1 Message Date
brent.edwards 4c8cfdcc60 feat(autonomy): parallel execution scales to 10+ concurrent subplans
CI / benchmark-publish (pull_request) Has been skipped
CI / build (pull_request) Successful in 19s
CI / helm (pull_request) Successful in 21s
CI / lint (pull_request) Successful in 3m18s
CI / quality (pull_request) Successful in 3m42s
CI / typecheck (pull_request) Successful in 3m56s
CI / security (pull_request) Successful in 4m6s
CI / unit_tests (pull_request) Successful in 6m34s
CI / docker (pull_request) Successful in 1m31s
CI / coverage (pull_request) Successful in 12m43s
CI / e2e_tests (pull_request) Successful in 19m39s
CI / integration_tests (pull_request) Successful in 24m43s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-regression (pull_request) Successful in 55m19s
Add M6 parallel-scaling coverage for 10+ concurrent subplans by
introducing a 15-subplan Behave scenario with explicit peak-concurrency
bound checks (max_parallel=10) and thread-safe concurrency tracking
via _build_executor().

Add deep hierarchical decomposition coverage (4+ levels) and adjust the
decomposition leaf condition to only stop early when hitting max_depth
or when the workset is trivially small (min_files_per_subplan).  A
non-progress guard prevents pathological recursion when clustering
cannot meaningfully split the file set.

Add a small-project regression test (< 50 files) verifying that the
relaxed leaf condition does not cause unexpected decomposition depth
for small worksets.

Add ASV benchmark coverage for 15-subplan parallel execution to track
scaling behavior under higher concurrency.

Note: the _build_hierarchy child-linkage correctness fix (returning
node_id from recursive calls instead of using nodes[-1].node_id) has
been removed from this PR per review feedback — it is a separate bug
fix and will be submitted as an independent issue/PR per CONTRIBUTING.md
atomic commit policy.

ISSUES CLOSED: #855
2026-03-31 23:11:06 +00:00