新增发布 readiness artifact SDK 校验 workflow
This commit is contained in:
@@ -47,6 +47,7 @@ import {
|
||||
createMachineSessionPersistenceRenderState,
|
||||
createMachineSessionPersistenceSummary,
|
||||
createMachineSessionSnapshotPayload,
|
||||
createProjectReleaseReadinessArtifactValidation,
|
||||
createProjectReleaseReadinessReport,
|
||||
createSessionSnapshot,
|
||||
defaultMachinePaths,
|
||||
@@ -69,6 +70,7 @@ import {
|
||||
mountIniPanelShellWorkflowOverviewEmbeddingMountState,
|
||||
normalizeOpfsPath,
|
||||
parameterFilePath,
|
||||
parseProjectReleaseReadinessArtifactJson,
|
||||
planIniFileContextStaging,
|
||||
planSimConfigStaging,
|
||||
readMachineSessionReadiness,
|
||||
@@ -194,7 +196,10 @@ and `../PROJECT_COMPLETION_TRACKER.md`.
|
||||
The executable release gate uses the same helper to write
|
||||
`build/project-release-readiness.json` after all project checks pass, then
|
||||
validates that artifact with
|
||||
`tests/host/verify_project_release_readiness_artifact.sh`.
|
||||
`tests/host/verify_project_release_readiness_artifact.sh`. External tools can
|
||||
load that JSON with `parseProjectReleaseReadinessArtifactJson()` and validate
|
||||
it with `createProjectReleaseReadinessArtifactValidation()` without copying the
|
||||
host test assertions.
|
||||
|
||||
## OPFS/session persistence exports
|
||||
|
||||
|
||||
Reference in New Issue
Block a user