You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added focused routing coverage in packages/patterns/tests/multi-agent/routing-worker-selection.test.ts, routing-rule-based.test.ts, routing-llm.test.ts, and routing-registry.test.ts, with shared fixture support in routing.fixtures.ts
Kept combined routing and node-path verification green in packages/patterns/tests/multi-agent/nodes.test.ts, validating the modularized strategy split against the surrounding multi-agent flow
Added story documentation in docs/st09048-modularize-multi-agent-routing-strategies-and-tests.md capturing the modularization scope, file-size reduction, validation evidence, and review-driven hardening follow-ups
Reduced packages/patterns/src/multi-agent/routing.ts from a mixed-responsibility 373 line implementation to a 51 line public facade
Extracted focused internal routing modules for LLM, round-robin, skill-based, load-balanced, and rule-based strategies plus shared worker-selection helpers under packages/patterns/src/multi-agent/routing-internal/
Preserved public routing exports and existing runtime behavior while making the routing layer easier to review, extend, and test in smaller slices
Fixed
@agentforge/patterns - Routing Registry and Test Contract Hardening
Hardened routing strategy lookup so inherited object keys such as toString and __proto__ cannot bypass the unknown-strategy guard
Aligned shared routing test fixtures with schema-required message id fields and kept tracker/checklist state consistent through the modularization review cycle
Kept the explicit-any baseline flat at workspace 90/289 and patterns 2/28 while modularizing both production and test code
Published
All packages published to npm registry at version 0.16.33: