openxiangda 1.0.266 → 1.0.268

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 OpenXiangda contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -4,18 +4,23 @@
 
 OpenXiangda is a lightweight CLI and skill package for private low-code platforms.
 
-## Two runtime generations
+## Repository boundary
 
-OpenXiangda now has two deliberately separate development tracks:
+This repository contains only the stable OpenXiangda 1.x maintenance toolchain.
+It maintains existing resource-based applications and its legacy Delivery V2
+protocol. Stable applications keep this runtime and are not migrated by a
+platform upgrade.
 
-- `openxiangda` 1.x maintains existing resource-based applications and its legacy Delivery V2 protocol. Stable applications keep this runtime and are not migrated by a platform upgrade.
-- `v2/` contains the new platform-2.0 application toolchain: `create-openxiangda`, `@openxiangda/cli`, `@openxiangda/mcp`, standard React/NestJS packages, typed configuration, domain skills, and application-level deployment.
-
-For a new 2.0 application, start with [`v2/docs/getting-started.md`](v2/docs/getting-started.md). A 2.0 workspace has `openxiangda.config.ts`, `apps/web`, and `apps/server`; it must not use the 1.x resource/SDD publishing commands.
+OpenXiangda 2.0 is developed and released from the independent
+`tools/openxiangda-v2` repository pinned by the platform orchestration
+repository. A new 2.0 workspace must use that repository's current public
+packages, unified AI skill, templates, and documentation. It must not use the
+1.x resource/SDD publishing commands or any historical embedded copy of the
+2.0 toolchain.
 
 Normal OpenXiangda app development uses platform-user login tokens through `/openxiangda-api/v1`; it does not use AK/SK. External backend and third-party integrations use the separate `openxiangda-open-api` skill, `/dingtalk-api/v1.0`, and a platform-managed AK/SK credential.
 
-Private platform routing is fixed: backend APIs are under `/service`, platform management is under `/platform`, and app runtime access is under `/view`. Passing a root domain such as `https://yida.wisejob.cn/` to the CLI is supported; OpenXiangda stores the API base as `https://yida.wisejob.cn/service`.
+Private platform routing is fixed: backend APIs are under `/service`, platform management is under `/platform`, and app runtime access is under `/view`. Passing a root domain such as `https://platform.example.com/` to the CLI is supported; OpenXiangda stores the API base as `https://platform.example.com/service`.
 
 ## OpenXiangda 1.x Delivery V2 (maintenance)
 

package/lib/cli.js

@@ -114,6 +114,7 @@ const {
   summarizeBindingDifferences,
 } = require('./resource-binding-contract');
 const { getSkillStatusReport, installSkills } = require('./skills');
