openxiangda 1.0.252 → 1.0.253

package/README.md

@@ -1,4 +1,4 @@
-<!-- OpenXiangda-Policy-Version: 6 -->
+<!-- OpenXiangda-Policy-Version: 7 -->
 # OpenXiangda
 
 OpenXiangda is a lightweight CLI and skill package for private low-code platforms.
@@ -38,7 +38,12 @@ path is used.
 `status` and `retry` locate the run across preproduction and production when
 `--environment` is omitted. Retry resumes only unfinished checkpoints, safely
 replays local Form bindings on another machine, and uses a server-side attempt
-fence so an older executor cannot continue writing after takeover.
+fence so an older executor cannot continue writing after takeover. Runtime
+build IDs include both the Runtime layer and sealed package digests, so a newly
+sealed package cannot collide with an older package that happens to contain the
+same Runtime bytes. An exact same-package retry may reuse an `uploaded` release
+only after verifying its content hash, source revision, and Runtime parent;
+immutable storage objects are never overwritten.
 
 The lower-level commands later in this README remain available for V1
 compatibility and diagnostics; do not use them to assemble a normal V2 release.

package/lib/cli.js

@@ -15674,7 +15674,13 @@ async function runtime(args) {
     const files = collectRuntimeDistFiles(distDir, {
       includeSourceMaps: Boolean(flags['include-sourcemaps']),
     });
+    const declaredReleaseFiles = runtimeReleaseFileDescriptors(files);
     const totalBytes = files.reduce((sum, file) => sum + file.size, 0);
+    const reusableRuntimeRelease = await telemetry.runPhase(
+      'reuse-check',
+      async () =>
+        findRuntimeReleaseByBuildId(config, target, buildId)
+    );
     printRuntimeProgress(
       `runtime release upload: mode=${effectiveUploadMode} traceId=${traceId} files=${files.length} size=${formatBytes(totalBytes)} timeout=${uploadTimeoutMs}ms`
     );
@@ -15682,6 +15688,20 @@ async function runtime(args) {
       'upload',
       { fileCount: files.length, totalBytes, mode: effectiveUploadMode },
       async () => {
+        if (reusableRuntimeRelease) {
+          assertRuntimeReleaseReusable(reusableRuntimeRelease, {
+            appType: target.appType,
+            buildId,
+            files: declaredReleaseFiles,
+            sourceRevision: runtimeLineage.sourceRevision,
+            parentReleaseId: runtimeLineage.parentReleaseId,
+          });
+          effectiveUploadMode = 'reuse-existing';
+          printRuntimeProgress(
+            `runtime immutable release reused: releaseId=${reusableRuntimeRelease.id} buildId=${buildId} traceId=${traceId}`
+          );
+          return declaredReleaseFiles;
+        }
         if (uploadMode === 'legacy-json') {
           effectiveUploadMode = 'legacy-json';
           return files.map(file => ({
@@ -15714,6 +15734,27 @@ async function runtime(args) {
             timeoutMs: uploadTimeoutMs,
           });
         } catch (error) {
+          if (isRuntimeBuildImmutableConflict(error)) {
+            const racedRuntimeRelease = await findRuntimeReleaseByBuildId(
+              config,
+              target,
+              buildId
+            );
+            if (racedRuntimeRelease) {
+              assertRuntimeReleaseReusable(racedRuntimeRelease, {
+                appType: target.appType,
+                buildId,
+                files: declaredReleaseFiles,
+                sourceRevision: runtimeLineage.sourceRevision,
+                parentReleaseId: runtimeLineage.parentReleaseId,
+              });
+              effectiveUploadMode = 'reuse-existing';
+              printRuntimeProgress(
+                `runtime immutable release won upload race and was reused: releaseId=${racedRuntimeRelease.id} buildId=${buildId} traceId=${traceId}`
+              );
+              return declaredReleaseFiles;
+            }
+          }
           if (uploadMode !== 'auto' || !isRuntimeStagedUploadBlocked(error)) {
             throw error;
           }
@@ -16076,6 +16117,134 @@ function collectRuntimeDistFiles(distDir, options = {}) {
   return files;
 }
 
+function runtimeReleaseFileDescriptors(files) {
+  return (files || []).map(file => ({
+    path: file.path,
+    size: file.size,
+    sha256: file.sha256,
+    contentType: file.contentType,
+  }));
+}
+
+function calculateRuntimeReleaseContentHash(files) {
+  const hash = crypto.createHash('sha256');
+  for (const file of files || []) {
+    const filePath = String(file?.path || '').trim();
+    const fileSha256 = String(file?.sha256 || '').trim().toLowerCase();
+    if (!filePath || !/^[a-f0-9]{64}$/.test(fileSha256)) {
+      throw runtimeReleaseReuseError(
+        'RUNTIME_RELEASE_REUSE_LOCAL_MANIFEST_INVALID',
+        `本地 Runtime 文件描述不完整: ${filePath || '(unknown)'}`,
+        { filePath: filePath || null }
+      );
+    }
+    hash.update(filePath);
+    hash.update(fileSha256);
+  }
+  return hash.digest('hex');
+}
+
+async function findRuntimeReleaseByBuildId(config, target, buildId) {
+  const appPath = `/openxiangda-api/v1/apps/${encodeURIComponent(target.appType)}/runtime/releases`;
+  try {
+    const exact = await requestWithAuth(
+      config,
+      target.profileName,
+      `${appPath}/by-build/${encodeURIComponent(buildId)}`
+    );
+    return exact?.id ? exact : null;
+  } catch (error) {
+    if (Number(error?.status) !== 404) throw error;
+  }
+  const releases = await requestWithAuth(
+    config,
+    target.profileName,
+    appPath
+  );
+  const items = Array.isArray(releases)
+    ? releases
+    : Array.isArray(releases?.items)
+      ? releases.items
+      : [];
+  return (
+    items.find(item => String(item?.buildId || '') === String(buildId)) ||
+    null
+  );
+}
+
+function assertRuntimeReleaseReusable(existing, expected) {
+  const context = {
+    appType: expected.appType,
+    buildId: expected.buildId,
+    existingReleaseId: existing?.id || null,
+  };
+  if (String(existing?.status || '') !== 'uploaded') {
+    throw runtimeReleaseReuseError(
+      'RUNTIME_RELEASE_REUSE_STATUS_INVALID',
+      `相同 buildId 的 Runtime Release 状态为 ${existing?.status || '(unknown)'}，仅 uploaded 状态可作为失败发布的暂存恢复点`,
+      { ...context, existingStatus: existing?.status || null }
+    );
+  }
+  const expectedContentHash = calculateRuntimeReleaseContentHash(
+    expected.files
+  );
+  if (
+    String(existing?.contentHash || '').trim().toLowerCase() !==
+    expectedContentHash
+  ) {
+    throw runtimeReleaseReuseError(
+      'RUNTIME_RELEASE_REUSE_CONTENT_MISMATCH',
+      '相同 buildId 的历史 Runtime Release 内容与当前密封包不一致，拒绝复用',
+      {
+        ...context,
+        expectedContentHash,
+        existingContentHash: existing?.contentHash || null,
+      }
+    );
+  }
+  if (
+    !runtimeSourceRevisionEquals(
+      existing?.sourceRevision,
+      expected.sourceRevision
+    )
+  ) {
+    throw runtimeReleaseReuseError(
+      'RUNTIME_RELEASE_REUSE_SOURCE_MISMATCH',
+      '相同 buildId 的历史 Runtime Release 源码血缘与当前密封包不一致，拒绝复用',
+      context
+    );
+  }
+  const existingParentReleaseId =
+    String(existing?.parentReleaseId || '').trim() || null;
+  const expectedParentReleaseId =
+    String(expected.parentReleaseId || '').trim() || null;
+  if (existingParentReleaseId !== expectedParentReleaseId) {
+    throw runtimeReleaseReuseError(
+      'RUNTIME_RELEASE_REUSE_PARENT_MISMATCH',
+      '相同 buildId 的历史 Runtime Release 父版本已与当前 Runtime head 不一致，拒绝复用',
+      {
+        ...context,
+        existingParentReleaseId,
+        expectedParentReleaseId,
+      }
+    );
+  }
+  return existing;
+}
+
+function runtimeSourceRevisionEquals(left, right) {
+  return ['repo', 'baseCommit', 'treeHash'].every(
+    key => String(left?.[key] || '').trim() === String(right?.[key] || '').trim()
+  );
+}
+
+function runtimeReleaseReuseError(code, message, data = {}) {
+  const error = new Error(`${code}: ${message}`);
+  error.code = code;
+  error.data = data;
+  return error;
+}
+
 function walkRuntimeDist(rootDir, currentDir, files, options) {
   const entries = fs.readdirSync(currentDir, { withFileTypes: true });
   for (const entry of entries) {
@@ -16311,6 +16480,16 @@ function isRuntimeStagedUploadBlocked(error) {
   return /^HTTP 403\b/.test(String(error?.message || ''));
 }
 
+function isRuntimeBuildImmutableConflict(error) {
+  return (
+    Number(error?.status) === 409 &&
+    (String(error?.code || '') === 'RUNTIME_BUILD_IMMUTABLE' ||
+      /Runtime buildId .*禁止覆盖|RUNTIME_BUILD_IMMUTABLE/.test(
+        String(error?.message || '')
+      ))
+  );
+}
+
 function normalizeRuntimeUploadTimeoutMs(value) {
   const candidate =
     value === undefined || value === null || value === ''
@@ -30664,12 +30843,14 @@ function buildWorkspacePublishEnv(
 }
 
 module.exports = {
+  assertRuntimeReleaseReusable,
   buildResourceManifestSddTargets,
   buildScopeGrantSourceSyncDecision,
   deploymentEvidencePendingError,
   deploymentQueueWaitDecision,
   inspectSucceededPreproductionDeployment,
   main,
+  calculateRuntimeReleaseContentHash,
   recoveredPreproductionShipPatch,
   resolveReleaseCommandScopedFiles,
   selectSucceededPreproductionDeployment,

package/lib/delivery-v2-executor.js

@@ -1096,7 +1096,7 @@ function decorateSteps(
         '--dist',
         path.join(executionRoot, 'dist'),
         '--build-id',
-        `pkg-${runtime.digest.slice(0, 20)}`,
+        deliveryV2RuntimeBuildId(runtime?.digest, run?.packageDigest),
         '--upload-mode',
         'staged'
       );
@@ -1129,6 +1129,30 @@ function decorateSteps(
   return result;
 }
 
+function deliveryV2RuntimeBuildId(runtimeDigest, packageDigest) {
+  const normalizedRuntimeDigest = String(runtimeDigest || '')
+    .trim()
+    .toLowerCase();
+  const normalizedPackageDigest = String(packageDigest || '')
+    .trim()
+    .toLowerCase();
+  if (!/^[a-f0-9]{64}$/.test(normalizedRuntimeDigest)) {
+    throw deliveryError(
+      'DELIVERY_RUNTIME_LAYER_DIGEST_INVALID',
+      'Runtime layer digest 必须是 64 位 SHA-256',
+      false
+    );
+  }
+  if (!/^[a-f0-9]{64}$/.test(normalizedPackageDigest)) {
+    throw deliveryError(
+      'DELIVERY_PACKAGE_DIGEST_INVALID',
+      'package digest 必须是 64 位 SHA-256',
+      false
+    );
+  }
+  return `pkg-${normalizedRuntimeDigest.slice(0, 20)}-${normalizedPackageDigest.slice(0, 12)}`;
+}
+
 function packageSummary(manifest, previousManifest) {
   return {
     sourceFileCount: layerByKind(manifest, 'source')?.fileCount || 0,
@@ -1668,6 +1692,7 @@ module.exports = {
   compactStepResult,
   createDeliveryV2Executor,
   decorateSteps,
+  deliveryV2RuntimeBuildId,
   normalizeLegacyPackageTargetsForExecution,
   packageWorkspaceRoot,
   prepareAppFinalizeStep,

package/lib/policy.js

@@ -60,10 +60,14 @@ function validateEngineeringPolicy(policy) {
     policy?.release?.deletionsFailClosed !== true ||
     policy?.release?.attemptFencing !== true ||
     policy?.release?.crossMachineBindingReplay !== true ||
+    policy?.release?.deterministicRuntimeBuildIdentity !==
+      'runtime-layer-plus-package-digest' ||
+    policy?.release?.deterministicRuntimeUploadedReleaseReuse !==
+      'exact-content-source-parent-only' ||
     policy?.release?.statusAutoResolvesEnvironment !== true
   ) {
     errors.push(
-      'Delivery V2 必须启用密封构建、精确差异、删除关闭、attempt 隔离、跨机器绑定恢复和环境自动解析'
+      'Delivery V2 必须启用密封构建、精确差异、删除关闭、attempt 隔离、跨机器绑定恢复、Runtime 包级身份与严格恢复，以及环境自动解析'
     );
   }
   const ttl = Number(policy?.ownership?.defaultTtlSeconds);

package/openxiangda-skills/SKILL.md

@@ -3,7 +3,7 @@ name: openxiangda
 description: "Use OpenXiangda for private low-code platform work: app workspaces, forms, pages, resources, functions, automations, workflows, permissions, publishing, deployment, diagnosis, profiles, and the openxiangda CLI."
 ---
 
-<!-- OpenXiangda-Policy-Version: 6 -->
+<!-- OpenXiangda-Policy-Version: 7 -->
 # OpenXiangda
 
 OpenXiangda connects an AI coding workspace to the private low-code platform through a normal-user profile and `/openxiangda-api/v1`. External backends using AK/SK are a separate `openxiangda-open-api` flow.
@@ -37,6 +37,10 @@ Keep the `runId`; failures preserve successful checkpoints. `status` and
 `retry` auto-locate preproduction or production when no environment is given.
 Retry fences the previous attempt and safely replays local Form bindings, so it
 can resume from another machine without recreating completed platform writes.
+Deterministic Runtime build IDs combine the Runtime layer and sealed package
+digests, preventing cross-package provenance collisions. An exact same-package
+retry reuses an existing `uploaded` release only after exact
+content/source/parent verification and never overwrites immutable storage.
 
 ## Keep the agent loop small
 

package/openxiangda-skills/skills/openxiangda-core/SKILL.md

@@ -30,7 +30,11 @@ unsupported and fail before remote writes. V2 executes authored builds with the
 CLI-sealed toolchain, never a workspace `node_modules` or custom builder.
 `status`/`retry` auto-resolve the run environment if omitted. Retry preserves
 completed checkpoints, fences the older attempt, and replays only local Form
-bindings when resuming on a different machine.
+bindings when resuming on a different machine. Deterministic Runtime build IDs
+combine the Runtime layer and sealed package digests, preventing provenance
+collisions across packages with identical Runtime bytes. An `uploaded` release
+is reused only for an exact same-package retry when its content hash, source
+revision, and parent Runtime release match; all other identities fail closed.
 
 ## Resolve the boundary
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openxiangda",
-  "version": "1.0.252",
+  "version": "1.0.253",
   "description": "OpenXiangda CLI, workspace build tools, runtime SDK, and form components.",
   "private": false,
   "bin": {

package/policy/openxiangda-policy.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": "openxiangda_engineering_policy_v1",
-  "policyVersion": 6,
+  "policyVersion": 7,
   "risk": {
     "levels": ["L0", "L1", "L2", "L3"],
     "quickMaxLevel": "L1",
@@ -39,6 +39,8 @@
     "deletionsFailClosed": true,
     "attemptFencing": true,
     "crossMachineBindingReplay": true,
+    "deterministicRuntimeBuildIdentity": "runtime-layer-plus-package-digest",
+    "deterministicRuntimeUploadedReleaseReuse": "exact-content-source-parent-only",
     "statusAutoResolvesEnvironment": true,
     "v2RequiresSdd": false,
     "v2RequiresGitMainline": false,

package/templates/openxiangda-react-spa/.cursor/rules/openxiangda.mdc

@@ -21,7 +21,7 @@ This is an OpenXiangda React SPA workspace using Delivery V2. See [DELIVERY.md](
 ## Always
 
 - Delivery V2 derives exact scope and does not require SDD, Git clean, `--change`, `--only`, candidate, or ship.
-- Treat `check --json` as the authoritative exact delta and execution plan. Deletions and unsealed third-party build dependencies fail before writes; package execution uses only the CLI toolchain and never links workspace `node_modules`. `status`/`retry` auto-locate the environment, while retry fences the old attempt and replays only cross-machine local Form bindings.
+- Treat `check --json` as the authoritative exact delta and execution plan. Deletions and unsealed third-party build dependencies fail before writes; package execution uses only the CLI toolchain and never links workspace `node_modules`. `status`/`retry` auto-locate the environment, while retry fences the old attempt and replays only cross-machine local Form bindings. Runtime build IDs combine the Runtime layer and sealed package digests; only an exact same-package `uploaded` release with matching content, source, and parent may be reused, and immutable storage is never overwritten.
 - Writes and deploys must pass `--profile <name>` explicitly.
 - Architecture-class work is plan-gated: run `openxiangda design gates --topic <code> --json` and wait for confirmation.
 - Give every task an isolated worktree/branch and one explicit development change; feature worktrees never publish. Merge approved commits to the remote default branch, create one `sdd bundle <release-change> --changes ...`, commit/push it, then publish once from the synchronized clean main/master checkout.

package/templates/openxiangda-react-spa/.qoder/rules/openxiangda.md

@@ -21,7 +21,7 @@ This is an OpenXiangda React SPA workspace using Delivery V2. Read [DELIVERY.md]
 ## Always
 
 - Delivery V2 自动计算精确范围，不要求 SDD、Git clean、`--change`、`--only` 或 candidate/ship。
-- `check --json` 是 V2 权威预检：确认精确资源差异和执行计划。删除与未密封第三方构建依赖在写入前失败；包执行只用 CLI 工具链且不链接工作区 `node_modules`。`status`/`retry` 自动定位环境，retry 以 attempt 隔离旧执行器并仅重放跨机器所需的本地 Form 绑定。
+- `check --json` 是 V2 权威预检：确认精确资源差异和执行计划。删除与未密封第三方构建依赖在写入前失败；包执行只用 CLI 工具链且不链接工作区 `node_modules`。`status`/`retry` 自动定位环境，retry 以 attempt 隔离旧执行器并仅重放跨机器所需的本地 Form 绑定。Runtime buildId 同时包含 Runtime layer 与密封包摘要；仅同包 `uploaded` Release 在内容、源码、父版本完全一致时复用，不覆盖不可变存储对象。
 - 发布和写平台资源必须显式传 `--profile <name>`。
 - 架构类需求先跑 `openxiangda design gates --topic <code> --json` 并等用户确认。
 - 每个任务使用独立 worktree/branch 和一个开发 change，但 feature worktree 不发布。批准提交先合并并 push 到远端默认主分支，再创建一个 `sdd bundle <release-change> --changes ...`，从同步且干净的 main/master 一次发布。

package/templates/openxiangda-react-spa/AGENTS.md

@@ -1,11 +1,11 @@
-<!-- OpenXiangda-Policy-Version: 6 -->
+<!-- OpenXiangda-Policy-Version: 7 -->
 # AGENTS.md — OpenXiangda React SPA 应用工作区
 
 本工作区是标准 React 18 + Vite + React Router 应用。默认模板只提供应用壳、账号菜单和一个首页，不是开发验证控制台。
 
 ## Delivery V2（发布唯一入口）
 
-本工作区声明 `deliveryVersion: 2`，正常发布只使用 `openxiangda check`、`openxiangda deploy`、`openxiangda status`、`openxiangda retry`、`openxiangda rollback`，完整约定见 [DELIVERY.md](DELIVERY.md)。V2 按资源指纹计算精确范围，使用不依赖工作区 `node_modules` 的 CLI 密封工具链，并在服务端持久化 ReleaseRun、attempt 和检查点；跨机器重试只重放本地 Form 绑定，删除和未密封构建依赖在写入前失败关闭。`status`/`retry` 未指定环境时会自动定位预发或生产。V2 不要求 SDD、Git clean、主线 ancestry、`--change`、`--only` 或生产确认参数。本文后续出现的 `resource publish`、`runtime deploy`、`release publish/ship`、candidate、SDD/mainline 发布门禁均为 V1 底层兼容说明，不得用于 V2 正常发布。
+本工作区声明 `deliveryVersion: 2`，正常发布只使用 `openxiangda check`、`openxiangda deploy`、`openxiangda status`、`openxiangda retry`、`openxiangda rollback`，完整约定见 [DELIVERY.md](DELIVERY.md)。V2 按资源指纹计算精确范围，使用不依赖工作区 `node_modules` 的 CLI 密封工具链，并在服务端持久化 ReleaseRun、attempt 和检查点；跨机器重试只重放本地 Form 绑定。Runtime buildId 同时包含 Runtime layer 与密封包摘要，避免相同 Runtime 字节在不同包之间发生来源碰撞；同包重试仅在历史 Release 为 `uploaded` 且内容、源码、父版本完全一致时复用，不覆盖不可变存储对象。删除和未密封构建依赖在写入前失败关闭。`status`/`retry` 未指定环境时会自动定位预发或生产。V2 不要求 SDD、Git clean、主线 ancestry、`--change`、`--only` 或生产确认参数。本文后续出现的 `resource publish`、`runtime deploy`、`release publish/ship`、candidate、SDD/mainline 发布门禁均为 V1 底层兼容说明，不得用于 V2 正常发布。
 
 ## 开发原则
 

package/templates/openxiangda-react-spa/DELIVERY.md

@@ -30,7 +30,11 @@ Rules:
   dependencies fail preflight.
 - On failure, keep the `runId`. `status` and `retry` auto-locate its environment
   when omitted. Retry preserves successful checkpoints, fences the previous
-  attempt, and safely replays local Form bindings on another machine.
+  attempt, and safely replays local Form bindings on another machine. Runtime
+  build IDs include the Runtime layer and sealed package digests, preventing
+  cross-package provenance collisions. A same-package retry reuses an existing
+  Runtime release only in `uploaded` state after exact content, source, and
+  parent verification; storage is never overwritten.
 - Project `.env`, credentials, private keys, `.git`, `node_modules`, `dist`,
   and generated `.openxiangda` state are never included in the authored source
   layer. Runtime output is a separate immutable layer.

package/templates/sy-lowcode-app-workspace/.cursor/rules/openxiangda.mdc

@@ -27,7 +27,7 @@ This is a `sy-lowcode-app-workspace` managed by the `openxiangda` CLI. See [AGEN
 
 ## Always
 
-- For `deliveryVersion: 2`, use only Delivery V2 commands. Later V1 SDD/mainline/`--only`/candidate/ship text is compatibility guidance and must not be mixed into V2.
+- For `deliveryVersion: 2`, use only Delivery V2 commands. Runtime build IDs combine the Runtime layer and sealed package digests; retry may reuse only an exact same-package `uploaded` release whose content, source, and parent match. Immutable storage is never overwritten. Later V1 SDD/mainline/`--only`/candidate/ship text is compatibility guidance and must not be mixed into V2.
 - Treat V2 `check --json` as the authoritative exact delta and execution plan. Deletions and unsealed third-party build dependencies fail before writes; package execution uses only the CLI toolchain and never links workspace `node_modules`. `status`/`retry` auto-locate the environment, while retry fences the old attempt and replays only cross-machine local Form bindings.
 - Give every task an isolated worktree/branch and one development change; feature worktrees never publish. Merge approved commits to the remote default branch, create one `sdd bundle`, commit/push it, and publish once from synchronized clean main/master.
 - Close tasks from canonical main only. Review `openxiangda workspace cleanup`, then run `openxiangda workspace cleanup --apply` for that exact hashed `SAFE` plan; it revalidates managed worktrees under the owner lock, never picks up newly-safe entries, and never runs global `git worktree prune`. Review stale records separately.

package/templates/sy-lowcode-app-workspace/.qoder/rules/openxiangda.md

@@ -27,7 +27,7 @@ This is a `sy-lowcode-app-workspace` managed by the `openxiangda` CLI. Read [AGE
 
 ## Always
 
-- `deliveryVersion: 2` 的正常发布只允许 Delivery V2 命令；后续 V1 SDD/mainline/`--only`/candidate/ship 内容仅作兼容说明，不得混入 V2。
+- `deliveryVersion: 2` 的正常发布只允许 Delivery V2 命令；Runtime buildId 同时包含 Runtime layer 与密封包摘要，仅同包 `uploaded` Release 在内容、源码、父版本完全一致时复用，不覆盖不可变存储对象；后续 V1 SDD/mainline/`--only`/candidate/ship 内容仅作兼容说明，不得混入 V2。
 - V2 `check --json` 是权威预检：确认精确资源差异和执行计划。删除与未密封第三方构建依赖在写入前失败；包执行只用 CLI 工具链且不链接工作区 `node_modules`。`status`/`retry` 自动定位环境，retry 以 attempt 隔离旧执行器并仅重放跨机器所需的本地 Form 绑定。
 - 每个任务使用独立 worktree/branch 和一个开发 change，但 feature worktree 不发布。批准提交先合并并 push 到远端默认主分支，再创建一个 `sdd bundle`，从同步且干净的 main/master 一次发布。
 - 合并、push、发布和 `release end` 后，回到 canonical 主工作区先审阅 `openxiangda workspace cleanup`，再执行 `openxiangda workspace cleanup --apply` 应用精确哈希计划。CLI 在 owner lock 内复核，只删除已审阅的 managed `SAFE` 项，不顺带处理后来才安全的项，也不执行全局 `git worktree prune`；stale 记录单独人工审阅。

package/templates/sy-lowcode-app-workspace/AGENTS.md

@@ -1,4 +1,4 @@
-<!-- OpenXiangda-Policy-Version: 6 -->
+<!-- OpenXiangda-Policy-Version: 7 -->
 # AGENTS.md — OpenXiangda 工作区 AI 强约束
 
 > 任何 AI（Qoder / Claude / Codex / Cursor / Copilot 等）在本工作区操作前 **必须先读完本文件**。
@@ -8,7 +8,7 @@
 
 **本工作区声明 `deliveryVersion: 2`。所有“发布 / 上线 / 部署 / publish / deploy / ship / release”请求只使用 `openxiangda check`、`openxiangda deploy`、`openxiangda status`、`openxiangda retry`、`openxiangda rollback`，完整约定见 [DELIVERY.md](DELIVERY.md)。**
 
-Delivery V2 自动从期望状态按资源指纹计算精确范围，使用 CLI 密封工具链封存内容寻址 App Package，并在服务端持久化 ReleaseRun、attempt 和检查点；包执行不链接工作区 `node_modules`。`status`/`retry` 可自动定位预发或生产环境，跨机器重试只重放本地 Form 绑定并跳过已完成的平台写入。删除和未密封的第三方构建依赖会在远程写入前失败关闭。它不要求 SDD、Git clean、主线 ancestry、`--change`、`--only` 或生产确认参数。本文后续出现的 `workspace publish`、`resource publish`、`runtime deploy`、`release publish/ship`、candidate、SDD/mainline 发布门禁均属于 V1 底层兼容说明，不得用于 V2 正常发布。
+Delivery V2 自动从期望状态按资源指纹计算精确范围，使用 CLI 密封工具链封存内容寻址 App Package，并在服务端持久化 ReleaseRun、attempt 和检查点；包执行不链接工作区 `node_modules`。`status`/`retry` 可自动定位预发或生产环境，跨机器重试只重放本地 Form 绑定并跳过已完成的平台写入。Runtime buildId 同时包含 Runtime layer 与密封包摘要，避免相同 Runtime 字节在不同包之间发生来源碰撞；同包重试仅在历史 Release 为 `uploaded` 且内容、源码、父版本完全一致时复用，绝不覆盖不可变存储对象。删除和未密封的第三方构建依赖会在远程写入前失败关闭。它不要求 SDD、Git clean、主线 ancestry、`--change`、`--only` 或生产确认参数。本文后续出现的 `workspace publish`、`resource publish`、`runtime deploy`、`release publish/ship`、candidate、SDD/mainline 发布门禁均属于 V1 底层兼容说明，不得用于 V2 正常发布。
 
 **架构类需求先过设计门。** 新应用、复杂页面、登录注册、公开访问、权限数据范围、流程自动化、连接器/通知等需求，先 `openxiangda doctor --json` + `openxiangda design gates --topic <code> --json`。只有仍存在会改变实现方向的业务、安全或数据选择时才输出设计并等待确认；用户已经给出具体需求与验收标准时，直接记录结构化 SDD 范围并实现，不再写长篇设计或重复确认。
 

package/templates/sy-lowcode-app-workspace/DELIVERY.md

@@ -30,7 +30,11 @@ Rules:
   dependencies fail preflight.
 - On failure, keep the `runId`. `status` and `retry` auto-locate its environment
   when omitted. Retry preserves successful checkpoints, fences the previous
-  attempt, and safely replays local Form bindings on another machine.
+  attempt, and safely replays local Form bindings on another machine. Runtime
+  build IDs include the Runtime layer and sealed package digests, preventing
+  cross-package provenance collisions. A same-package retry reuses an existing
+  Runtime release only in `uploaded` state after exact content, source, and
+  parent verification; storage is never overwritten.
 - Project `.env`, credentials, private keys, `.git`, `node_modules`, `dist`,
   and generated `.openxiangda` state are never included in the authored source
   layer. Runtime output is a separate immutable layer.