openxiangda 1.0.188 → 1.0.190

package/lib/application-environments.js

@@ -363,6 +363,16 @@ function releaseExecutionPath(changeId, deploymentId, cwd = process.cwd()) {
 
 function withManagedReleaseForwardedFlags(stepId, args = [], flags = {}) {
   const forwarded = [...args];
+  const immutableResourceStages = new Set([
+    'backend-stage',
+    'workflow-stage',
+  ]);
+  if (
+    immutableResourceStages.has(stepId) &&
+    !forwarded.includes('--include-noop')
+  ) {
+    forwarded.push('--include-noop');
+  }
   const baselineAdoptionStages = new Set([
     'form-stage',
     'backend-stage',

package/lib/cli.js

@@ -11438,6 +11438,7 @@ async function resource(args) {
       '  - publish 默认跳过 plan 判定为 noop 的资源，避免无意义 upsert；需要强制写入时加 --force。',
       '  - Form settings bundle 默认只 stage，不推进线上 Form head；只有显式 --activate 才 CAS 激活。',
       '  - Function/Automation/Workflow 可用 --stage-only 只 prepare + verify immutable child；随后由 release app-finalize 一次原子激活。',
+      '  - --include-noop 仅可与 --stage-only 一起使用，用于受管候选为内容未变的目标生成带当前来源的不可变子版本。',
       '  - publish --dry-run 等价于发布前计划，不会写平台资源。',
       '  - 在线 publish 必须用 --only/--code 精确选择；真正全量发布必须显式 --all --reason，SDD bypass 不能绕过此范围门。',
       '  - 历史代码已先合入主线、线上又来自多次分批发布时，可显式使用 --adopt-online-baseline --adoption-reason "..."；仅允许绑定同一 change/lease 的精确非删除范围，仍保留 lease、冻结 head 检查与写入 CAS。',
@@ -11476,6 +11477,9 @@ async function resource(args) {
   const typeFilters = getResourceTypeFilters(positional, flags);
   const codeFilters = getResourceCodeFilters(flags);
   assertBackendStageOnlyScope(subcommand, flags, typeFilters);
+  if (flags['include-noop'] && !flags['stage-only']) {
+    fail('--include-noop 仅允许与 --stage-only 一起使用');
+  }
   assertExplicitResourcePublishScope(subcommand, flags, codeFilters);
   assertExplicitManifestReplacement(flags);
   if (codeFilters && flags.prune) {
@@ -11644,7 +11648,7 @@ async function resource(args) {
       async () =>
         publishResourceManifest(config, target, manifest, {
           planActions: publishPlan.actions,
-          skipNoop: !Boolean(flags.force),
+          skipNoop: !Boolean(flags.force || flags['include-noop']),
           prune: Boolean(flags.prune),
           pruneCandidates,
           publishLeaseId: publishLease?.leaseId,

package/package.json

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

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

@@ -0,0 +1,24 @@
+---
+description: src/forms/** — Use openxiangda-form skill
+globs: src/forms/**/*
+alwaysApply: false
+---
+
+# OpenXiangda React SPA Form Files
+
+Editing `src/forms/<formCode>/`. Use the **`openxiangda-form`** skill.
+
+- Keep field/schema rules in `schema.ts` and presentation in `page.tsx`.
+- Prefer OpenXiangda platform fields, then `antd` / `antd-mobile`; do not use native inputs, hand-written uploaders, pickers, or user/department selectors.
+- Option fields require non-empty `options`; linked data uses `SelectField` with `optionSource.type: "linkedForm"`.
+- Top-level `schema.rules` is only for `FormEffect[]`; validation belongs to field `rules`.
+- Do not recreate platform system fields. Use `behavior: "HIDDEN"` + `valueSync` for derived or permission keys.
+
+Release with exact scope:
+
+```bash
+openxiangda resource plan form-setting --only <formCode> --profile <name>
+openxiangda resource publish form-setting --only <formCode> --change <change> --profile <name>
+```
+
+Managed production activation only occurs through candidate → preproduction deploy/test → promotion of the same candidate.

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

@@ -0,0 +1,25 @@
+---
+description: src/pages/** — Use openxiangda-page skill
+globs: src/pages/**/*
+alwaysApply: false
+---
+
+# OpenXiangda React SPA Page Files
+
+Editing `src/pages/`. Use the **`openxiangda-page`** skill.
+
+- Keep routes in `src/app/router.tsx` and navigation in `src/app/navigation.ts`.
+- Split complex pages into thin views, `domain/`, `shared/{services,hooks}/`, `components/`, and styles.
+- Use server pagination and structured `filterGroup`; never fetch an oversized page and filter in the browser.
+- Prefer OpenXiangda platform components for platform data fields and `antd` / `antd-mobile` for ordinary UI.
+- Do not use native form controls, hand-written pickers/uploaders, or frontend-only authorization.
+
+Build and stage:
+
+```bash
+pnpm typecheck
+pnpm build
+openxiangda runtime deploy --no-activate --change <change> --profile <name>
+```
+
+Managed production activation only occurs through candidate → preproduction deploy/test → promotion of the same candidate.

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

@@ -0,0 +1,26 @@
+---
+description: src/{workflows,automations,js-code-nodes,functions}/** — Use openxiangda-workflow-automation skill
+globs: src/{workflows,automations,js-code-nodes,functions}/**/*
+alwaysApply: false
+---
+
+# OpenXiangda React SPA Workflow / Automation / Function Files
+
+Use the **`openxiangda-workflow-automation`** skill for workflows, automations, JS_CODE, and App Functions.
+
+- Ordinary lifecycle state changes use a status field, domain state machine, and automation; create workflows only for real approval semantics.
+- Prefer App Functions for reusable backend logic. JS_CODE is for cross-form, batch, process, platform API, external HTTP, and complex orchestration.
+- Keep UI interactions, normal validation, and display logic in React.
+- Log important backend steps with `ctx.logger`; obtain third-party credentials only through declared `secretRefs`.
+- Never copy workflow, automation, or function IDs across profiles.
+
+Build and release with exact scope:
+
+```bash
+pnpm typecheck:js-code
+pnpm build-js-code --script <code>
+openxiangda resource plan <workflow|automation|function> --only <code> --profile <name>
+openxiangda resource publish <workflow|automation|function> --only <code> --change <change> --profile <name>
+```
+
+Managed production activation only occurs through candidate → preproduction deploy/test → promotion of the same candidate.

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

@@ -0,0 +1,37 @@
+---
+description: src/forms/** glob — 精准引导到 openxiangda-form skill
+glob: src/forms/**/*
+alwaysApply: false
+---
+
+# OpenXiangda React SPA Form Files
+
+You are editing files under `src/forms/<formCode>/`. Use the **`openxiangda-form`** skill.
+
+## Required structure
+
+```text
+src/forms/<formCode>/
+├── schema.ts   # defineFormSchema() default export
+└── page.tsx    # presentation only
+```
+
+## Common pitfalls
+
+- 平台字段组件优先于 `antd` / `antd-mobile` 包装和自定义业务组件。
+- `schema.ts` 定义字段、选项、规则与行为；`page.tsx` 只负责展示。
+- 禁止直接写原生 `<input>` / `<select>` / `<textarea>` / file input，禁止手写人员、部门、上传和 picker 组件。
+- 选项字段必须提供非空 `options`；跨表数据使用 `SelectField` + `optionSource.type: "linkedForm"`。
+- 顶层 `schema.rules` 只用于 `FormEffect[]`；字段校验放字段自己的 `rules`。
+- 平台系统字段由平台维护，不要重复创建。
+- 派生键和隐式权限键使用 `behavior: "HIDDEN"` + `valueSync`。
+
+## Release
+
+```bash
+openxiangda resource validate form-setting --only <formCode> --profile <name>
+openxiangda resource plan form-setting --only <formCode> --profile <name>
+openxiangda resource publish form-setting --only <formCode> --change <change> --profile <name>
+```
+
+正式环境托管发布仍必须走 candidate → preproduction deploy/test → 同 candidate promotion，禁止直接激活生产资源。

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

@@ -0,0 +1,29 @@
+---
+description: src/pages/** glob — 精准引导到 openxiangda-page skill
+glob: src/pages/**/*
+alwaysApply: false
+---
+
+# OpenXiangda React SPA Page Files
+
+You are editing files under `src/pages/`. Use the **`openxiangda-page`** skill.
+
+## Strong defaults
+
+- 路由集中维护在 `src/app/router.tsx`，应用导航维护在 `src/app/navigation.ts`。
+- 复杂页面拆分为薄视图、`domain/`、`shared/{services,hooks}/`、`components/` 和样式文件。
+- 默认使用原生 Tailwind utilities，不使用未配置的 shadcn token。
+- 列表必须服务端分页并使用结构化 `filterGroup`；禁止抓取超大页后在浏览器过滤。
+- 平台数据字段优先使用 OpenXiangda 平台组件；普通 UI 使用 `antd` / `antd-mobile`。
+- 禁止原生表单控件、手写 picker/uploader/人员部门选择器。
+- 后端权限、公开访问 grants 与 App Function 检查才是授权依据；前端只做展示保护。
+
+## Release
+
+```bash
+pnpm typecheck
+pnpm build
+openxiangda runtime deploy --no-activate --change <change> --profile <name>
+```
+
+Runtime 只暂存到候选发布；正式环境托管发布必须走 candidate → preproduction deploy/test → 同 candidate promotion。

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

@@ -0,0 +1,34 @@
+---
+description: src/{workflows,automations,js-code-nodes,functions}/** glob — 精准引导到 openxiangda-workflow-automation skill
+glob: src/{workflows,automations,js-code-nodes,functions}/**/*
+alwaysApply: false
+---
+
+# OpenXiangda React SPA Workflow / Automation / Function Files
+
+Use the **`openxiangda-workflow-automation`** skill when editing:
+
+- `src/workflows/<code>/workflow.ts`
+- `src/automations/<code>/index.ts`
+- `src/js-code-nodes/<code>/index.ts`
+- `src/functions/<code>/index.ts`
+
+## Boundaries
+
+- 普通 `pending → processing → resolved → closed` 使用状态字段、领域状态机与 automation；只有真实审批语义才创建 workflow。
+- 复用后端业务逻辑优先 App Function；JS_CODE 用于跨表、批量、流程、平台 API、外部 HTTP 与复杂编排。
+- UI 交互、普通表单校验和展示逻辑留在 React 代码，不放进 JS_CODE。
+- 每个关键步骤使用 `ctx.logger.debug/info/warn/error`；第三方凭据只通过 `secretRefs` 与 `ctx.secrets.get()` 获取。
+- workflowId / automationId / functionId 不得跨 profile 复制。
+
+## Build and release
+
+```bash
+pnpm typecheck:js-code
+pnpm build-js-code --script <code>
+openxiangda resource validate <workflow|automation|function> --only <code> --profile <name>
+openxiangda resource plan <workflow|automation|function> --only <code> --profile <name>
+openxiangda resource publish <workflow|automation|function> --only <code> --change <change> --profile <name>
+```
+
+资源发布只生成候选子版本；正式环境托管发布必须走 candidate → preproduction deploy/test → 同 candidate promotion。

package/templates/openxiangda-react-spa/scripts/guard-publish.mjs

@@ -9,7 +9,7 @@ const lines = [
   '  openxiangda resource publish <type> --only <codes> --change <change> --profile <name>',
   '  openxiangda runtime deploy --no-activate --change <change> --profile <name>',
   '',
-  '正式激活后还必须 merge/push 冻结 SHA，再执行 release integration-status 与 release end。',
+  '发布前必须先把批准的提交合并并 push 到权威主线；激活后直接执行 release integration-status 与 release end。',
   '',
   'legacy lowcode-workspace publish-all 只用于旧 classic workspace 的兼容流程。',
   '',