openxiangda 1.0.265 → 1.0.267

package/packages/sdk/dist/runtime/react.d.mts

@@ -1,6 +1,6 @@
-import * as React from 'react';
 import React__default, { Dispatch, SetStateAction, CSSProperties, Key, ReactNode, HTMLAttributes } from 'react';
-import { bg as RuntimeAuthHeadersProvider, a as FormRuntimeApi, a9 as AttachmentItem, ab as FilePreviewCapability, aa as PreparedFilePreview, o as InitiatorSelectRequirement, I as InitiatorSelectCandidate, bf as ProcessPreviewProps, an as ApprovalTimelineProps } from '../ProcessPreview-DSUIJi5V.mjs';
+import { a$ as RuntimeAuthHeadersProvider, a9 as FormRuntimeApi, l as AttachmentItem, S as FilePreviewCapability, aJ as PreparedFilePreview, ao as InitiatorSelectRequirement, an as InitiatorSelectCandidate, aR as ProcessPreviewProps, e as ApprovalTimelineProps } from '../ProcessPreview-Cyk6uv-w.mjs';
+import * as react_jsx_runtime from 'react/jsx-runtime';
 
 type PageQueryValue = string | string[];
 type PageHttpMethod = "get" | "post" | "put" | "delete" | "patch";
@@ -2576,7 +2576,7 @@ interface AttachmentPreviewListProps {
     className?: string;
 }
 /** Read-only attachment list with capability-aware preview and download actions. */
