Verification, Decisions, and CI Evidence

VibePro gates rely on current evidence. A test result is useful only when it is tied to the Story and the git state being prepared for review.

Record local verification

vibepro verify record . \
  --id <story-id> \
  --kind typecheck \
  --status pass \
  --command "npm run typecheck" \
  --summary "Checked CLI and src JavaScript syntax"

Use --artifact for reports, screenshots, logs, or TAP/JUnit files that reviewers should inspect.

Verify user flow

When a Story affects a user path, record a flow run:

vibepro journey derive .
vibepro verify flow . --base-url http://localhost:3000 --id <story-id> --journey <journey-id>

Use --allow-mutation only when the target environment is safe for write operations.

Import CI evidence

If CI already ran the relevant checks, import it rather than retyping the outcome:

vibepro verify import-ci . --id <story-id> --pr <number> --check "typecheck=typecheck"

CI evidence should still be reviewed for freshness. A green run from an old commit should not satisfy a current-head gate.

Record decisions and waivers

Use decision records for accepted risk, noise classifications, and exceptions:

vibepro decision record . \
  --id <story-id> \
  --type waiver \
  --source <gate-id> \
  --summary "<what is accepted>" \
  --reason "<why this is acceptable>"

vibepro decision status . --id <story-id>

Waivers are visible PR evidence. They should explain the risk in reviewer-readable language.