Keep ambiguous Issue titles out of Added and Changed

Merged
UN
3mo ago
+230-41

Summary

  • let bug-like item types outrank title-only add, new, update, and change tokens
  • preserve explicit feature, refactor, removal, and security type/tag signals
  • adopt pm-cli 2026.8.11 for current item-hash verification and a fail-closed exact legacy-provenance baseline
  • refresh the v2 merge fence, distribution artifacts, regressions, and generator-owned changelog
  • record GitHub issue #120 as a separate tag-date fallback item without claiming it here

PM items

Verification

  • npm run release:check
  • 372 tests passed; source coverage 100/100/100
  • 136 declarations documented; production audit 0 vulnerabilities
  • dry-run package tarball valid
  • current pm-cli history verification: 133 items, zero drift
  • managed v2 merge attributes verified

Issue #120 remains open and is intentionally not closed by this PR.

Summary by Sourcery

Clarify changelog classification of ambiguous Issues while adopting the latest pm-cli verifier and updating supporting metadata.

Bug Fixes:

  • Ensure Issues with command-like or Added/Changed-style titles still classify as Fixed by default.
  • Correct a misclassified changelog entry so feature flags are recorded under Fixed instead of Added.

Enhancements:

  • Refine classifier heuristics so Added signals rely on explicit types/tags, with title-only Added/Changed keywords handled after bug-like types.
  • Update Unreleased changelog entries to reflect the classifier fix and current history verification.

Build:

  • Upgrade pm-cli dev dependency to version 2026.8.11.

CI:

  • Replace the simple strict-exit health check with a JSON-based pm health gate that fails on any non-advisory warning and pins the expected legacy provenance warning set.

Tests:

  • Expand generator tests to cover a broader set of ambiguous Issue titles and assert their placement within the Fixed section.

Chores:

  • Add new pm agent history, issue, task, and chore records for classifier recurrence, pm-cli verifier adoption, and tag-aware fallback dates.