vibepro-diagnosis-packageslisted

# VibePro Diagnosis Packages ## Purpose Use VibePro purpose-level packages instead of guessing which low-level scanner or log to inspect. The package is the user-facing intent; the scanner set and evidence paths are VibePro's implementation detail. ## Diagnosis Packages List packages first when the request is ambiguous: ```bash vibepro check list ``` Use these mappings: - UI quality / user flow / API contract in UI calls / gesture UX: `vibepro check ui <repo> --story-id <story-id>` - Security / auth / exposed surface / API route contracts: `vibepro check security <repo> --story-id <story-id>` - Performance readiness / heavy dev / DB access risks: `vibepro check performance <repo> --story-id <story-id>` - Architecture / responsibility boundary: `vibepro check architecture <repo> --story-id <story-id>` - PR readiness: `vibepro check pr-readiness <repo> --story-id <story-id> --base <ref> --head <ref>` - Release or handoff readiness: `vibepro check launch-readiness <repo> --story-id <story-id>` - Broad inspection: `vibepro check all <repo> --story-id <story-id>` Package evidence is written to: ```text .vibepro/checks/<pack>/<run-id>/check.json .vibepro/checks/<pack>/<run-id>/check.md ``` ## Performance Evidence For a performance improvement claim, define Story-level metrics and record before/after runs. Do not rely only on ad hoc server logs or one-off E2E output. Define metrics: ```bash vibepro performance define <repo> \ --id <story-id> \ --metric-id <metric-id