mirrors/pikasTech-HWLAB
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test: guard artifact runtime readiness

Browse Source
This commit is contained in:
Code Queue Review
2026-05-23 02:31:56 +00:00
parent 0a7311c3c2
commit e3c2537091
7 changed files with 1192 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/deployment-publish.md
+22
View File
@@ -84,6 +84,28 @@ image, workload, and mirror-env fields are blocked before any DEV apply.
Reports under `reports/` are evidence snapshots only and cannot override this
desired-state contract.
## Latest-Main Artifact/Runtime Guard
Before any controlled DEV apply for latest `origin/main`, run the read-only
artifact/runtime guard:
```sh
node scripts/artifact-runtime-readiness-guard.mjs --target-ref origin/main --check --no-report
```
When current readiness is expected to be blocked, use:
```sh
node scripts/artifact-runtime-readiness-guard.mjs --target-ref origin/main --check --no-report --expect-blocked
```
The guard compares target main, `reports/dev-gate/dev-artifacts.json`,
`deploy/artifact-catalog.dev.json`, the desired-state planner, Cloud API
`/health/live`, and Cloud Web `:16666/health/live`. It is report-only and must
not be used as an apply command. A local source check, static workbench smoke,
or stale report snapshot cannot claim latest-main deployment unless the guard's
runtime and artifact identity checks also pass.
## API, Edge, Health, And FRP
The public route is fixed: