Add documentation for retry configuration in planning mode: - Document retry settings in .g3.toml under [agent] section - Note RetryConfig implementation in g3-core/src/retry.rs - Clarify hardcoded vs config-based retry values Verify existing retry loop and coach feedback parsing: - Confirm execute_with_retry() handles recoverable errors - Document feedback extraction source priority order - Provide manual verification steps for testing
667 B
667 B
Planning Mode Verification Tasks
1. Document Retry Configuration Location
- Add coach and player retry config examples to config.example.toml
- Document the relationship between config file settings and RetryConfig::planning()
2. Verify Retry Loop Functionality
- Review retry logic implementation (already done - looks correct)
- Document verification findings
3. Verify Coach Response Parsing
- Review feedback extraction implementation (already done - looks correct)
- Document verification findings
4. Optional: Add Integration Test
- Create integration test for retry + feedback extraction flow in g3-planner/tests/