Repository navigation
fix: enforce per-agent capacity during concurrent run startup - #3
Merged
Merged
Conversation
ULis3h
marked this pull request as ready for review
November 2, 2026 14:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
maxConcurrent.CI blockers fixed while validating
node --testdiscovery, preserving all five tests.npm ciso native Prisma generation matches runtime.Validation
cdc04e7089135328ef14fbe3a0133b3b53172d23). Final-head CI passed for2b0a8fe2639ccab766b4a4b19ffc55ded94d2233: Node 20 and Node 22 typecheck/tests/build, plus Docker image build and smoke test.No public APIs or application dependency versions changed. No merge or deployment performed.