# E2E Verification Report

## Scope

- Workflow / plan:
- User authorization and permitted side effects:
- Target build / ref:
- Actual environment / device / session:
- Assigned scenario IDs:

## Results

| Scenario | Expected | Actual | Outcome | Evidence |
|---|---|---|---|---|

Outcome is exactly `passed`, `failed`, `not-run`, or `blocked`. For a blocked/not-run scenario, state the missing prerequisite instead of a pass claim.

## Evidence

Record actual commands/actions and observed output or artifact links with build/environment identity. Distinguish new evidence from reused evidence and explain its applicability. Do not record secrets.

## Findings and handoff

For each failure: scoped impact, reproduction, evidence, proposed repair owner and bounded follow-up. Retest only the authorized scenarios after a fix. No automatic mutation or reopening of another workflow.

## Not verified

List excluded scenarios, unavailable capabilities, and any evidence limitations.

## Completion recommendation

State assigned/completed/blocked scenario counts and pending actions. Recommend the independent run's lifecycle outcome to PM separately from the product pass/fail result. PM alone marks the plan Done and closes the workflow; ops reports results.