Repository navigation
feat(cli): tole doctor coverage ledger (#378, 3/3) - #392
Merged
Merged
Conversation
🔍 Cora AI Code Review✅ No issues found. Code looks good! Review powered by cora-code · BYOK · MIT |
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.
What
Part 3 of 3 of
tole doctor: the persisted coverage ledger and theREADY n-of-msummary. Builds on #388 (offline/catalog) and #390 (full).Why
#378. Release validation needs the result of a run to outlive the terminal, and a one-line answer to "how many providers are proven, and what blocks the first one that is not?".
Changes
doctor.rs: ledger at$CODECORA_HOME/tole/doctor-ledger.json— per provider + model: level reached, first blocker, fix command, timestamp. The provider identity is the redacted URL (no userinfo/query/fragment); the API key is never stored. Latest run wins per provider + model.main.rs:tole doctor --summaryprintsREADY n-of-m+ first blocker + fix without running anything;--no-ledgerskips recording.Testing
READY 1-of-1, a no-tool-calling provider exits 1, the ledger file is 0600 and contains neither the API key nor URL credentials.Refs #378