chore(toolchain): upgrade medharness to 0.10.0 and migrate dhfkit commands - #117
Merged
Conversation
…mands - Bump medharness[full] pin from 0.9.0 → 0.10.0 in requirements.txt - Migrate all DHF data-layer CLI calls (item, validate, doc, report) from `medharness dhf …` to the new `dhfkit` binary (split introduced in v0.8.0) - Update `medharness ci cr-status` → `medharness change status` (v0.8.0 rename) - Document dhfkit as bundled inside the medharness wheel (one install, both CLIs) - Add v0.9/0.10 test-point annotation guidance (@testing:T1 / @pytest.mark.dhf_testing) to Agent Rule #3 and the for-stage stage name hint to Quick Reference - Fix autocontour:service script to use .venv/bin/python -m uvicorn for unambiguous venv resolution Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… command API medharness 0.8.0 reorganised the CLI — the flat `ci` subgroup was replaced by focused groups. Update all workflow files and the contract check script to use the new API: ci generate-dhf → change plan ci develop-cr → change implement ci cr-status → change status ci advance-stage → change advance ci approve-gate → approval check ci github-event → automation github-event ci validate-branch → verify branch ci validate-code → verify code ci dhf-validate → verify dhf ci test-coverage → verify tests ci test-points → verify tests ci validate-verif. → verify verification ci evidence bundle → evidence bundle Also bump medharness-setup action pin from 0.9.0 → 0.10.0 to match requirements.txt (fixes MedHarness Contract CI gate). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… tests The old ci test-points command accepted --req-type; the new verify tests command uses the full --requirement-type flag. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
medharness[full]pin0.9.0 → 0.10.0inrequirements.txtmedharness dhf …to the newdhfkitbinary (CLI split introduced in v0.8.0 —dhfkitis bundled inside the medharness wheel, no separate install needed)medharness ci cr-status→medharness change status(v0.8.0 rename)@testing:T1/@pytest.mark.dhf_testing)autocontour:servicescript:.venv/bin/uvicorn→.venv/bin/python -m uvicornfor unambiguous venv Python resolutionDHF impact
No DHF items updated — infrastructure/toolchain change only, no product functionality affected.
Validation
medharness --version→0.10.0✓dhfkit --dhf DHF item list --type cr→ works ✓dhfkit --dhf DHF validate schema→ all 96 items passed ✓medharness --dhf DHF change status→ command recognised ✓Manual testing remaining
🤖 Generated with Claude Code