v2.32.0

What's new

Features

Config validation now handles the full lifecycle of bundled skill and agent names — including names that have been removed in past releases. Previously, listing a no-longer-bundled name in disabled_skills or disabled_agents would fail validation and prevent plugin load, effectively bricking setups that had disabled something Systematic later cleaned up.

v2.32.0 introduces a removed-names mechanism with three coordinated layers:

• Schema acceptance: The JSON Schema generator now includes the removed-names list in the enum for disabled_skills and disabled_agents, so editors and runtime stay in sync. While the list ships empty today, the schema will reflect any future additions without requiring editor configuration updates.
• Validation acceptance: Removed names are accepted during config validation alongside current bundled names, maintaining the strict rejection of genuinely-unknown names.
• Load-time cleanup: After validation, removed names are silently dropped from the effective disabled lists and a per-load [systematic] warning identifies each stale entry. Raw config is preserved for merge precedence; the dedup is stateless per load.

A content-integrity gate enforces that removed names never overlap current bundled names, preventing accidental misclassification as a name moves from active to removed.

Also in this release

• deps: Synced biome.json $schema to 2.4.16 to match the pinned @biomejs/biome CLI version — a mismatch caused the newer CLI to treat it as a config deserialize error and fail local lint.
• deps: Renovate non-major dependency updates to v4.16.26.
• deps: Updated fro-bot/agent to v0.64.1.

Compare

v2.31.1...v2.32.0