What problem does it solve? Whole-plugin properties like consistency, coherence, and completeness cannot be verified by a test suite, so a plugin can pass every test while its files contradict each other or its ruleset silently drifts from what it ships. This Skill performs the final static audit of the Senzing Bootcamp plugin before a live dry-run, checking the plugin against its INVARIANTS.md ruleset in both directions. ## Core Features & Use Cases - Bidirectional invariant audit: Verifies every invariant is honored at every site it binds (forward), and that every durable rule the plugin states is registered as an invariant (reverse). - Lead-generating scans: Ships a stdlib-only Python tool (conformance.py) with views for hard rules, per-rule citations, rules added since the last audit, enumerations, duplication, and file size. - Structured defect handling: Records findings as GitHub issues or ledger entries, fixes defect classes rather than instances, and requires negative-controlled regression tests. - Use Case: Before shipping a new version of the plugin, a maintainer runs this audit to catch contradictions between sibling skill files, stale enumerations in invariants, and hard rules that shipped with no governing invariant. ## Quick Start Ask the assistant to run the production-readiness audit on the Senzing Bootcamp plugin and report findings by severity.