Bug bounty validationRegression retestsAuth flow onboarding
Pick the workflow that matches the moment, not a generic automation bundle.
Guide each operator into the right starting point: validate a report, retest after release, or land a newcomer on the first safe workflow.
How to choose
Choose bug bounty triage
When the question is whether a reported issue still reproduces and how cleanly you can prove it.
Choose post-deploy checks
When a release just shipped and you need a narrow, evidence-backed regression sweep.
Choose the starter run
When the operator is new and the product needs to teach the first successful path.
Best for
Security teams replaying external reports
Bug bounty triage playbook
Validate incoming reports quickly with clean repro steps, role diffs, and evidence bundles.
Role-diff evidence
Repro transcript
Export bundle
Best for
Engineering and AppSec after releases
Post-deploy security regression checks
Run scoped checks after deploy events so auth and routing regressions are caught early.
Regression summary
Artifact timeline
Fast retest path
Best for
Teams onboarding a new operator
Auth flow starter run
Guide a newcomer from runner install and scope definition into the first successful auth workflow.
Runner status
Scope checklist
Starter report
Newcomer default
If the user is new, the right use case is the one that gets them to a safe first win.
That means install runner, define scope, launch a guided auth or smoke workflow, and show the evidence that came back. The first run should earn trust immediately.
1Install local runner
2Create project and scope
3Launch starter workflow