docs: update TODO.md — mark P0–P5 done, promote P3 as next priority#120
docs: update TODO.md — mark P0–P5 done, promote P3 as next priority#120
Conversation
Reviewer's GuideDocumentation-only PR updating TODO.md to reflect stabilization progress: test/PR counts corrected, recent completion list extended, and P0–P5 work items marked as done or reprioritized, with P3 highlighted as the final blocker before v1.0. State diagram for stabilisation tasks P0–P5 status updatestateDiagram-v2
[*] --> P0
[*] --> P1
[*] --> P2
[*] --> P3
[*] --> P4
[*] --> P5
state P0 {
[*] --> done
done: status_done_in_PR_117
}
state P1 {
[*] --> done
done: status_done_in_PR_117
}
state P2 {
[*] --> done
done: status_done_in_PR_117
}
state P4 {
[*] --> partial
partial: status_partially_done_in_PR_117
}
state P5 {
[*] --> done
done: status_done_in_PR_117
}
state P3 {
[*] --> next_priority
next_priority: status_last_blocker_before_v1_0
}
P0 --> stabilisation_progress
P1 --> stabilisation_progress
P2 --> stabilisation_progress
P4 --> stabilisation_progress
P5 --> stabilisation_progress
state stabilisation_progress {
[*] --> nearing_v1_0
nearing_v1_0: P0_P1_P2_P4_P5_done_P3_remaining
}
P3 --> v1_0_release_ready
state v1_0_release_ready {
[*] --> blocked
blocked: pending_completion_of_P3_import_time_side_effects
}
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
🔒 Security Analysis ReportSecurity Analysis ReportGenerated: Tue Mar 31 19:30:27 UTC 2026 Bandit Security ScanSafety Check ResultsPip-Audit Results |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c742b0617b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - **Version**: 0.9.0 (beta — stabilisation in progress) | ||
| - **Tests**: 2,173 collected, 16 skipped | ||
| - **Tests**: 2,158 passing, 15 skipped |
There was a problem hiding this comment.
Reconcile skipped-test count with P16 breakdown
The updated health summary now states 15 skipped, but the unchanged P16 table in the same file still enumerates 12 + 2 + 1 + 1 = 16 skipped tests. This internal mismatch makes the TODO status unreliable for release planning (especially since this commit explicitly claims to have corrected the test counts), so either the headline count or the per-file breakdown needs to be updated to the same source-of-truth.
Useful? React with 👍 / 👎.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
Test plan
🤖 Generated with Claude Code
Summary by Sourcery
Update TODO documentation to reflect current stabilisation progress and testing status for the v1.0 release.
Documentation: