Continuous Integration Workflow
What hosted CI validates before documentation or source release decisions.
Read the exact check result, not only the aggregate workflow status.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
CI validates content, links, SEO, public safety, installation/admin/integration/security claims, routes, assets, build, browser smoke, and accessibility. The canonical docs workflow runs these checks on the hosted branch and pull request.
| Check | Source-backed expectation |
|---|---|
| Scope | A skipped job must be explained; it is not an unqualified pass. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm validate |
| 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
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.