The retry value of review.on_status_contradiction (ReviewPolicy.on_status_contradiction, src/bmad_loop/policy.py) is documented as "legacy" in both core.toml's field description and the policy docstring, since #334 introduced escalate as the default and demoted retry to a compatibility fallback. Until now it named no concrete removal target and emitted no load-time warning.
This issue is the tracking/ownership point for actually removing the retry value from REVIEW_ON_STATUS_CONTRADICTION_MODES and its handling, targeted for version 0.12.0.
Acceptance criteria
retry is removed from REVIEW_ON_STATUS_CONTRADICTION_MODES and ReviewPolicy.on_status_contradiction in src/bmad_loop/policy.py.- Any remaining docs/tests referencing
retry for this field are updated to escalate.
- Released as part of, or after, version 0.12.0.
The
retryvalue ofreview.on_status_contradiction(ReviewPolicy.on_status_contradiction,src/bmad_loop/policy.py) is documented as "legacy" in bothcore.toml's field description and the policy docstring, since #334 introducedescalateas the default and demotedretryto a compatibility fallback. Until now it named no concrete removal target and emitted no load-time warning.This issue is the tracking/ownership point for actually removing the
retryvalue fromREVIEW_ON_STATUS_CONTRADICTION_MODESand its handling, targeted for version 0.12.0.Acceptance criteria
retryis removed fromREVIEW_ON_STATUS_CONTRADICTION_MODESandReviewPolicy.on_status_contradictioninsrc/bmad_loop/policy.py.retryfor this field are updated toescalate.