diff --git a/.changes/harness-config/feat-15711-rule-to-enforcer-inventory-e006297b.md b/.changes/harness-config/feat-15711-rule-to-enforcer-inventory-e006297b.md deleted file mode 100644 index d12306557bf..00000000000 --- a/.changes/harness-config/feat-15711-rule-to-enforcer-inventory-e006297b.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -bump: minor ---- - -### Added - -- **Ladder spread in `/harness-config:audit-automation-gaps`.** Present Results prints, read-only - and with no target, how many of the repository's rules sit on each of the enforcement ladder's - five tiers, and the guidance rules that forbid a literal a pattern check could match ("sits lower - than it could", candidates for a person to judge). Both are rollups of one rule-to-enforcer - inventory that `scripts/rule-inventory.sh` generates, one row per rule (rule, enforcer, rung, - tier), from the repository's settings, ecosystem records, test files, control skills and - instruction files. Rung ids and tiers come from the ladder copy the skill carries. A source the - script cannot find or read is named, never counted as zero, and so is each source present but not - counted: CI workflows, git hook managers, local settings and enabled plugins' hooks. -- **`rule_inventory.declared` in `harness-config.yaml`.** Rows for rules no file shows, such as a - type that makes the mistake impossible; the schema describes the key. The file is read from the - convention home, or `docs/conventions` when the repository has no pointer region; a declined home - or one that does not resolve gives no declared rows and is named with the reason. diff --git a/plugins/harness-config/.claude-plugin/plugin.json b/plugins/harness-config/.claude-plugin/plugin.json index 9341f0e0681..e28dab84ef4 100644 --- a/plugins/harness-config/.claude-plugin/plugin.json +++ b/plugins/harness-config/.claude-plugin/plugin.json @@ -5,7 +5,7 @@ "name": "Melodic Software", "email": "info@melodicsoftware.com" }, - "version": "5.0.10", + "version": "5.1.0", "license": "MIT", "userConfig": { "time_units": { diff --git a/plugins/harness-config/CHANGELOG.md b/plugins/harness-config/CHANGELOG.md index 32bc6ed6a26..88504c50dfd 100644 --- a/plugins/harness-config/CHANGELOG.md +++ b/plugins/harness-config/CHANGELOG.md @@ -5,6 +5,24 @@ All notable changes to the `harness-config` plugin are documented here. Format f Versions 0.51.8 to 0.51.9 and 0.51.11 to 0.51.14 were reserved by parallel branches and never released. +## [5.1.0] - 2026-11-16 + +### Added + +- **Ladder spread in `/harness-config:audit-automation-gaps`.** Present Results prints, read-only + and with no target, how many of the repository's rules sit on each of the enforcement ladder's + five tiers, and the guidance rules that forbid a literal a pattern check could match ("sits lower + than it could", candidates for a person to judge). Both are rollups of one rule-to-enforcer + inventory that `scripts/rule-inventory.sh` generates, one row per rule (rule, enforcer, rung, + tier), from the repository's settings, ecosystem records, test files, control skills and + instruction files. Rung ids and tiers come from the ladder copy the skill carries. A source the + script cannot find or read is named, never counted as zero, and so is each source present but not + counted: CI workflows, git hook managers, local settings and enabled plugins' hooks. +- **`rule_inventory.declared` in `harness-config.yaml`.** Rows for rules no file shows, such as a + type that makes the mistake impossible; the schema describes the key. The file is read from the + convention home, or `docs/conventions` when the repository has no pointer region; a declined home + or one that does not resolve gives no declared rows and is named with the reason. + ## [5.0.10] - 2026-11-16 ### Changed