Phase 1 feature flag + dual-run parity gate
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 21h 49m
- Merged PRs (30d)
- 404
Description
Add a config flag (config/unified.py, mirroring use_experimental_redis_event_dispatcher) to gate the new composition/service path so it can run alongside the legacy path for parity validation before cutover.
Success Criteria:
- [ ] Flag off -> legacy AbstractAgent path; flag on -> new service/backend path.
- [ ] Both paths confirmed to behave identically via the #1 CLI (live parity).
- [ ] Default is off (opt-in) until parity is confirmed.
- [ ] pants test passes for affected packages
JIRA Issue: BA-6766
Contributor guide
Research direction
Start in config/unified.py by comparing the requested flag with use_experimental_redis_event_dispatcher, then trace the AbstractAgent and new service/backend paths used by the #1 CLI. Confirm that the default-off flag selects the legacy path, opt-in selects the new path, both show live parity, and pants test passes for affected packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100