v0.4.0

CervoMutants v0.4.0

Changelog

Added

• Semantic triage v1 with pkg/triage, actionable scoring, semantic grouping,
  actionable-only survivor views, and triage-aware report fields.
• GitHub-native review surfaces including SARIF, GitHub summary output, and
  first-party GitHub Action support for the standard CI path.
• Historical dashboards, recommendation surfaces, ownership routing, and
  baseline review lifecycle expansion for more durable survivor governance.
• Pool campaign orchestration, benchmark-corpus support, and committed example
  workspaces for small, medium, and large-repo adoption paths.

Changed

• The public support story now includes an explicit compatibility matrix,
  additive compatibility policy, and daemon/worker narrowing as an
  experimental-only surface until protocol versioning exists.
• Release automation now verifies release notes, archive contents, checksums,
  upgrade handoff, go install, and archive-install report flows before
  publication.
• Public CI and release guidance now reflect the first hardened cross-platform
  validation lane on GitHub Actions.

Documentation

• Added adoption guidance, rollout playbooks, maintainer operations guidance,
  adoption feedback intake, hosted-layer scope notes, and commercialization
  guardrails for the OSS core.
• Published the 24-month roadmap v2 and refreshed the project maturity
  assessment against the current repo-head evidence.

Verification

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

Upgrade Notes

Summary

• v0.4.0 is the first release that packages the repository's current
  semantic-triage, GitHub-native review, compatibility-policy, and release
  hardening work into one public version.
• The release expands review surfaces with actionable scoring, semantic
  grouping, GitHub summary output, SARIF, history dashboards, recommendations,
  and first-party GitHub Action support.
• The release also makes support boundaries clearer: daemon/worker remains
  explicitly experimental, while install, upgrade, and report compatibility are
  validated more aggressively before publication.

Operator Action

• If you run CervoMutants in CI, prefer the first-party GitHub Action and
  review docs/github-action.md plus
  docs/go-toolchain-compatibility.md before widening the lane.
• If your workflow reads survivor output or reports, review the new
  actionable-only and semantic-triage surfaces. The raw report model stays
  additive, but teams should re-baseline any local expectations that were based
  only on pre-triage survivor ordering.
• If you previously treated daemon/worker as an implied future distribution
  contract, narrow that expectation now. The public docs treat it as
  experimental until a versioned protocol exists.
• Before promoting this release broadly, run a bounded lane and confirm that
  your install path, report readers, and baseline posture still match the
  documented workflow.

Rollback

• Reinstall v0.3.0 if the new review surfaces, CI integration path, or
  compatibility expectations create rollout friction that needs to be backed
  out quickly.
• If rolling back, also restore the previous baseline or survivor-review
  expectations when they depended on pre-v0.4.0 ranking or governance shape.
• Keep the rollback within the same install family where possible:
  • go install github.com/cervantesh/cervo-mutants/cmd/cervomut@v0.3.0
  • reinstall the v0.3.0 GitHub release archive