[CI] [HOOK-REGRESSION] step6_bundling_bypass has severity='high' — not in allowed set, breaks TestBypassPatternsConfig

[akaszubski]

Problem

plugins/autonomous-dev/config/known_bypass_patterns.json pattern step6_bundling_bypass (issue #973) has \"severity\": \"high\" but the test schema in TestBypassPatternsConfig::test_all_patterns_have_required_fields only allows ('critical', 'warning', 'info'). This causes 1 failing test:

FAILED tests/unit/hooks/test_session_activity_pipeline_actions.py::TestBypassPatternsConfig::test_all_patterns_have_required_fields
AssertionError: Invalid severity 'high' for step6_bundling_bypass
assert 'high' in ('critical', 'warning', 'info')

The installed config (.claude/config/known_bypass_patterns.json) does NOT have this entry (it was never deployed), so enforcement is not affected — but the source config diverged from the schema and the test catches it.

Evidence

• Failing test: tests/unit/hooks/test_session_activity_pipeline_actions.py::TestBypassPatternsConfig::test_all_patterns_have_required_fields
• Pattern file: plugins/autonomous-dev/config/known_bypass_patterns.json line 374
• Observed during post-pipeline analysis of Issue [CI] Multi-validator finding diversity is a quality signal worth measuring — add to CIA report #991 (2026-05-24)

Suggested Fix

Change "severity": "high" → "severity": "critical" for step6_bundling_bypass in plugins/autonomous-dev/config/known_bypass_patterns.json. The pattern represents an active bypass of STEP 6 acceptance tests — critical is the correct tier. Then re-deploy to .claude/config/ via bash scripts/deploy-all.sh.

Repo: autonomous-dev
Session: 2026-05-24T01:17:32

Plugin Version: 3.50.0 (fcfec4b)

---

Filed automatically by continuous-improvement-analyst