rule-trace v1.4.0

Changed

• Cursor .mdc generated importers now use either global alwaysApply: true or glob-scoped alwaysApply: false; existing generated .mdc files preserve frontmatter on sync, so hand-edit the frontmatter or delete/recreate the file before running rule-trace sync.
• Report unwaivedMust / unwaivedMustGaps semantics now follow the strongest configured severity while preserving stable JSON field names.
• Aligned the two CI validate-job wiring snippets (templates/wiring/github-actions.yml, references/ci-wiring.md); documented that their differing install commands (vendored vs. published) are intentional, not drift.

rule-trace v1.3.0

Added

• Live trace coverage metrics, read-side event deduplication, report staleness detection, and release-readiness documentation.
• Structured fenced rule-trace JSON parsing with prose fallback for trace blocks.
• Generated importer support and the sync command for reference-blind tools such as Cursor and GitHub Copilot.
• report.mjs --now <ISO-8601 date> pins report time (staleness and generatedAt) for reproducible runs; the committed demo artifacts and their regeneration test use it so staleness no longer drifts with the wall clock.

rule-trace v1.2.0

Added

• Codex-backed evaluation support for running and grading rule-trace behavior against fixtures.

Changed

• Renamed the skill to rule-trace and updated README positioning and usage examples.

rule-trace v1.1.0

Added

• Catalog generator and turnkey init scaffolding for new rule-trace installations.
• Generic audit methodology in references/audit.md.
• One-command eval runner with documented trigger modes.
• Upstream test suite, GitHub Actions CI, and doc/script-integrity guards.

Fixed

• Scaffold, validate, and report regressions covered by tests.
• Trace-block parsing for multiline fields.
• CLI help rendering when template literals contain backticks.