v0.4.1

CervoMutants v0.4.1

Changelog

Changed

• Hosted adoption-wave summaries now distinguish raw recommendation entries
  from collapsed recommendation review units, and raw governance suggestion
  totals from per-status governance counts, which makes released GitHub Action
  evidence easier to interpret without hiding the raw totals.
• The published first-party GitHub Action now uses actions/setup-go@v6,
  removing the stale Node 20 deprecation path from the released action surface.
• Windows compatibility validation is more deterministic:
  pre-canceled pool commands no longer start real processes, and the serial
  runner budget/quarantine coverage no longer depends on real-clock races.

Documentation

• Published dated follow-up notes for released adoption-wave recommendation
  review units and governance suggestion status counts.

Verification

• go test ./...
• go run ./cmd/releasehelper verify-compat
• go run ./cmd/releasehelper notes --version v0.4.1 --out .tmp/release-notes-v0.4.1.md

Upgrade Notes

Summary

• v0.4.1 is a patch release that tightens the released GitHub Action surface
  and sharpens how released adoption-wave artifacts describe review workload.
• Hosted adoption-wave summaries now preserve review-unit recommendation counts
  and governance suggestion status counts in addition to the existing raw
  totals.
• The release also hardens two Windows-only CI pain points that were still
  showing up as rerun-prone flakes after v0.4.0.

Operator Action

• If you pin the first-party GitHub Action, move the tag from @v0.4.0 to
  @v0.4.1 so the released action picks up the current setup-go@v6 surface
  and the latest hosted-wave/reporting refinements.
• If you use released adoption-wave artifacts to judge rollout quality, start
  reading these fields together instead of overloading the raw totals:
  • recommendation_entries
  • recommendation_review_units
  • collapsed_recommendation_duplicates
  • governance_total_suggestions
  • governance_suggestions_by_status
• If you validate CervoMutants on Windows runners, rerun pressure should be
  lower after this patch, but keep the same bounded-lane discipline and
  version pinning you already use for release adoption.

Rollback

• Reinstall v0.4.0 if the new release causes friction and you need to return
  quickly to the previous public surface.
• If rolling back from hosted-wave or adoption-analysis workflows, also return
  any interpretation docs or automation that assumed the new recommendation
  review-unit or governance-status fields.
• Keep the rollback within the same install family where possible:
  • go install github.com/cervantesh/cervo-mutants/cmd/cervomut@v0.4.0
  • reinstall the v0.4.0 GitHub release archive