h4tcher-capability-remove

To safely decommission pipeline modules and agents, you must pass a removal-threshold gate proving zero value-duplication, run preflight discovery to scrub cross-references, and enforce validation and inventory regeneration before committing.

The D16.3 removal-threshold gate is a safety check that blocks artifact decommissioning unless you prove zero value-duplication, minimal cross-references, and no orchestrator dependency, ensuring safe removal across code and docs.

To migrate CHANGELOG entries when removing rules, commands, and hooks, sub-agents draft migration notes and add a precise entry under an active release's "Removed" section to maintain full traceability during decommissioning.

Before approving the removal of adapters and rules, governance checks require full validation, test, typecheck, lint, build, inventory regeneration, and anti-slop and pillar compliance constraints to pass.

You cannot decommission artifacts with existing orchestrator dependencies or value duplication, as the D16.3 removal-threshold gate explicitly blocks removal under these conditions to maintain system integrity.

The best way to scrub canonical references during artifact decommissioning is an automated workflow that dispatches sub-agents to scrub across code and docs, enforcing a strict "no orphan hits" check before final approval.