Implement the 031-quality-gates-hygiene feature that strengthens automated quality gates by adding pnpm audit to the check script, v8 coverage thresholds with per-directory auto-ratchet (domain 96%, adapters 71%, persistence 87%), Biome cognitive complexity enforcement (max 15), and keyboard accessibility for the combatant row, while cleaning up all blanket biome-ignore comments, refactoring 5 overly complex functions into smaller helpers, and codifying the early-enforcement principle in the constitution and CLAUDE.md

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.specify/memory/constitution.md

@@ -108,6 +108,9 @@ architecture, and quality — not product behavior.
   practical.
 - Layer boundary compliance MUST be verified by automated import
   rules or architectural tests.
+- All automated quality gates MUST run at the earliest feasible
+  enforcement point (currently pre-commit via Lefthook). No gate
+  may exist only as a CI step or manual process.
 - When a feature adds, removes, or changes user-facing capabilities
   described in README.md, the README MUST be updated in the same
   change. Features that materially alter what the product does or
@@ -138,4 +141,4 @@ MUST comply with its principles.
 **Compliance review**: Every spec and plan MUST include a
 Constitution Check section validating adherence to all principles.
 
-**Version**: 2.2.0 | **Ratified**: 2026-03-03 | **Last Amended**: 2026-03-10
+**Version**: 2.2.1 | **Ratified**: 2026-03-03 | **Last Amended**: 2026-03-11