Approval / escalation boundary violation
Auto-closing urgent cases violates the approval/escalation boundary. The source packet requires urgent, safety, harm, repeated-unresolved, or escalation cases to go through human review or escalation.
src/triage.js
Restricted case-history leakage
Restricted case-history details are exposed in user-facing output, and the response implies a hidden record exists. The source packet forbids exposing restricted related-case details to public users.
src/caseHistory.js
Weak inference routing
Weak keyword inference routes cases without a clarification or review step, and reports high confidence regardless of match strength. The source packet requires weak or ambiguous classifications to ask for clarification or route for review.
src/routing.js
Missing confirmation before submission
AI-generated summaries are marked ready to submit without user confirmation, even after material restructuring. The source packet requires user review or confirmation before submission.
src/summary.js
Missing behavior-boundary tests
Tests miss critical behavior-boundary coverage. The suite covers happy paths only and does not test the urgent-approval boundary, restricted-case leakage, weak-inference routing, or confirmation-before-submission boundary.
tests/