openxiangda 1.0.266 → 1.0.267

package/README.md

@@ -4,14 +4,19 @@
 
 OpenXiangda is a lightweight CLI and skill package for private low-code platforms.
 
-## Two runtime generations
-
-OpenXiangda now has two deliberately separate development tracks:
-
-- `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.
+## Repository boundary
+
+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 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.
 

package/lib/skills.js

@@ -82,62 +82,17 @@ 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',
-  },
+];
+
+const RETIRED_SKILL_SPECS = [
+  { name: 'openxiangda-v2', sourceRelativePath: 'v2/skills/openxiangda-v2' },
+  { name: 'openxiangda-v2-architecture', sourceRelativePath: 'v2/skills/openxiangda-v2-architecture' },
+  { name: 'openxiangda-v2-frontend', sourceRelativePath: 'v2/skills/openxiangda-v2-frontend' },
+  { name: 'openxiangda-v2-backend', sourceRelativePath: 'v2/skills/openxiangda-v2-backend' },
+  { name: 'openxiangda-v2-data-authz', sourceRelativePath: 'v2/skills/openxiangda-v2-data-authz' },
+  { name: 'openxiangda-v2-workflow-events', sourceRelativePath: 'v2/skills/openxiangda-v2-workflow-events' },
+  { name: 'openxiangda-v2-delivery', sourceRelativePath: 'v2/skills/openxiangda-v2-delivery' },
+  { name: 'openxiangda-v1-maintenance', sourceRelativePath: 'v2/skills/openxiangda-v1-maintenance' },
 ];
 
 function getDefaultCodexSkillsDir(env = process.env) {
@@ -242,6 +197,36 @@ 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;
@@ -252,10 +237,12 @@ function getSkillStatusReport(options = {}) {
   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,
     });
   }
 
@@ -283,6 +270,7 @@ function installSkills(options = {}) {
   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 +286,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 +317,9 @@ function installSkills(options = {}) {
       dryRun,
       force,
       operations,
+      retiredOperations,
       skills: after,
+      retiredSkills: retiredAfter,
     });
   }
 
@@ -446,6 +448,7 @@ function buildWarnings(legacySkills) {
 
 module.exports = {
   INSTALL_MANIFEST,
+  RETIRED_SKILL_SPECS,
   SKILL_SPECS,
   getSkillStatusReport,
   installSkills,

package/openxiangda-skills/SKILL.md

@@ -13,7 +13,7 @@ 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 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 the independently released `$openxiangda-v2` unified 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.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openxiangda",
-  "version": "1.0.266",
+  "version": "1.0.267",
   "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/",

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."