+const { resolveUpdateTarget, buildGenerationUpdateCommand } = require('./generation-update');
 const {
   assertOrClaimWorktreeOwner,
   claimWorktreeOwner,
@@ -532,9 +533,10 @@ async function update(args) {
     return;
   }
   const registry = normalizeNpmRegistry(flags.registry || OFFICIAL_NPM_REGISTRY);
+  const selection = resolveUpdateTarget({ target: flags.target });
 
   if (requestedSubcommand === 'check') {
-    const result = checkOpenXiangdaUpdate(registry);
+    const result = checkOpenXiangdaUpdate(registry, selection);
     if (flags.json) return writeJson(result);
     printUpdateCheck(result);
     return;
@@ -545,6 +547,7 @@ async function update(args) {
       json: Boolean(flags.json),
       skipSkills: Boolean(flags['no-skills']),
       timeoutSeconds: flags['timeout-seconds'],
+      ...selection,
     });
     if (flags.json) return writeJson(result);
     print('OpenXiangda 已更新。');
@@ -562,8 +565,8 @@ function normalizeNpmRegistry(value) {
   return registry.replace(/\/+$/, '') || OFFICIAL_NPM_REGISTRY;
 }
 
-function checkOpenXiangdaUpdate(registry) {
-  const latestVersion = fetchLatestOpenXiangdaVersion(registry);
+function checkOpenXiangdaUpdate(registry, selection = resolveUpdateTarget()) {
+  const latestVersion = fetchLatestOpenXiangdaVersion(registry, selection.channel);
   const versionComparison = compareVersions(latestVersion, CURRENT_VERSION);
   const updateAvailable = versionComparison > 0;
   return {
@@ -577,8 +580,10 @@ function checkOpenXiangdaUpdate(registry) {
       : versionComparison < 0
         ? 'local_newer_than_registry'
         : 'latest',
-    installCommand: `npm ${buildOpenXiangdaUpdateInstallPlan(registry).args.join(' ')}`,
-    skillInstallCommand: 'openxiangda skill install --force',
+    target: selection.target,
+    channel: selection.channel,
+    installCommand: `openxiangda update install --target ${selection.target}`,
+    skillInstallCommand: 'openxiangda skill install',
     compatibilityCheckCommand: 'openxiangda commands --json',
     checkedAt: new Date().toISOString(),
     notes: [
@@ -588,10 +593,10 @@ function checkOpenXiangdaUpdate(registry) {
   };
 }
 
-function fetchLatestOpenXiangdaVersion(registry) {
+function fetchLatestOpenXiangdaVersion(registry, channel = 'v1') {
   const result = spawnSync(
     'npm',
-    ['view', `${NPM_PACKAGE_NAME}@latest`, 'version', `--registry=${registry}`, '--json'],
+    ['view', `${NPM_PACKAGE_NAME}@${channel}`, 'version', `--registry=${registry}`, '--json'],
     {
       encoding: 'utf8',
       timeout: 30000,
@@ -630,17 +635,22 @@ function normalizeUpdateInstallTimeoutSeconds(value) {
 
 function buildOpenXiangdaUpdateInstallPlan(registryInput, options = {}) {
   const registry = normalizeNpmRegistry(registryInput);
+  const selection = resolveUpdateTarget(options);
+  const version = options.version || fetchLatestOpenXiangdaVersion(registry, selection.channel);
+  const execution = buildGenerationUpdateCommand(selection, version);
   const timeoutSeconds = normalizeUpdateInstallTimeoutSeconds(
     options.timeoutSeconds
   );
   return {
     registry,
     timeoutSeconds,
+    ...selection,
+    command: execution.command,
+    version,
     args: [
-      'install',
-      '-g',
-      `${NPM_PACKAGE_NAME}@latest`,
+      ...execution.args,
       `--registry=${registry}`,
+      ...(execution.command === 'npm' ? [
       '--prefer-offline',
       '--legacy-peer-deps',
       '--no-audit',
@@ -650,6 +660,7 @@ function buildOpenXiangdaUpdateInstallPlan(registryInput, options = {}) {
       '--fetch-timeout=60000',
       '--fetch-retry-mintimeout=1000',
       '--fetch-retry-maxtimeout=10000',
+      ] : []),
     ],
   };
 }
@@ -662,6 +673,7 @@ async function runCommandWithHeartbeat(command, args, options = {}) {
     let child;
     try {
       child = spawn(command, args, {
+        cwd: options.cwd || process.cwd(),
         encoding: 'utf8',
         stdio: quiet ? ['ignore', 'pipe', 'pipe'] : 'inherit',
         env: options.env || process.env,
@@ -731,7 +743,8 @@ async function installOpenXiangdaUpdate(registry, options = {}) {
   if (!quiet) {
     print(`执行: npm ${npmArgs.join(' ')}`);
   }
-  const installResult = await runCommandWithHeartbeat('npm', npmArgs, {
+  const installResult = await runCommandWithHeartbeat(plan.command, npmArgs, {
+    cwd: plan.cwd,
     quiet,
     timeoutMs: plan.timeoutSeconds * 1000,
     env: { ...process.env, npm_config_registry: plan.registry },
@@ -763,11 +776,15 @@ async function installOpenXiangdaUpdate(registry, options = {}) {
     },
   };
 
-  if (!options.skipSkills) {
+  if (!options.skipSkills && plan.target === 'workspace') {
     if (!quiet) {
       print('刷新 OpenXiangda skills: openxiangda skill install --force');
     }
-    const skillResult = spawnSync('openxiangda', ['skill', 'install', '--force'], {
+    const localManifest = path.join(plan.cwd, 'node_modules/openxiangda/package.json');
+    const localPackage = JSON.parse(fs.readFileSync(localManifest, 'utf8'));
+    const localBin = path.resolve(path.dirname(localManifest), typeof localPackage.bin === 'string' ? localPackage.bin : localPackage.bin.openxiangda);
+    const skillResult = spawnSync(process.execPath, [localBin, 'skill', 'install'], {
+      cwd: plan.cwd,
       encoding: 'utf8',
       stdio: quiet ? 'pipe' : 'inherit',
       timeout: 60000,

package/lib/generation-update.js

@@ -0,0 +1,42 @@
+const fs = require('fs');
+const path = require('path');
+
+function resolveUpdateTarget(options = {}) {
+  let root = path.resolve(options.cwd || process.cwd());
+  let workspace = null;
+  while (true) {
+    const v1 = fs.existsSync(path.join(root, 'app-workspace.config.ts')) || fs.existsSync(path.join(root, '.openxiangda/state.json'));
+    const v2 = fs.existsSync(path.join(root, 'openxiangda.config.ts')) || fs.existsSync(path.join(root, 'openxiangda-app.config.ts'));
+    if (v1 && v2) throw new Error('WORKSPACE_GENERATION_CONFLICT: 同一目录存在 V1/V2 工作区标记');
+    if (v2) throw new Error('WORKSPACE_ENGINE_GENERATION_MISMATCH: V1 CLI 不能升级 V2 项目；请使用统一入口');
+    if (v1) { workspace = root; break; }
+    const parent = path.dirname(root);
+    if (parent === root) break;
+    root = parent;
+  }
+  const target = options.target || (workspace ? 'workspace' : 'launcher');
+  if (!['workspace', 'launcher'].includes(target)) throw new Error('DISTRIBUTION_UPDATE_TARGET_INVALID: 使用 workspace 或 launcher');
+  if (target === 'workspace' && !workspace) throw new Error('DISTRIBUTION_WORKSPACE_REQUIRED: 未找到 V1 工作区');
+  return { target, channel: target === 'workspace' ? 'legacy-v1' : 'latest', cwd: workspace || process.cwd() };
+}
+
+function buildGenerationUpdateCommand(selection, version) {
+  if (!/^[12]\.\d+\.\d+$/.test(version)) throw new Error('DISTRIBUTION_UPDATE_VERSION_INVALID: 升级目标必须是已发布的稳定版本');
+  if (selection.target === 'launcher') {
+    if (!version.startsWith('2.')) throw new Error('DISTRIBUTION_UPDATE_GENERATION_MISMATCH: 全局入口需要 V2');
+    if (Number(process.versions.node.split('.')[0]) < 24) throw new Error('DISTRIBUTION_NODE_VERSION_REQUIRED: 全局统一入口需要 Node.js 24；当前 V1 项目环境不会自动改变');
+    return { command: 'npm', args: ['install', '-g', `openxiangda@${version}`] };
+  }
+  if (!version.startsWith('1.')) throw new Error('DISTRIBUTION_UPDATE_GENERATION_MISMATCH: V1 项目只允许安装 V1');
+  const file = path.join(selection.cwd, 'package.json');
+  if (!fs.existsSync(file)) throw new Error('DISTRIBUTION_PACKAGE_MANIFEST_REQUIRED: 工作区缺少 package.json');
+  const manifest = JSON.parse(fs.readFileSync(file, 'utf8'));
+  const pnpm = fs.existsSync(path.join(selection.cwd, 'pnpm-lock.yaml')) || manifest.packageManager?.startsWith('pnpm@');
+  if (pnpm && fs.existsSync(path.join(selection.cwd, 'package-lock.json'))) throw new Error('DISTRIBUTION_PACKAGE_MANAGER_CONFLICT: 多个包管理器锁文件');
+  if (fs.existsSync(path.join(selection.cwd, 'yarn.lock'))) throw new Error('DISTRIBUTION_PACKAGE_MANAGER_UNSUPPORTED: 请通过项目 Yarn 命令显式安装 openxiangda@legacy-v1');
+  return { command: pnpm ? 'pnpm' : 'npm', args: pnpm
+    ? ['add', ...(manifest.dependencies?.openxiangda ? [] : ['--save-dev']), '--save-exact', `openxiangda@${version}`, ...(fs.existsSync(path.join(selection.cwd, 'pnpm-workspace.yaml')) ? ['--workspace-root'] : [])]
+    : ['install', manifest.dependencies?.openxiangda ? '--save-prod' : '--save-dev', '--save-exact', `openxiangda@${version}`] };
+}
+
+module.exports = { resolveUpdateTarget, buildGenerationUpdateCommand };

package/lib/skills.js

@@ -11,9 +11,9 @@ const MANAGER = 'openxiangda';
 
 const SKILL_SPECS = [
   {
-    name: 'openxiangda',
-    displayName: 'OpenXiangda',
-    shortDescription: '私有化低代码平台 CLI 与 AI skill 入口。',
+    name: 'openxiangda-v1',
+    displayName: 'OpenXiangda V1',
+    shortDescription: 'OpenXiangda V1 维护入口，仅用于 V1 工作区。',
     sourceRelativePath: 'openxiangda-skills',
     type: 'root',
   },
@@ -82,64 +82,11 @@ const SKILL_SPECS = [
     sourceRelativePath: 'openxiangda-skills/skills/openxiangda-open-api',
     type: 'subskill',
   },
-  {
-    name: 'openxiangda-v2',
-    displayName: 'OpenXiangda 2.0',
-    shortDescription: '标准 React/NestJS 应用与应用级交付入口。',
-    sourceRelativePath: 'v2/skills/openxiangda-v2',
-    type: 'subskill',
-  },
-  {
-    name: 'openxiangda-v2-architecture',
-    displayName: 'OpenXiangda 2.0 Architecture',
-    shortDescription: '设计 2.0 应用边界与类型化平台契约。',
-    sourceRelativePath: 'v2/skills/openxiangda-v2-architecture',
-    type: 'subskill',
-  },
-  {
-    name: 'openxiangda-v2-frontend',
-    displayName: 'OpenXiangda 2.0 Frontend',
-    shortDescription: '开发 React、Ant Design 与标准后台页面。',
-    sourceRelativePath: 'v2/skills/openxiangda-v2-frontend',
-    type: 'subskill',
-  },
-  {
-    name: 'openxiangda-v2-backend',
-    displayName: 'OpenXiangda 2.0 Backend',
-    shortDescription: '开发平台托管的标准 NestJS 应用后端。',
-    sourceRelativePath: 'v2/skills/openxiangda-v2-backend',
-    type: 'subskill',
-  },
-  {
-    name: 'openxiangda-v2-data-authz',
-    displayName: 'OpenXiangda 2.0 Data and AuthZ',
-    shortDescription: '设计 Data API、RBAC 与上下文数据权限。',
-    sourceRelativePath: 'v2/skills/openxiangda-v2-data-authz',
-    type: 'subskill',
-  },
-  {
-    name: 'openxiangda-v2-workflow-events',
-    displayName: 'OpenXiangda 2.0 Workflow and Events',
-    shortDescription: '开发 Workflow Kernel v2 与持久事件消费者。',
-    sourceRelativePath: 'v2/skills/openxiangda-v2-workflow-events',
-    type: 'subskill',
-  },
-  {
-    name: 'openxiangda-v2-delivery',
-    displayName: 'OpenXiangda 2.0 Delivery',
-    shortDescription: '构建、部署、观察、晋级和回滚完整应用。',
-    sourceRelativePath: 'v2/skills/openxiangda-v2-delivery',
-    type: 'subskill',
-  },
-  {
-    name: 'openxiangda-v1-maintenance',
-    displayName: 'OpenXiangda 1.x Maintenance',
-    shortDescription: '不迁移地安全维护稳定 1.x 应用。',
-    sourceRelativePath: 'v2/skills/openxiangda-v1-maintenance',
-    type: 'subskill',
-  },
 ];
 
+// V1 does not own V2 or the unified routing skill, including historical installs.
+const RETIRED_SKILL_SPECS = [];
+
 function getDefaultCodexSkillsDir(env = process.env) {
   const codexHome = env.CODEX_HOME || path.join(os.homedir(), '.codex');
   return path.join(codexHome, 'skills');
@@ -242,20 +189,52 @@ function getSkillStatus(spec, skillsDir) {
   };
 }
 
+function getRetiredSkillStatus(spec, skillsDir) {
+  const targetDir = path.join(skillsDir, spec.name);
+  if (!fs.existsSync(targetDir)) {
+    return {
+      name: spec.name,
+      status: 'absent',
+      targetDir,
+      sourceRelativePath: spec.sourceRelativePath,
+    };
+  }
+
+  const manifest = readManifest(targetDir);
+  const isManagedRetiredSkill =
+    manifest?.manager === MANAGER &&
+    manifest.sourceRelativePath === spec.sourceRelativePath;
+  return {
+    name: spec.name,
+    status: isManagedRetiredSkill ? 'retired-managed' : 'preserved-external',
+    targetDir,
+    sourceRelativePath: spec.sourceRelativePath,
+  };
+}
+
+function removeRetiredManagedSkill(spec, skillsDir) {
+  const status = getRetiredSkillStatus(spec, skillsDir);
+  if (status.status === 'retired-managed') {
+    fs.rmSync(status.targetDir, { recursive: true, force: true });
+  }
+}
+
 function getSkillStatusReport(options = {}) {
   const agent = validateAgent(options.agent);
   const env = options.env || process.env;
 
   // 获取目标目录列表
-  const skillsDirs = getDualSkillsDirs(agent, env);
+  const skillsDirs = options.dest ? [path.resolve(options.dest)] : getDualSkillsDirs(agent, env);
 
   const results = [];
   for (const skillsDir of skillsDirs) {
     const skills = SKILL_SPECS.map(spec => getSkillStatus(spec, skillsDir));
+    const retiredSkills = RETIRED_SKILL_SPECS.map(spec => getRetiredSkillStatus(spec, skillsDir));
     results.push({
       agent,
       skillsDir,
       skills,
+      retiredSkills,
     });
   }
 
@@ -278,11 +257,12 @@ function installSkills(options = {}) {
   const force = Boolean(options.force);
 
   // 获取目标目录列表
-  const skillsDirs = getDualSkillsDirs(agent, options.env);
+  const skillsDirs = options.dest ? [path.resolve(options.dest)] : getDualSkillsDirs(agent, options.env);
 
   const results = [];
   for (const skillsDir of skillsDirs) {
     const before = SKILL_SPECS.map(spec => getSkillStatus(spec, skillsDir));
+    const retiredBefore = RETIRED_SKILL_SPECS.map(spec => getRetiredSkillStatus(spec, skillsDir));
     const conflicts = before.filter(item => item.status === 'foreign');
 
     if (conflicts.length > 0 && !force && !dryRun) {
@@ -298,17 +278,29 @@ function installSkills(options = {}) {
       targetDir: item.targetDir,
       sourceRelativePath: item.sourceRelativePath,
     }));
+    const retiredOperations = retiredBefore.map(item => ({
+      name: item.name,
+      operation: item.status === 'retired-managed' ? 'remove-retired-managed' : 'preserve',
+      targetDir: item.targetDir,
+      sourceRelativePath: item.sourceRelativePath,
+    }));
 
     if (!dryRun) {
       fs.mkdirSync(skillsDir, { recursive: true });
       for (const spec of SKILL_SPECS) {
         installOneSkill(spec, skillsDir);
       }
+      for (const spec of RETIRED_SKILL_SPECS) {
+        removeRetiredManagedSkill(spec, skillsDir);
+      }
     }
 
     const after = dryRun
       ? before
       : SKILL_SPECS.map(spec => getSkillStatus(spec, skillsDir));
+    const retiredAfter = dryRun
+      ? retiredBefore
+      : RETIRED_SKILL_SPECS.map(spec => getRetiredSkillStatus(spec, skillsDir));
 
     results.push({
       agent,
@@ -317,7 +309,9 @@ function installSkills(options = {}) {
       dryRun,
       force,
       operations,
+      retiredOperations,
       skills: after,
+      retiredSkills: retiredAfter,
     });
   }
 
@@ -408,7 +402,7 @@ function writeAgentMetadata(spec, skillDir) {
   const defaultPrompt =
     spec.defaultPrompt ||
     (spec.name === 'openxiangda'
-      ? '使用 $openxiangda 处理私有化低代码平台的登录、发布和诊断任务。'
+      ? '使用 $openxiangda-v1 处理 V1 工作区的登录、发布和诊断任务。'
       : `使用 $${spec.name} 处理对应的 OpenXiangda 低代码平台任务。`);
   const content = [
     'interface:',
@@ -446,6 +440,7 @@ function buildWarnings(legacySkills) {
 
 module.exports = {
   INSTALL_MANIFEST,
+  RETIRED_SKILL_SPECS,
   SKILL_SPECS,
   getSkillStatusReport,
   installSkills,

package/openxiangda-skills/SKILL.md

@@ -1,6 +1,6 @@
 ---
-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."
+name: openxiangda-v1
+description: "Maintain existing OpenXiangda V1 workspaces: forms, pages, resources, workflows, permissions, publishing and diagnosis. New applications default to V2; assess V2 adoption for V1 projects still in testing when capability coverage and migration cost permit."
 ---
 
 <!-- OpenXiangda-Policy-Version: 7 -->
@@ -13,10 +13,12 @@ This file is a router and safety card. Read only the one or two subskills select
 
 ## Select the runtime generation first
 
-If the workspace contains `openxiangda.config.ts`, `apps/web`, and `apps/server`, it is a platform-2.0 application. Stop this 1.x resource flow and use `$openxiangda-v2` plus its architecture, frontend, backend, data-authz, workflow-events, and delivery skills. The 2.0 CLI operates on one immutable application package and does not use SDD or per-resource publishing.
+If the nearest workspace contains `openxiangda.config.ts` or `openxiangda-app.config.ts`, it is a platform-2.0 application; a Nest server is optional. Stop this 1.x resource flow and use the independently released `$openxiangda-v2` skill. The 2.0 CLI operates on one immutable application package and does not use SDD or per-resource publishing.
 
 If the workspace contains `app-workspace.config.ts`, forms/pages/resource manifests, or an existing 1.x state directory, continue with this router. Never migrate a stable 1.x application merely because platform 2.0 is available.
 
+For an existing V1 project, proactively check whether V2 covers its required capabilities, whether it is still in testing, and whether migration cost is manageable. When those conditions hold, recommend V2 first and explain the benefit, rebuild scope and verification cost. Use the unified entry's `openxiangda migrate assess --to v2` for source pointers; confirm the project design, data/workflow mapping, acceptance and rollback before implementing migration. Keep unknown conditions explicit and continue current maintenance with the matching engine until migration is authorized.
+
 ## 1.x Delivery V2 is the normal 1.x release path
 
 When `app-workspace.config.ts` declares `deliveryVersion: 2`, all later V1 SDD,

package/openxiangda-skills/references/openxiangda-api.md

@@ -930,7 +930,7 @@ Body:
     "allowedExtensions": ["txt", "pdf", "png"],
     "cors": {
       "managed": true,
-      "allowedOrigins": ["https://yida.wisejob.cn"],
+      "allowedOrigins": ["https://platform.example.com"],
       "allowedMethods": ["PUT", "GET", "HEAD"],
       "allowedHeaders": ["content-type", "x-oss-*"],
       "exposeHeaders": ["ETag", "x-oss-request-id"],

package/openxiangda-skills/references/resource-manifest-cheatsheet.md

@@ -173,7 +173,7 @@ await auth.phoneCodeLogin({ phone, code, challengeId: sent.challengeId });
     "allowedExtensions": ["txt", "pdf", "png"],
     "cors": {
       "managed": true,
-      "allowedOrigins": ["https://yida.wisejob.cn"],
+      "allowedOrigins": ["https://platform.example.com"],
       "allowedMethods": ["PUT", "GET", "HEAD"],
       "allowedHeaders": ["content-type", "x-oss-*"],
       "exposeHeaders": ["ETag", "x-oss-request-id"],

package/openxiangda-skills/references/workspace-state.md

@@ -64,7 +64,7 @@ Environment-managed workspaces add a logical application and target-specific bin
   "currentTarget": "preproduction",
   "targets": {
     "preproduction": {
-      "profile": "hgy",
+      "profile": "instrument-example",
       "environmentId": "PRE_ENV_UUID",
       "kind": "preproduction",
       "appType": "APP_PRE",
@@ -82,7 +82,7 @@ Environment-managed workspaces add a logical application and target-specific bin
       "resources": {}
     },
     "production": {
-      "profile": "hgy",
+      "profile": "instrument-example",
       "environmentId": "PROD_ENV_UUID",
       "kind": "production",
       "appType": "APP_PROD",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openxiangda",
-  "version": "1.0.266",
+  "version": "1.0.268",
   "description": "OpenXiangda CLI, workspace build tools, runtime SDK, and form components.",
   "private": false,
   "bin": {
@@ -55,7 +55,6 @@
     "bin/",
     "lib/",
     "openxiangda-skills/",
-    "v2/skills/",
     "policy/",
     "templates/",
     "packages/sdk/bin/",
@@ -216,8 +215,58 @@
     "node": ">=18"
   },
   "publishConfig": {
+    "tag": "legacy-v1",
     "access": "public",
     "registry": "https://registry.npmjs.org/"
   },
-  "license": "MIT"
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/1377385356/openxiangda-v1.git"
+  },
+  "homepage": "https://github.com/1377385356/openxiangda-v1",
+  "bugs": {
+    "url": "https://github.com/1377385356/openxiangda-v1/issues"
+  },
+  "openxiangdaRelease": {
+    "schemaVersion": "openxiangda.release-notes/v1",
+    "version": "1.0.268",
+    "title": "OpenXiangda V1 维护版 1.0.268",
+    "status": "reviewed",
+    "summary": "旧项目继续使用 V1 引擎，项目升级保持在 V1 维护渠道；同时兼容新的全局统一入口与独立的 V2 Skill。",
+    "newFeatures": [
+      "V1 工具源码从经审查的公开基线发布到独立 GitHub 仓库，并提供对应版本说明。"
+    ],
+    "fixes": [
+      "在 V1 项目内执行 update 默认更新项目依赖，使用 v1 维护渠道并固定具体版本。",
+      "全局入口更新单独使用 --target launcher，检查 Node.js 24 要求并安装统一 V2 入口。",
+      "V1 主 Skill 使用 openxiangda-v1 名称，安装时保留统一入口和 V2 技能。",
+      "V1 发布仅允许 legacy-v1 渠道，防止维护版覆盖 V2 的 latest。"
+    ],
+    "affectedUsers": [
+      "维护既有 V1 项目的开发者",
+      "已经安装全局统一入口的 V1 用户"
+    ],
+    "compatibility": {
+      "node": ">=18；全局 V2 统一入口需要 >=24",
+      "workspaceGenerations": [
+        "v1"
+      ],
+      "workspacePolicy": "沿用现有 app-workspace.config.ts、平台绑定、登录态、业务数据及流程。",
+      "platformPolicy": "本次维护不改变平台协议或部署状态。"
+    },
+    "upgradeSteps": [
+      "项目依赖通过 v1 维护渠道升级，例如 npm install --save-dev --save-exact openxiangda@1.0.268；按项目实际包管理器和依赖类型调整。",
+      "安装全局 V2 统一入口后，进入旧项目运行 openxiangda version --json 核对 V1 引擎来源。",
+      "刷新对应项目的 V1 Skill，检查依赖与锁文件差异，并执行原有项目测试。",
+      "V2 能力满足、项目仍在测试阶段且迁移成本可控时，优先建议 V1 项目采用 V2；先完成项目评估、设计确认和迁移验收。"
+    ],
+    "knownLimitations": [
+      "本版本不会自动把 V1 应用迁移到 V2；跨代迁移需要独立设计、映射、演练和批准。",
+      "既有 1.0.267 及更早版本的全局更新命令可能安装 latest；新统一入口仍按旧项目标记调用 V1 引擎。"
+    ],
+    "issues": [],
+    "sha256": "7aaa99d31b91f725b785259031daaeaf3841cb18a95f6155e43009f1f601e6c9",
+    "url": "https://github.com/1377385356/openxiangda-v1/releases/tag/v1.0.268"
+  }
 }

package/templates/openxiangda-react-spa/app-workspace.config.ts

@@ -8,7 +8,7 @@ export default defineAppWorkspaceConfig({
   platformUrl:
     process.env.APP_PLATFORM_URL ||
     process.env.OPENXIANGDA_BASE_URL ||
-    "https://yida.wisejob.cn/service",
+    "https://platform.example.com/service",
   servicePrefix: process.env.APP_SERVICE_PREFIX || "/service",
   appKey: process.env.APP_KEY || "",
   appSecret: process.env.APP_SECRET || "",

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

@@ -139,7 +139,7 @@ sy-lowcode-app-workspace/
 
 ## 还想看更细的
 
-- 全局 skill：`~/.qoder/skills/openxiangda/SKILL.md`（root 决策卡）+ 9 个子 skill。
+- 全局 V1 skill：`~/.qoder/skills/openxiangda-v1/SKILL.md`（V1 决策卡）+ 9 个子 skill；`openxiangda` 由统一分发入口管理。
 - 资源 / 连接器 manifest：`docs/openxiangda-resources-and-connectors.md`（来自 openxiangda 仓库）。
 - 平台数据模型：`references/platform-data-model.md`（option `{label, value}`、附件、成员字段等持久化形态）。
 - 排错清单：`references/troubleshooting.md`。

package/templates/sy-lowcode-app-workspace/app-workspace.config.ts

@@ -4,7 +4,7 @@ export default defineAppWorkspaceConfig({
   deliveryVersion: 2,
   appType: process.env.APP_TYPE || process.env.OPENXIANGDA_APP_TYPE || "APP_XXXXXXXXXXXXXXXX",
   appName: process.env.APP_NAME || "低代码应用",
-  platformUrl: process.env.APP_PLATFORM_URL || process.env.OPENXIANGDA_BASE_URL || "http://yida.wisejob.cn/service",
+  platformUrl: process.env.APP_PLATFORM_URL || process.env.OPENXIANGDA_BASE_URL || "http://platform.example.com/service",
   servicePrefix: process.env.APP_SERVICE_PREFIX || "/service",
   appKey: process.env.APP_KEY || "",
   appSecret: process.env.APP_SECRET || "",

package/v2/README.md

@@ -1,35 +0,0 @@
-# OpenXiangda 2.0 toolchain
-
-This directory is the isolated OpenXiangda 2.0 package workspace. It does not
-import or dispatch the 1.x CLI implementation in `lib/cli.js`.
-
-Current packages:
-
-- `@openxiangda/contracts`: versioned wire contracts and JSON Schemas.
-- `@openxiangda/compiler`: deterministic configuration, generated contracts and AppPackage sealing.
-- `@openxiangda/devkit-core`: framework-neutral workspace, package and control-plane use cases.
-- `@openxiangda/nest`: trusted Principal/RoleSession Guard, Data API client,
-  signed CloudEvents receiver and standard backend health endpoints.
-- `@openxiangda/admin`: React + Ant Design application shell, capability-aware
-  data pages and protocol-driven Workflow v2/1.x compatibility pages.
-- `@openxiangda/testing`: permission fixtures, allow/deny matrix assertions and
-  local event record/replay/simulation.
-- `create-openxiangda`: distributable standard application workspace creator.
-- `@openxiangda/cli`: thin Oclif application-level CLI.
-- `@openxiangda/mcp`: structured AI resources and tools over the same services.
-- `@openxiangda/skill-kit`: validation, packaging and installation for the 2.0 domain skills.
-
-`templates/application` is the build-verified React 19 + NestJS 11 golden
-workspace. None of these packages imports or dispatches the 1.x CLI, so this
-toolchain can evolve without increasing the stable 1.x launcher surface.
-
-```bash
-pnpm install
-pnpm check
-pnpm test
-pnpm template:build
-pnpm skills:check
-pnpm docs:build
-```
-
-The fixed Changesets group publishes the packages as one compatible version train. See `docs/getting-started.md` for application usage and `docs/migration.md` for the strict 1.x coexistence boundary.

package/v2/skills/manifest.json

@@ -1,45 +0,0 @@
-{
-  "schemaVersion": 1,
-  "skills": [
-    {
-      "name": "openxiangda-v1-maintenance",
-      "description": "Maintain an existing stable OpenXiangda 1.x application without migrating it. Use for scoped fixes to legacy pages, forms, resources, App Function code, automation, workflow, or 1.x release records.",
-      "sha256": "7f554b8092397a0994f6aba70be38d2ec7eaf7524a075d68fb99ecbc95303525"
-    },
-    {
-      "name": "openxiangda-v2",
-      "description": "Build, inspect, validate, and deliver a complete OpenXiangda 2.0 application workspace. Use when a task spans the React frontend, NestJS backend, Data API, authorization, workflow, events, or whole-application delivery.",
-      "sha256": "5645e5cb1c18731d5b5fb21c9ad0e59b9760600794705bb4adcad1d0e316010b"
-    },
-    {
-      "name": "openxiangda-v2-architecture",
-      "description": "Design OpenXiangda 2.0 application boundaries and typed contracts. Use when creating an app, decomposing frontend and backend responsibilities, or changing Data, AuthZ, workflow, event, or deployment declarations.",
-      "sha256": "02768b17e048c623a13b9a99e5cedc72c9081eaa71b346c3d9db3ca66c95bf5e"
-    },
-    {
-      "name": "openxiangda-v2-backend",
-      "description": "Build the standard OpenXiangda 2.0 NestJS application backend. Use when implementing App APIs, Data API transactions, identity-aware business services, event consumers, health checks, or external integration endpoints.",
-      "sha256": "04c3de82f4406eaeb378910fbd53e2721c13e1cb9afbeb39f1c63f352522dd39"
-    },
-    {
-      "name": "openxiangda-v2-data-authz",
-      "description": "Design OpenXiangda 2.0 Data API and contextual authorization contracts. Use for RBAC, active-role behavior, department or record attributes, application-admin bypass, field policies, and restricted transactions.",
-      "sha256": "595fe9b8edc1e9b33720de21ed8758d4c266143c84fcb9eccc25a6adb5cce061"
-    },
-    {
-      "name": "openxiangda-v2-delivery",
-      "description": "Validate, build, deploy, observe, promote, retry, and roll back an OpenXiangda 2.0 application. Use when preparing an immutable AppPackage or changing a platform-managed environment.",
-      "sha256": "0ee0ffef78ebe37f60319bbf5684522ce61f8d6d084c360f46dc7bb2a31d1906"
-    },
-    {
-      "name": "openxiangda-v2-frontend",
-      "description": "Build OpenXiangda 2.0 React and Ant Design admin experiences. Use when implementing menus, routes, CRUD pages, role switching, workflow task pages, or application-defined action components.",
-      "sha256": "26add1dadeaf9a0a25d41163fb65cb70c1c5c7d882d57922193c3bd11d9d3e05"
-    },
-    {
-      "name": "openxiangda-v2-workflow-events",
-      "description": "Implement OpenXiangda Workflow Kernel v2 and durable application events. Use for approval definitions, assignee providers, task actions, delegation, add-sign, previews, data-change events, workflow events, or timers.",
-      "sha256": "e32a5dc84e21d32a00fbfff62a349d848b04d44a569eb4f89b390901f54bb19e"
-    }
-  ]
-}

package/v2/skills/openxiangda-v1-maintenance/SKILL.md

@@ -1,21 +0,0 @@
----
-name: openxiangda-v1-maintenance
-description: Maintain an existing stable OpenXiangda 1.x application without migrating it. Use for scoped fixes to legacy pages, forms, resources, App Function code, automation, workflow, or 1.x release records.
----
-
-# OpenXiangda 1.x Maintenance
-
-Preserve the installed 1.x runtime and its existing SDD, resource, function, automation, and workflow release process. Do not reinterpret the workspace as a 2.0 application package.
-
-## Maintenance Workflow
-
-1. Inspect the existing workspace and platform state with the installed 1.x OpenXiangda skills.
-2. Run `openxiangda sdd context --json` and create or select the required SDD change.
-3. Change only the named legacy resource. Keep existing identifiers and dependency order.
-4. Validate 1.x JS_CODE, App Function, page, form, automation, or workflow artifacts with their dedicated 1.x skill.
-5. Run `openxiangda sdd verify <change> --changed` and use the established 1.x publish gate.
-6. Verify the live application without migrating its runtime, data model, or deployment topology.
-
-Do not use 2.0 build, deploy, promote, or rollback commands for a 1.x workspace. Migration is a separate, explicitly approved project.
-
-Read [1.x Migration Boundary](../../docs/migration.md) before proposing any coexistence or migration work.

package/v2/skills/openxiangda-v1-maintenance/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "OpenXiangda 1.x Maintenance"
-  short_description: "Maintain stable OpenXiangda 1.x applications safely"
-  default_prompt: "Use $openxiangda-v1-maintenance to make a scoped maintenance change to this 1.x application."

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

@@ -1,38 +0,0 @@
----
-name: openxiangda-v2
-description: Build, inspect, validate, and deliver a complete OpenXiangda 2.0 application workspace. Use when a task spans the React frontend, NestJS backend, Data API, authorization, workflow, events, or whole-application delivery.
----
-
-# OpenXiangda 2.0
-
-Treat the repository as one typed application product. Work through package contracts and deterministic commands; do not mutate platform resources one at a time.
-
-## Start Here
-
-1. Run `openxiangda app info` and inspect the returned workspace and platform contract versions.
-2. Read `openxiangda.config.ts`, then identify which domain skill applies:
-   - architecture: `$openxiangda-v2-architecture`
-   - frontend: `$openxiangda-v2-frontend`
-   - backend: `$openxiangda-v2-backend`
-   - data and authorization: `$openxiangda-v2-data-authz`
-   - workflow and events: `$openxiangda-v2-workflow-events`
-   - delivery: `$openxiangda-v2-delivery`
-3. Keep generated contracts current with `openxiangda generate`.
-4. Before delivery, run `openxiangda check` and `openxiangda test`.
-
-For a new repository, link it to the target platform and let an authorized platform administrator run `openxiangda app provision` once. The command is idempotent and must not be used to migrate an existing 1.x identity.
-
-## Boundaries
-
-- Put browser code in `apps/web`, server code in `apps/server`, shared domain types in `packages/domain`, and generated declarations in `packages/contracts`.
-- Persist business records only through Data API or an App API implemented by the application backend.
-- Treat the active role and context attributes as explicit request state.
-- Use durable event consumers for side effects and idempotency keys for retries.
-- Build one immutable application package; the platform owns deployment execution, health gates, promotion, and rollback.
-- For a stable 1.x workspace, stop and use `$openxiangda-v1-maintenance`.
-
-## Delivery Gate
-
-Use `openxiangda build --backend-image <immutable-image>` only after checks pass. Use `openxiangda deploy`, `openxiangda status`, and `openxiangda logs` only when the user has authorized the environment change.
-
-Read [Getting Started](../../docs/getting-started.md) for the complete development loop.

package/v2/skills/openxiangda-v2/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "OpenXiangda 2.0"
-  short_description: "Build and deliver typed OpenXiangda 2.0 applications"
-  default_prompt: "Use $openxiangda-v2 to build and validate this OpenXiangda 2.0 application."

package/v2/skills/openxiangda-v2-architecture/SKILL.md

@@ -1,29 +0,0 @@
----
-name: openxiangda-v2-architecture
-description: Design OpenXiangda 2.0 application boundaries and typed contracts. Use when creating an app, decomposing frontend and backend responsibilities, or changing Data, AuthZ, workflow, event, or deployment declarations.
----
-
-# OpenXiangda 2.0 Architecture
-
-Design one independently versioned application with a standard React frontend and NestJS backend.
-
-## Design Sequence
-
-1. Inspect the workspace with `openxiangda app info`.
-2. Define business aggregates and invariants in `packages/domain`.
-3. Declare Data API resources, capabilities, policies, workflow definitions, event subscriptions, and timers in `openxiangda.config.ts`.
-4. Keep synchronous user interactions in App APIs; move retryable side effects to event consumers.
-5. Use a workflow provider when assignee resolution or a workflow action depends on application data.
-6. Generate types with `openxiangda generate`, then run `openxiangda check`.
-
-## Required Decisions
-
-- Name every resource, capability, event type, workflow, and provider with a stable application-scoped code.
-- Separate business data from workflow runtime state.
-- Define the authorization context needed for each operation, including active role and data attributes.
-- Define idempotency and concurrency behavior before implementing writes.
-- Define health, readiness, and rollback expectations as part of the application contract.
-
-Do not design environment-specific code paths. Environment values and secrets are injected by the platform at deployment time.
-
-Read [Concepts](../../docs/concepts.md) before introducing a new platform-facing contract.

package/v2/skills/openxiangda-v2-architecture/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "OpenXiangda 2.0 Architecture"
-  short_description: "Design typed OpenXiangda 2.0 application boundaries"
-  default_prompt: "Use $openxiangda-v2-architecture to design this OpenXiangda 2.0 application."

package/v2/skills/openxiangda-v2-backend/SKILL.md

@@ -1,28 +0,0 @@
----
-name: openxiangda-v2-backend
-description: Build the standard OpenXiangda 2.0 NestJS application backend. Use when implementing App APIs, Data API transactions, identity-aware business services, event consumers, health checks, or external integration endpoints.
----
-
-# OpenXiangda 2.0 Backend
-
-Build a normal NestJS service in `apps/server`. The platform deploys one container per application and injects identity, platform endpoints, environment configuration, and secrets.
-
-## Request Path
-
-1. Use the platform guard to verify the user token and construct typed request context.
-2. Authorize the capability and contextual data policy before accessing records.
-3. Keep invariants in domain services, not controllers.
-4. Use Data API for persistence and its restricted transaction endpoint for atomic batches.
-5. Require revision or idempotency keys for retryable writes.
-6. Return stable application contracts and structured errors.
-
-## Runtime Path
-
-- Expose liveness and readiness endpoints.
-- Consume platform events with signature verification and durable idempotency.
-- Keep outbound integrations behind adapters with timeouts and correlation IDs.
-- Read secrets only from injected environment references; never place them in source or application packages.
-
-Use `openxiangda dev` for local orchestration. Run `openxiangda check`, `openxiangda test`, and `openxiangda build --backend-image <immutable-image>` before deployment.
-
-Read [Backend](../../docs/backend.md) for the standard module layout.

package/v2/skills/openxiangda-v2-backend/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "OpenXiangda 2.0 Backend"
-  short_description: "Build standard NestJS application backend services"
-  default_prompt: "Use $openxiangda-v2-backend to implement this OpenXiangda 2.0 backend."

package/v2/skills/openxiangda-v2-data-authz/SKILL.md

@@ -1,28 +0,0 @@
----
-name: openxiangda-v2-data-authz
-description: Design OpenXiangda 2.0 Data API and contextual authorization contracts. Use for RBAC, active-role behavior, department or record attributes, application-admin bypass, field policies, and restricted transactions.
----
-
-# OpenXiangda 2.0 Data and AuthZ
-
-Model permissions as capability checks plus contextual data predicates. A role grants capabilities; policies decide which records and fields are available in the current role context.
-
-## Authorization Model
-
-1. Declare application roles and stable capability codes.
-2. Treat the selected active role as part of each request. Do not silently union all user roles.
-3. Resolve subject attributes such as departments and managed colleges from trusted platform or application providers.
-4. Resolve resource attributes such as instrument manager and college from the target record.
-5. Express allow rules as explicit subject, action, resource, and environment predicates.
-6. Grant application administrators the declared application-admin bypass and audit every bypassed write.
-
-## Data Rules
-
-- Declare resources and fields in `openxiangda.config.ts`; generate types with `openxiangda generate`.
-- Prefer server-enforced filters and field policies over client filtering.
-- Use revision checks for updates and restricted transaction batches for related writes.
-- Keep policy tests for multiple roles, role switching, cross-department denial, and administrator access.
-
-Run `openxiangda check` and `openxiangda test` after every policy or schema change.
-
-Read [Data and Authorization](../../docs/data-authz.md) for policy examples.

package/v2/skills/openxiangda-v2-data-authz/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "OpenXiangda 2.0 Data and AuthZ"
-  short_description: "Model Data API contracts and contextual authorization"
-  default_prompt: "Use $openxiangda-v2-data-authz to design this application's data authorization."

package/v2/skills/openxiangda-v2-delivery/SKILL.md

@@ -1,30 +0,0 @@
----
-name: openxiangda-v2-delivery
-description: Validate, build, deploy, observe, promote, retry, and roll back an OpenXiangda 2.0 application. Use when preparing an immutable AppPackage or changing a platform-managed environment.
----
-
-# OpenXiangda 2.0 Delivery
-
-Deliver the whole application as one immutable version. The client submits intent; the platform owns durable execution and environment state.
-
-## Preflight
-
-1. Run `openxiangda doctor` and confirm client/platform contract compatibility.
-2. For a first deployment only, confirm an authorized platform administrator has run `openxiangda app provision`.
-3. Run `openxiangda generate --check`, `openxiangda check`, and `openxiangda test`.
-4. Build and push the backend image; use an immutable digest reference.
-5. Run `openxiangda build --backend-image <immutable-image>` and retain the returned package digest.
-
-## Deployment
-
-- Inspect the plan before changing an environment.
-- Use `openxiangda deploy` only with explicit user authorization.
-- Follow the durable run with `openxiangda status` and `openxiangda logs`.
-- Use `openxiangda retry` only for retryable failed runs.
-- Use `openxiangda cancel <deploymentId>` to stop an obsolete or blocked run before submitting a replacement package.
-- Use `openxiangda promote` to move the exact same application version between environments.
-- Use `openxiangda rollback` to create a new run that activates a known historical version.
-
-Do not rebuild during promotion or rollback. Do not expose injected secrets in logs, manifests returned to clients, or package metadata.
-
-Read [Delivery](../../docs/delivery.md) for gates and failure handling.

package/v2/skills/openxiangda-v2-delivery/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "OpenXiangda 2.0 Delivery"
-  short_description: "Build deploy observe promote and rollback whole apps"
-  default_prompt: "Use $openxiangda-v2-delivery to validate and deploy this OpenXiangda 2.0 application."

package/v2/skills/openxiangda-v2-frontend/SKILL.md

@@ -1,21 +0,0 @@
----
-name: openxiangda-v2-frontend
-description: Build OpenXiangda 2.0 React and Ant Design admin experiences. Use when implementing menus, routes, CRUD pages, role switching, workflow task pages, or application-defined action components.
----
-
-# OpenXiangda 2.0 Frontend
-
-Build inside `apps/web` with `@openxiangda/admin`. Preserve the standard shell, role session, route guards, error handling, and typed clients.
-
-## Implementation Rules
-
-1. Register menus and routes through the application contribution API.
-2. Gate navigation and actions with generated capability names; the server remains authoritative.
-3. Use the active-role session supplied by the platform. Switching roles must refresh permissions and scoped data.
-4. Use the standard CRUD and workflow modules first; add application components only for real domain interactions.
-5. Render workflow actions and field policies from the backend protocol. Do not duplicate workflow transition rules in the browser.
-6. Keep data calls in typed client modules rather than components.
-
-Run `openxiangda generate`, `openxiangda check`, and `openxiangda test` after changing contracts or pages. Use accessible Ant Design patterns and run the repository's Ant Design lint when available.
-
-Read [Frontend](../../docs/frontend.md) for route, menu, role, and workflow page examples.

package/v2/skills/openxiangda-v2-frontend/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "OpenXiangda 2.0 Frontend"
-  short_description: "Build standard React and Ant Design application pages"
-  default_prompt: "Use $openxiangda-v2-frontend to implement this OpenXiangda 2.0 frontend."

package/v2/skills/openxiangda-v2-workflow-events/SKILL.md

@@ -1,28 +0,0 @@
----
-name: openxiangda-v2-workflow-events
-description: Implement OpenXiangda Workflow Kernel v2 and durable application events. Use for approval definitions, assignee providers, task actions, delegation, add-sign, previews, data-change events, workflow events, or timers.
----
-
-# OpenXiangda 2.0 Workflow and Events
-
-The workflow kernel owns definitions, instances, tasks, transitions, delegation, add-sign, audit, and field policies. The application owns business records and application-specific logic.
-
-## Workflow
-
-1. Declare approval and conditional nodes in `openxiangda.config.ts`.
-2. Use provider contracts for application-data-dependent assignee resolution and custom action decisions.
-3. Keep submit preview and actual start on the same definition version and subject context.
-4. Return allowed actions, field policies, presentation hints, and concurrency tokens from the backend.
-5. Persist business changes through Data API or App API, then correlate them to the workflow action.
-6. Test approve, reject, transfer, return, delegation, add-sign, duplicate requests, and stale revisions.
-
-## Events
-
-- Subscribe to typed data and workflow events; implement idempotent consumers.
-- Use timers as durable event producers.
-- Verify signatures, propagate correlation IDs, and fail retryably for transient dependencies.
-- Never assume event ordering unless the contract explicitly provides a partition key.
-
-Use `openxiangda generate`, `openxiangda check`, and `openxiangda test` to keep providers and event payloads aligned.
-
-Read [Workflow and Events](../../docs/workflow-events.md) for protocol details.

package/v2/skills/openxiangda-v2-workflow-events/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "OpenXiangda 2.0 Workflow and Events"
-  short_description: "Implement workflow providers and durable event consumers"
-  default_prompt: "Use $openxiangda-v2-workflow-events to implement this workflow and event behavior."