新增 release gate execution manifest API

wasm-port/docs/project-release-handoff.md

@@ -19,8 +19,8 @@ Use these documents as the current handoff set:
   reuse and non-drift rules.
 - `../PROJECT_COMPLETION_TRACKER.md` for project-level acceptance tracking.
 
-Old turn logs `text1.txt` through `text13.txt` are historical context. Current
-continuation records are in `../text14.txt`.
+Old turn logs `text1.txt` through `text14.txt` are historical context. Current
+continuation records are in `../text15.txt`.
 
 ## Supported current workflows
 
@@ -39,10 +39,13 @@ continuation records are in `../text14.txt`.
   expected smoke outputs, `createProjectReleaseGateResultMatrix()` to map
   observed outputs onto passed/unknown gate rows,
   `createProjectReleaseGateActionPlan()` to derive pending gate commands, the
-  next command, display rows, and a shell script from that matrix, and
+  next command, display rows, and a shell script from that matrix,
+  `createProjectReleaseGateExecutionManifest()` to package each gate command,
+  expected output, observed-output evidence, and passed/unknown status, and
   `createProjectReleaseReadinessReport()` for a machine-readable release
-  readiness report covering the same manifest, result matrix, action plan,
-  sim-config inventory baseline, and blocked runtime families.
+  readiness report covering the same manifest, execution manifest, result
+  matrix, action plan, sim-config inventory baseline, and blocked runtime
+  families.
   `createProjectReleaseReadinessSummaryViewModel()` turns that report into
   stable status text and rows for dashboards. The report helper is evidence
   driven and only reports `ready: true` when the caller supplies release gate
@@ -52,8 +55,9 @@ continuation records are in `../text14.txt`.
   External tools can load that artifact with
   `parseProjectReleaseReadinessArtifactJson()` and validate it with
   `createProjectReleaseReadinessArtifactValidation()`. Artifact validation
-  requires the embedded gate manifest, result matrix, and action plan to be
-  ready, so stale release JSON cannot pass the executable artifact gate.
+  requires the embedded gate manifest, execution manifest, result matrix, and
+  action plan to be ready, so stale release JSON cannot pass the executable
+  artifact gate.
   `createProjectReleaseReadinessArtifactValidationSummaryViewModel()` turns the
   validation into stable dashboard rows without reinterpreting artifact fields.
   `createProjectReleaseReadinessArtifactValidationActionPlan()` turns a blocked