Quick answer: A successful scan proves the document was rebuilt from routes the scan could resolve, and nothing more. It does not prove the implementation conforms to the spec, behaves correctly at runtime, or is free of defects. Treat unresolved findings as unknown rather than inferred facts, and verify runtime behavior separately through tests and scenario runs. The scan does not run the app.
What the scan actually establishes
The output of a scan is a validated OpenAPI 3.2 document with routes proven through framework tracing and AST analysis, and contracts classified by the completeness gate. That is a real result, but it is a statement about the document and its provenance, not a statement about runtime behavior.
Confusing the two leads to over-trust. A route that was detected and emitted is a route the code mounts, not a behavior that was verified.
Consider a handler that returns 200 on the happy path but throws on an input the scanner never exercises.…