SHA-23: Stage 5 capability matrix and release-note rollup - #58
Conversation
Align README Supported/Partial/Not-supported claims and design-doc status with main after SHA-12 C–J. Add §11 residual checklist, epic release-note narrative, Towncrier fragment, and refresh fixture gap inventory. No protocol features — public claims only; still not full Garmin FIT conformance. Co-authored-by: multica-agent <github@multica.ai>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9ed04e27be
ℹ️ 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".
| @@ -0,0 +1,6 @@ | |||
| Stage 5 capability-matrix and release-note pass (Multica SHA-12 / L): README | |||
There was a problem hiding this comment.
Rewrite the fragment for release-note readers
When Towncrier builds the next release, this fragment will publish internal planning language such as “Stage 5,” “Multica SHA-12 / L,” “C–J,” and “§11” instead of concisely telling users what documentation or capability guidance changed. Rewrite it as a standalone user-facing description of the updated capability matrix and documented conformance limits.
AGENTS.md reference: AGENTS.md:L138-L138
Useful? React with 👍 / 👎.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #58 +/- ##
=======================================
Coverage 92.72% 92.72%
=======================================
Files 36 36
Lines 2721 2721
Branches 461 461
=======================================
Hits 2523 2523
Misses 117 117
Partials 81 81 ☔ View full report in Codecov by Harness. |
Codex P1: user-facing capability-matrix wording instead of Multica stage/issue planning language. Co-authored-by: multica-agent <github@multica.ai>
Summary
Stage 5 (L) public-claims pass for Multica epic SHA-12 after stages 1–4 (C–J) landed on
main.news/SHA-23.doc+ epic rollup narrativedocs/EPIC_SHA12_RELEASE_NOTES.mdfor the next version bump (no version bump in this PR).validation.pymodule docstring brought in line with shipped FILE_TYPE / scopes.No new protocol features.
Acceptance (SHA-23)
done/in_reviewwith clear residual list (§11 checklist)Test plan
uv run pytest fit_tool/tests/test_public_api.py fit_tool/tests/test_validation.py fit_tool/tests/test_profile_scope.py -q(52 passed)ProfileScope/IMPLEMENTED_FILE_TYPESon review