-declare const AttachmentPreviewList: ({ items, appType, bucketName, showPreview, showDownload, showFileSize, showFileTypeBadge, emptyText, className, }: AttachmentPreviewListProps) => React__default.JSX.Element;
+declare const AttachmentPreviewList: ({ items, appType, bucketName, showPreview, showDownload, showFileSize, showFileTypeBadge, emptyText, className, }: AttachmentPreviewListProps) => react_jsx_runtime.JSX.Element;
 interface ImagePreviewGridProps {
     items?: AttachmentItem[];
     appType?: string;
@@ -2588,7 +2588,7 @@ interface ImagePreviewGridProps {
     className?: string;
 }
 /** Read-only image grid that opens the current item in the shared preview gallery. */
-declare const ImagePreviewGrid: ({ items, appType, bucketName, showPreview, showDownload, showFileName, emptyText, className, }: ImagePreviewGridProps) => React__default.JSX.Element;
+declare const ImagePreviewGrid: ({ items, appType, bucketName, showPreview, showDownload, showFileName, emptyText, className, }: ImagePreviewGridProps) => react_jsx_runtime.JSX.Element;
 type FilePreviewItem = AttachmentItem;
 
 type SelectedApproverMap = Record<string, InitiatorSelectCandidate[]>;
@@ -3129,7 +3129,7 @@ interface AdminListProps<Row> {
     onRow?: (row: Row) => HTMLAttributes<HTMLTableRowElement>;
 }
 
-declare function AdminList<Row>(props: AdminListProps<Row>): React.JSX.Element;
+declare function AdminList<Row>(props: AdminListProps<Row>): react_jsx_runtime.JSX.Element;
 
 declare function createFormAdminListSource<Row>(options: AdminListFormSourceOptions): AdminListDataSource<Row>;
 declare function createDataViewAdminListSource<Row>(options: AdminListDataViewSourceOptions): AdminListDataSource<Row>;

package/packages/sdk/dist/runtime/react.d.ts

@@ -1,6 +1,6 @@
-import * as React from 'react';
 import React__default, { Dispatch, SetStateAction, CSSProperties, Key, ReactNode, HTMLAttributes } from 'react';
-import { bg as RuntimeAuthHeadersProvider, a as FormRuntimeApi, a9 as AttachmentItem, ab as FilePreviewCapability, aa as PreparedFilePreview, o as InitiatorSelectRequirement, I as InitiatorSelectCandidate, bf as ProcessPreviewProps, an as ApprovalTimelineProps } from '../ProcessPreview-DSUIJi5V.js';
+import { a$ as RuntimeAuthHeadersProvider, a9 as FormRuntimeApi, l as AttachmentItem, S as FilePreviewCapability, aJ as PreparedFilePreview, ao as InitiatorSelectRequirement, an as InitiatorSelectCandidate, aR as ProcessPreviewProps, e as ApprovalTimelineProps } from '../ProcessPreview-Cyk6uv-w.js';
+import * as react_jsx_runtime from 'react/jsx-runtime';
 
 type PageQueryValue = string | string[];
 type PageHttpMethod = "get" | "post" | "put" | "delete" | "patch";
@@ -2576,7 +2576,7 @@ interface AttachmentPreviewListProps {
     className?: string;
 }
 /** Read-only attachment list with capability-aware preview and download actions. */
-declare const AttachmentPreviewList: ({ items, appType, bucketName, showPreview, showDownload, showFileSize, showFileTypeBadge, emptyText, className, }: AttachmentPreviewListProps) => React__default.JSX.Element;
+declare const AttachmentPreviewList: ({ items, appType, bucketName, showPreview, showDownload, showFileSize, showFileTypeBadge, emptyText, className, }: AttachmentPreviewListProps) => react_jsx_runtime.JSX.Element;
 interface ImagePreviewGridProps {
     items?: AttachmentItem[];
     appType?: string;
@@ -2588,7 +2588,7 @@ interface ImagePreviewGridProps {
     className?: string;
 }
 /** Read-only image grid that opens the current item in the shared preview gallery. */
-declare const ImagePreviewGrid: ({ items, appType, bucketName, showPreview, showDownload, showFileName, emptyText, className, }: ImagePreviewGridProps) => React__default.JSX.Element;
+declare const ImagePreviewGrid: ({ items, appType, bucketName, showPreview, showDownload, showFileName, emptyText, className, }: ImagePreviewGridProps) => react_jsx_runtime.JSX.Element;
 type FilePreviewItem = AttachmentItem;
 
 type SelectedApproverMap = Record<string, InitiatorSelectCandidate[]>;
@@ -3129,7 +3129,7 @@ interface AdminListProps<Row> {
     onRow?: (row: Row) => HTMLAttributes<HTMLTableRowElement>;
 }
 
-declare function AdminList<Row>(props: AdminListProps<Row>): React.JSX.Element;
+declare function AdminList<Row>(props: AdminListProps<Row>): react_jsx_runtime.JSX.Element;
 
 declare function createFormAdminListSource<Row>(options: AdminListFormSourceOptions): AdminListDataSource<Row>;
 declare function createDataViewAdminListSource<Row>(options: AdminListDataViewSourceOptions): AdminListDataSource<Row>;

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

@@ -59,6 +59,8 @@ openxiangda studio
 openxiangda commands --json
 ```
 
+未登记环境的旧工作区只有在平台已核验“精确非删除目标来自多次历史发布、无法对应单一 Git 基线”时，才可在同一条 `release publish` 上增加 `--adopt-online-baseline --adoption-reason "..."`。CLI 只把该意图传给精确 `resource publish --only/--code` 阶段；表单 ensure、Runtime 与 App finalize 不接收，原因不足或没有精确资源阶段会在获取租约前失败关闭。
+
 模板已停用无范围的 `pnpm deploy` 聚合入口。日常变更必须使用 `resource plan|publish <type> --only <codes>`（单资源可用 `--code <code>`）。Form bundle、Backend Release 和 Runtime 都先暂存；CLI 会按 `--change` 自动聚合 `.openxiangda/releases/<change>/staged-resources.json`，最后只由一次 Root App finalize 原子激活。Form Release 一旦 abort 绝不能作为幂等结果复用；重新执行相同精确表单发布时，CLI 会淘汰旧 staged 索引，平台会创建新的不可变 attempt，再由 Root App 一次事务重试。相同 change 的既有 staged FormRelease 只有在 CLI 重新核验服务端不可变状态、identity/hash、冻结 schema/formType、finalized 资源、parent/base revision 和当前 Form Head 后，才可重挂接到新的 baseline/session；`schemaSyncedAt` 只是本地缓存元数据。禁止伪造它、提前激活 Form 或用顺序激活多张表单绕过失败。不要使用 `workspace publish --form`、单独 `runtime activate`、`pnpm publish:all`、`pnpm openxiangda:publish` 或 `lowcode-workspace publish-all`。
 
 同一发布同时包含 Form 设置和表单权限组时，必须由一条 `resource publish form-setting,form-permission-group` 命令暂存，并在 `--only` 中分别使用 `form-setting:<code>`、`form-permission-group:<code>`。SDD bundle 与 prepublish 校验使用同一精确契约；缺失、夹带、拆成两个 FormRelease 或提前激活都应失败关闭。

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

@@ -65,7 +65,7 @@ Delivery V2 自动从期望状态按资源指纹计算精确范围，使用 CLI
 - ✅ Function/Automation 使用 Backend Release v2；正式多资源发布用精确 `--only/--code` 加 `--stage-only` 暂存，同一 child 可混合源码 create、无 `sourceFile` 的完整 v3 声明式 Automation manifest create、source-only update 和显式 manifest replacement，再由 Root App finalize 原子激活。声明式 create 自动选路；替换已有资源的整包 manifest 才需要另加 `--replace-manifest --reason "..."`。clone primary 与冻结仓库 ID 不同时，只有冻结 ID 已存在于 `repoAliases` 才会统一用于 Backend/Workflow/Root App Release；无交集继续失败关闭。
 - ✅ 相同 change 已有 staged FormRelease 时，不要直发 schema、伪造 `schemaSyncedAt` 或提前激活 Form。CLI 只在重新核验服务端不可变状态、identity/hash、冻结 schema/formType、finalized 资源、parent/base revision 与当前 Form Head 后，才将 child 重挂接到新的 baseline/session；冲突继续失败关闭。
 - ✅ 同一发布同时包含 Form 设置和表单权限组时，必须使用一条 `resource publish form-setting,form-permission-group`，并以 `form-setting:<code>`、`form-permission-group:<code>` 精确限定 `--only`；SDD bundle 与 prepublish 校验共享该契约，禁止缺失、夹带、拆分发布或提前激活。
-- ✅ 未登记环境的旧工作区，正式 promotion 先聚合 mainline bundle 并 commit/push，再运行 `release publish --change <id> --profile <name>`。
+- ✅ 未登记环境的旧工作区，正式 promotion 先聚合 mainline bundle 并 commit/push，再运行 `release publish --change <id> --profile <name>`。平台核验精确非删除目标来自多次历史 lineage 后，可成对增加 `--adopt-online-baseline --adoption-reason "..."`；参数只进入精确 `resource publish --only/--code` 阶段，不进入 ensure、Runtime 或 App finalize，无精确资源范围时在获取租约前失败关闭。
 - ✅ 旧工作区已有 Root、且操作者明确授权无条件恢复时，可执行 `release app-activate <releaseId> --force-activate-without-validation --profile <name>`。该命令不读取 detail/capture，不要求 change、租约、baseline、源码 lineage、状态、parent、hash、resource head 或环境发布门禁；服务端直接在目标 tenant/appType 内以单事务切换 Root 与可识别的 staged children。
 - ✅ 已通过 `environment init` 或 `environment attach` 接入的工作区使用 `release ship`，始终按 candidate → preproduction → production 执行。日常首条命令在预发停止，后续 `--confirm-production` 晋级；用户明确授权紧急发布时，首条命令可携带 `--confirm-production` 在一个命令内顺序完成两阶段，但不跳过预发、证据、CAS 或确认。candidate 封存源码、public、构建配置/脚本、稳定环境/资源绑定和两目标 Runtime 哈希产物；部署不现场重建，Backend/Runtime/Root 子发布始终使用 candidate sourceRevision，并将两条服务端 deployment 闭环为 `succeeded`。两套环境身份仍完全隔离，人工验收建议和 swap/policy/权限门禁保持不变。
 - ✅ DataView `status` 仅是平台生命周期观察值；同一托管部署导致的 `active → draft → active` 不应让候选失效。`dataViewId`、`materializedViewName`、`storageMode`、其他资源状态、哈希、环境身份、CAS、租约和来源主线仍严格校验。

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