API Drift and Contract Validation
How endpoint inventory, OpenAPI, and documentation stay aligned.
Compare the immutable RC, current source snapshot, route inventory, and sanitized artifact before release.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The Phase 6 audit uses TypeScript decorator extraction for 59 controller classes and 403 methods, compares current main with the RC, and validates that the sanitized artifact does not expose excluded visibility classes or private values.
| Check | Source-backed expectation |
|---|---|
| Scope | A zero-drift result applies to the audited revisions; it does not waive future source review. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm validate:api |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
pnpm validate:api
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.