新增发布 readiness artifact SDK 校验 workflow
This commit is contained in:
@@ -41,7 +41,9 @@ continuation records are in `../text14.txt`.
|
||||
evidence driven and only reports `ready: true` when the caller supplies
|
||||
release gate evidence such as `project_release_gate=ok`. The project release
|
||||
gate writes the same report to `build/project-release-readiness.json` and
|
||||
validates it with `verify_project_release_readiness_artifact.sh`.
|
||||
validates it with `verify_project_release_readiness_artifact.sh`. External
|
||||
tools can load that artifact with `parseProjectReleaseReadinessArtifactJson()`
|
||||
and validate it with `createProjectReleaseReadinessArtifactValidation()`.
|
||||
- OPFS/session callers can use `createMachineSessionPersistenceSummary()` or
|
||||
`linuxCncIniPanelApi.getMachineSessionPersistenceSummary()` to inspect
|
||||
machine files, session snapshot, session readiness, session load, readonly
|
||||
|
||||
Reference in New Issue
Block a user