openxiangda-skill-kit 2.0.0-alpha.62 → 2.0.0-alpha.64

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "openxiangda-skill-kit",
3
- "version": "2.0.0-alpha.62",
3
+ "version": "2.0.0-alpha.64",
4
4
  "description": "Validation and deterministic packaging for OpenXiangda 2.0 AI skills.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
@@ -5,9 +5,17 @@ description: Use when building, inspecting, validating, or delivering a complete
5
5
 
6
6
  # OpenXiangda 2.0
7
7
 
8
- Use the generated React, NestJS and Data API workspace as one application. Before a workspace exists, invoke the 2.0 package explicitly with `pnpm dlx openxiangda-cli@latest`. Inside an application use only its locked CLI through `pnpm openxiangda`; never invoke a bare global `openxiangda`, because that executable may belong to 1.x.
8
+ Use the generated React, NestJS and Data API workspace as one application. Before a workspace exists, invoke the exact 2.0 package published with this Skill: `pnpm dlx openxiangda-cli@2.0.0-alpha.79`. Inside an application use only its locked CLI through `pnpm openxiangda`; never invoke a bare global `openxiangda`, because that executable may belong to 1.x.
9
9
 
10
- Start with `pnpm dlx openxiangda-cli@latest login`, then `pnpm dlx openxiangda-cli@latest create <directory>`. Run `pnpm openxiangda dev` for the local feedback loop and `pnpm openxiangda check` before delivery.
10
+ Start with `pnpm dlx openxiangda-cli@2.0.0-alpha.79 login`, then `pnpm dlx openxiangda-cli@2.0.0-alpha.79 create <directory>`. Run `pnpm openxiangda dev` for the local feedback loop and `pnpm openxiangda check` before delivery. Moving tags such as `latest` and `alpha` are forbidden for bootstrap because package-manager metadata and dlx caches can resolve an older toolchain.
11
+
12
+ For an AI-native development client, start the workspace MCP through the same
13
+ pinned executable with `pnpm exec openxiangda --mcp-stdio --cwd <workspace>`.
14
+ Read `openxiangda://workspace/contracts` or call `contract_describe` and verify
15
+ that `aiCatalog` and `aiCatalogDigest` match the normal compiler result. This is a
16
+ stdio transport mode, not another public CLI command. Never create an
17
+ application-owned MCP server, Catalog file, preview store or AI authorization
18
+ path.
11
19
 
12
20
  Keep ordinary CRUD on the platform Data API. Use NestJS only for real business actions. Page and field guards improve the interface; the platform remains authoritative for rows, fields and actions.
13
21
 
@@ -12,3 +12,4 @@
12
12
  - A single directory user reference uses a `string` field; a single department or same-app resource reference uses `uuid`; every `multiple: true` reference uses `json`. Roles that consume directory-backed fields explicitly include `app:<app-code>:directory:read`.
13
13
  - Do not add compatibility aliases, migration branches or silent fallbacks for an earlier 2.0 alpha contract. Replace an incorrect contract and regenerate the application.
14
14
  - Run `pnpm openxiangda check` after contract changes. Deploy with `pnpm openxiangda deploy`, inspect with `pnpm openxiangda status` and `pnpm openxiangda logs`, and use the platform rollback command rather than mutating K3s directly.
15
+ - AI-native clients start the workspace protocol through the same pinned binary: `pnpm exec openxiangda --mcp-stdio --cwd <workspace>`. Read `openxiangda://workspace/contracts` or call `contract_describe`, and require its `aiCatalog` and `aiCatalogDigest` to match the normal compiler output. This is a stdio transport mode, not a ninth CLI command. Never write an application MCP server, Catalog file, preview store or second authorization path.