openyida 2026.5.27 → 2026.6.1-beta.1

package/README.md

@@ -272,125 +272,172 @@ openyida append-chart APP_XXX REPORT_XXX .cache/openyida/reports/chart.json
 
 Run `openyida --help` or `openyida <command> --help` for detailed usage.
 
-### Environment and Authentication
+<!-- OPENYIDA_COMMANDS_START -->
+<!-- This section is generated by `npm run docs:commands`. Do not edit command rows by hand. -->
+
+### Auth & Environment
 
 | Command | Description |
 |---------|-------------|
-| `openyida env [--json]` | Detect the active AI tool environment and login state |
-| `openyida env setup` | Choose a customer-friendly login environment preset: public, overseas, Alibaba intranet, or private deployment |
-| `openyida env <list\|show\|switch\|add\|remove>` | Manage public/private Yida environment profiles |
-| `openyida commands [--json]` | Emit the machine-readable command manifest |
-| `openyida login [--qr\|--agent-qr\|--codex\|--browser] [--env <name>\|--intl\|--overseas\|--global\|--yidaapps] [--corp-id <corpId>]` | Log in to Yida |
-| `openyida logout` | Log out or switch account |
-| `openyida auth <status\|login\|refresh\|logout>` | Manage login status |
-| `openyida org list` | List accessible organizations |
-| `openyida org switch --corp-id <corpId>` | Switch organization without logging in again |
+| `openyida login [--qr\|--agent-qr\|--codex\|--browser] [--env <name>\|--intl\|--overseas\|--global\|--yidaapps] [--corp-id <corpId>]` | Login (cache first, --browser or --agent-qr when needed) |
+| `openyida logout` | Logout / switch account |
+| `openyida auth <status\|login\|refresh\|logout>` | Login state management |
+| `openyida org <list\|switch>` | Organization management (list / switch) |
+| `openyida env [--json]` | Detect AI tool environment & login state |
+| `openyida env <setup\|list\|show\|switch\|add\|remove>` | Manage public/private Yida environment profiles |
 
-Environment selectors such as `--env intl`, `--intl`, `--overseas`, `--global`, and `--yidaapps` can be used on login-required commands to choose the target Yida environment for that run. The `intl` preset uses `https://www.yidaapps.com` as the built-in Global YiDA entrypoint (not the bare `https://yidaapps.com` domain) and DingTalk International OAuth at `https://login.dingtalk.io`; business API requests still use the authenticated environment `baseUrl`, so customer custom subdomains are supported.
+### App Management
 
-For overseas apps, pass `--locale en_US` or `--locale ja_JP` on creation commands, or set `OPENYIDA_CONTENT_LOCALE`. OpenYida writes YiDA resource names with `zh_CN`, `en_US`, and `ja_JP` values so Global YiDA does not fall back to Chinese-only metadata.
-
-### Applications
+| Command | Description |
+|---------|-------------|
+| `openyida app-list [--size N]` | List my Yida apps |
+| `openyida corp-efficiency [overview\|details\|detail\|groups\|notify] [options] [--open\|--no-open]` | Query enterprise efficiency overview and detail reports |
+| `openyida create-app "<name>"\|--name <name> [options] [--locale zh_CN\|en_US\|ja_JP] [--open\|--no-open]` | Create a Yida app |
+| `openyida update-app <appType> [--name "..."] [--layout slide\|ver] [--theme deepBlue]` | Update app info |
+| `openyida nav-group <list\|create\|rename\|delete\|move\|hide\|show> <appType> ...` | Manage app sidebar navigation groups |
+| `openyida app-permission <get\|set\|add\|remove\|search-user> ...` | Manage app primary, data, and developer admins |
+| `openyida i18n <overview\|config\|languages\|list\|upsert\|delete\|translate\|translate-all\|upgrade> <appType> ...` | Manage app multilingual copy and language config |
+| `openyida export <appType> [output]` | Export app (generate migration package) |
+| `openyida import <file> [name]` | Import migration package, rebuild app |
+
+### Forms & Pages
 
 | Command | Description |
 |---------|-------------|
-| `openyida app-list [--size N]` | List Yida applications |
-| `openyida corp-efficiency [overview\|details\|detail\|groups\|notify] [options] [--open\|--no-open]` | Query enterprise efficiency metrics, detail report entries, and related notification actions |
-| `openyida create-app "<name>"\|--name <name> [options] [--locale zh_CN\|en_US\|ja_JP] [--open\|--no-open]` | Create an application and output `appType` |
-| `openyida update-app <appType> [--name "..."] [--layout slide\|ver] [--theme deepBlue]` | Update application metadata and theme/layout fields |
-| `openyida nav-group <list\|create\|rename\|delete\|move\|hide\|show> <appType> ...` | Manage sidebar navigation groups and move pages between groups |
-| `openyida app-permission <get\|set\|add\|remove\|search-user> ...` | Manage app primary admins, data admins, and developer members |
-| `openyida i18n <overview\|config\|languages\|list\|upsert\|delete\|translate\|translate-all\|upgrade> <appType> ...` | Manage app multilingual copy and language configuration |
-| `openyida export <appType> [output]` | Export an application migration package |
-| `openyida import <file> [name]` | Import a migration package into a target environment |
-
-### Forms and Pages
+| `openyida create-form create <appType> ... [--locale zh_CN\|en_US\|ja_JP] [--open\|--no-open]` | Create a form page |
+| `openyida create-form update <appType> ... [--locale zh_CN\|en_US\|ja_JP] [--open\|--no-open]` | Update a form page |
+| `openyida create-form patch <appType> <formUuid> <patchJsonOrFile> [--open\|--no-open]` | Update a form page |
+| `openyida create-form rule <appType> <formUuid> <rulesJsonOrFile> [--open\|--no-open]` | Update a form page |
+| `openyida create-form validation <appType> <formUuid> <validationsJsonOrFile> [--open\|--no-open]` | Update a form page |
+| `openyida add-validation <appType> <formUuid> --field <labelOrId> --type <phone\|regex\|idCard\|email\|...> [--message <text>]` | Update a form page |
+| `openyida create-form bind-datasource <appType> <formUuid> <fieldLabelOrId> <dataSourceJsonOrFile> [--open\|--no-open]` | Update a form page |
+| `openyida create-form add-option <appType> <formUuid> <fieldLabel> <option1> [option2] ...` | Update a form page |
+| `openyida list-forms <appType> [--keyword <text>]` | List forms/pages in an app |
+| `openyida aggregate-table <list\|create-empty\|inspect\|preview\|save\|publish\|status> <appType> ...` | Manage aggregate tables (virtualView) |
+| `openyida get-schema <appType> <formUuid\|--all>` | Get one form Schema or all form Schemas |
+| `openyida create-page <appType> "<name>" [--mode dashboard] [--locale zh_CN\|en_US\|ja_JP] [--open\|--no-open]` | Create a custom display page |
+| `openyida generate-page <template>` | Generate page from curated template |
+| `openyida build-page <sourceFile> [--output file\|--write]` | Build Yida-compatible page source |
+| `openyida check-page <src> [--compat]` | Check custom page standards |
+| `openyida compile <src>` | Compile custom page locally |
+| `openyida publish <src> <appType> <formUuid> [--health-check] [--force] [--open\|--no-open]` | Compile and publish custom page |
+| `openyida update-form-config <appType> ...` | Update form configuration |
+
+### Data & Permissions
 
 | Command | Description |
 |---------|-------------|
-| `openyida create-form create <appType> "<name>" <fields.json> [--locale zh_CN\|en_US\|ja_JP] [--open\|--no-open]` | Create a form page |
-| `openyida create-form update <appType> <formUuid> <changes.json> [--locale zh_CN\|en_US\|ja_JP] [--open\|--no-open]` | Update a form page |
-| `openyida create-form patch <appType> <formUuid> <patch.json> [--open\|--no-open]` | Apply controlled schema patches for designer-only form settings |
-| `openyida create-form rule <appType> <formUuid> <rules.json> [--open\|--no-open]` | Configure field show/hide linkage and onChange auto-assignment rules |
-| `openyida create-form validation <appType> <formUuid> <validations.json> [--open\|--no-open]` | Configure form validations using Yida-visible field `props.validation` rules and `customValidate` JSExpression functions for regex, bank card, cross-field, conditional, or async checks |
-| `openyida add-validation <appType> <formUuid> --field <labelOrId> --type <phone\|regex\|idCard\|email\|...> [--message <text>]` | Add one smart validation rule without writing a JSON file |
-| `openyida create-form bind-datasource <appType> <formUuid> <fieldLabelOrId> <datasource.json> [--open\|--no-open]` | Bind URL/search data sources to SelectField/MultiSelectField-style option fields |
-| `openyida create-form add-option <appType> <formUuid> <fieldLabel> <option1> [option2] ...` | Append options to a SelectField/RadioField/CheckboxField/MultiSelectField |
-| `openyida list-forms <appType> [--keyword <text>]` | List forms in an application |
-| `openyida aggregate-table <list\|create-empty\|inspect\|preview\|save\|publish\|status> <appType> ...` | Manage Yida aggregate tables (`virtualView`) |
-| `openyida get-schema <appType> <formUuid\|--all> [--field <labelOrFieldId>]` | Fetch one form schema, batch export all, or pick a single field's full props |
-| `openyida create-page <appType> "<name>" [--mode dashboard] [--locale zh_CN\|en_US\|ja_JP] [--open\|--no-open]` | Create a custom display page; dashboard mode hides top/workbench chrome |
-| `openyida generate-page <template> [--spec file]` | Generate custom page source from templates (`product-homepage`, `todo-mvc`) |
-| `openyida build-page <sourceFile> [--output file\|--write]` | Build/fix Yida-compatible page source from OpenYida authoring JSX |
-| `openyida check-page <sourceFile> [--compat] [--json]` | Check page compatibility; `.oyd.jsx` is compatibility-built before linting |
-| `openyida compile <sourceFile> [--compat]` | Compile a custom page locally; `.oyd.jsx` sources are compatibility-built first |
-| `openyida publish <sourceFile> <appType> <formUuid> [--compat] [--health-check] [--force] [--open\|--no-open]` | Compile and publish a custom display page; by default the target must be `formType=display` |
-| `openyida update-form-config <appType> <formUuid> <isRenderNav> <title> [--locale zh_CN\|en_US\|ja_JP]` | Update page/form display configuration |
+| `openyida data <action> <resource> [args]` | Unified data management (form/process/task/subform) |
+| `openyida task-center <type> [options]` | Global task center (todo/processed/cc etc.) |
+| `openyida basic-info <overview\|commodity\|grant\|capacity\|quota\|abs-path\|dataflow\|i18n\|domain>` | Query organization basic info, capacity, quotas, and domain settings |
+| `openyida get-permission <appType> <formUuid>` | Query form permission config |
+| `openyida save-permission <appType> <formUuid> ...` | Save form permission config |
+| `openyida corp-manager <search-user\|list\|add\|remove\|address-book> ...` | Manage platform admins and address book permissions |
+| `openyida agent-center <list\|create\|update\|cancel\|range\|search-user> ...` | Manage process and departure delegation |
 
-Form field definitions can include `alias` or `componentAlias` to populate Yida designer component aliases, stored as `pages[0].componentAlias.items`. Yida runtime resolves these aliases in page JS, so `this.$('phone')` can be used instead of `this.$('textField_xxx')`; OpenYida form rules, validations, and `openyida data ... --resolve-aliases` JSON inputs also accept aliases as field references. For server-side DingTalk OpenAPI calls, use `GET /v2.0/yida/forms/component/alias/{appType}/{formUuid}` to read the `{ fieldId, alias }` mapping, then translate aliases before sending form data/search JSON. That endpoint requires `systemToken`, `userId`, an access token, and the Yida form data read permission; grant that permission in DingTalk developer console API permissions and publish the DingTalk app. Yida app code and app secret are available under app settings > deployment/maintenance.
+### Process
 
-`openyida publish` preserves existing custom page data sources by default. Before saving the new compiled JSX Schema, it reads the current page Schema and merges the Page-level `dataSource` with the built-in `urlParams` and `timestamp` sources, so manually configured data sources are not deleted during republish.
+| Command | Description |
+|---------|-------------|
+| `openyida configure-process <appType> ...` | Configure and publish process rules |
+| `openyida create-process <appType> ...` | Create process form (all-in-one) |
+| `openyida ai-form-setting <get\|fields\|models\|enable\|disable\|save> <appType> ...` | Manage process form AI approval prompts |
+| `openyida process preview <appType> ...` | Preview process instance (visual flowchart) |
 
-### Data, Permissions, and Sharing
+### Page Config & Sharing
 
 | Command | Description |
 |---------|-------------|
-| `openyida data <action> <resource> [args]` | Unified data management for forms, processes, tasks, and subforms; form queries support `--all`, `--form-uuid` subform hydration, and `--resolve-aliases` for component alias JSON keys |
-| `openyida data check <appType> <formUuid> <rules.json>` | Detect anomalous process-form records |
-| `openyida task-center <type> [options]` | Query todo, created, processed, CC, or proxy-submitted tasks |
-| `openyida agent-center <sub-command>` | Manage Yida process delegation and departure delegation |
-| `openyida basic-info <overview\|commodity\|grant\|capacity\|quota\|abs-path\|dataflow\|i18n\|domain>` | Query organization basic info, capacity, quotas, fixed-domain records, and domain settings |
-| `openyida get-permission <appType> <formUuid>` | Query form permission configuration |
-| `openyida save-permission <appType> <formUuid> [options]` | Save form permission configuration, including raw `--field-permission <json>` |
-| `openyida corp-manager <sub-command>` | Manage platform admins, sub-admins, app admins, and address book visibility |
-| `openyida verify-short-url <appType> <formUuid> <url>` | Verify a short URL |
-| `openyida save-share-config <appType> <formUuid> <url> <isOpen> [openAuth]` | Save public access or sharing configuration |
-| `openyida get-page-config <appType> <formUuid>` | Query public access or sharing configuration |
-| `openyida externalize-form <appType> <formUuid> [--schema-file file]` | Assess public-access blockers and generate external-safe mirror fields |
-
-`openyida externalize-form` is useful when a form contains fields such as `AssociationFormField`, `EmployeeField`, or `DepartmentSelectField` that depend on internal organization permissions. It produces a report plus optional `--mirror-fields-output` JSON that can be used with `openyida create-form create` to build a separate public intake form while keeping the internal form and its association fields private.
+| `openyida verify-short-url <appType> ...` | Verify short URL |
+| `openyida save-share-config <appType> ...` | Save public access / share config |
+| `openyida get-page-config <appType> <formUuid>` | Query page public access config |
+| `openyida externalize-form <appType> <formUuid> [--schema-file file]` | Plan external access-safe mirror fields |
 
-### Workflow, Reports, and Integrations
+### Reports
 
 | Command | Description |
 |---------|-------------|
-| `openyida create-process <appType> ...` | Create a process form and configure workflow |
-| `openyida configure-process <appType> ...` | Configure and publish process rules |
-| `openyida ai-form-setting <get\|fields\|models\|enable\|disable\|save> <appType> ...` | Manage process-form AI approval prompts from `/settings/aiFormSetting` |
-| `openyida process preview <appType> <processInstanceId> [--output <path>]` | Generate a visual process preview |
-| `openyida create-report <appType> "<name>" <charts.json> [--open\|--no-open]` | Create a Yida report |
-| `openyida append-chart <appType> <reportId> <charts.json> [--open\|--no-open]` | Append a chart to an existing report |
-| `openyida connector <sub-command>` | Manage HTTP connectors, actions, tests, and auth accounts |
-| `openyida integration create <appType> <formUuid> <flowName> [options]` | Create an integration automation flow, including form and approval-process events |
-| `openyida integration list <appType> [--form-uuid <uuid>] [--status y\|n] [--json]` | List automation flows in an app, optionally filtered by form/status |
-| `openyida integration enable <appType> <formUuid> <processCode>` | Enable an automation flow |
-| `openyida integration disable <appType> <formUuid> <processCode>` | Disable an automation flow |
-| `openyida dws <command> [args]` | Access DingTalk CLI capabilities such as contacts, calendar, todo, and approval |
-| `openyida dingtalk-link <url> [--target fullScreen] [--legacy-scheme] [--json]` | Generate DingTalk AppLink URLs for opening pages in DingTalk; use `--legacy-scheme` only when old `dingtalk://` links are required |
+| `openyida create-report <appType> "<name>" ... [--open\|--no-open]` | Create a Yida report |
+| `openyida append-chart <appType> <reportId> ... [--open\|--no-open]` | Append chart to existing report |
 
-`openyida integration create` supports form events (`insert`, `update`, `delete`, `comment`) and approval events (`processFinish`, `activityTask`; aliases: `approval`, `approvalNode`). Approval events require `--approval-actions agree,disagree,terminated`; `activityTask` also requires `--approval-node-ids <nodeId,...>`.
+### Connectors
 
-### Utilities
+| Command | Description |
+|---------|-------------|
+| `openyida connector list` | List HTTP connectors |
+| `openyida connector create "name" "domain" ...` | Create a connector |
+| `openyida connector detail <id>` | View connector details |
+| `openyida connector delete <id>` | Delete a connector |
+| `openyida connector add-action --operations <file> --connector-id <id>` | Add an action |
+| `openyida connector list-actions <id>` | List actions |
+| `openyida connector delete-action <id> <operation-id>` | Delete an action |
+| `openyida connector test --connector-id <id> --action <actionId>` | Test an action |
+| `openyida connector list-connections <id>` | List auth connections |
+| `openyida connector create-connection <id> <name>` | Create an auth connection |
+| `openyida connector smart-create --curl "..."` | Smart create connector (from cURL) |
+| `openyida connector parse-api [options]` | Parse API information |
+| `openyida connector gen-template [output]` | Generate API document template |
+
+### Integration & DingTalk
+
+| Command | Description |
+|---------|-------------|
+| `openyida integration create <appType> ...` | Create integration automation flow |
+| `openyida integration list <appType> [--form-uuid <uuid>] [--status y\|n] [--json]` | List integration automation flows |
+| `openyida integration enable <appType> <formUuid> <processCode>` | Enable integration automation flow |
+| `openyida integration disable <appType> <formUuid> <processCode>` | Disable integration automation flow |
+| `openyida integration check <appType...>` | Check abnormal integration automation run logs |
+| `openyida integration diagnose (--text <text>\|--file <path>\|--rules) [--json]` | Diagnose integration automation tickets and common pitfalls |
+| `openyida dws <command> [args]` | DingTalk CLI (contacts/calendar/todo/approval etc.) |
+| `openyida dws contact user search --keyword <text>` | DingTalk CLI (contacts/calendar/todo/approval etc.) |
+| `openyida dingtalk-link <url> [--target fullScreen] [--legacy-scheme] [--json]` | Generate DingTalk AppLink / legacy dingtalk:// page links |
+
+### Utility
 
 | Command | Description |
 |---------|-------------|
-| `openyida copy [--force]` | Initialize the local `project/` workspace |
-| `openyida sample [--list]` | Emit sample templates |
-| `openyida bridge start [--token <pair-token>] [--port 6736] [--open]` | Start the local OpenYida web bridge for `https://demo.aliwork.com/s/openyida` |
-| `openyida doctor [--fix]` | Diagnose and repair environment issues |
+| `openyida commands [--json]` | Output machine-readable command manifest |
+| `openyida a2a <serve\|agent-card> [options]` | Start local read-only A2A adapter or print Agent Card |
+| `openyida bridge start [--token <pair-token>] [--port 6736] [--origin https://demo.aliwork.com] [--open\|--no-open]` | Start OpenYida local web bridge service |
+| `openyida copy [--force]` | Copy project working directory |
+| `openyida sample [--list]` | Output code samples/templates |
+| `openyida doctor [--fix]` | Environment diagnostics & auto-fix |
 | `openyida db-seq-fix [--fix]` | Detect and repair PostgreSQL sequence drift |
-| `openyida formula evaluate <formula\|file> [--schema file]` | Static-check formula syntax and field references |
-| `openyida update` | Update OpenYida through npm |
-| `openyida export-conversation [options]` | Export AI conversation history |
-| `openyida feedback <setup\|url\|dismiss\|status>` | Create a public Yida feedback form, generate privacy-safe feedback links, and manage local reminder snooze state |
-| `openyida flash-to-prd --file <path> --name "<project>"` | Convert flash notes or meeting notes into a PRD prompt |
-| `openyida ai text --prompt "..."` | Call Yida's text generation AI API |
-| `openyida ai image --file <image> --app-type APP_XXX` | Upload an image and call the image recognition connector |
-| `openyida cdn-config` | Configure image upload to Aliyun OSS/CDN |
-| `openyida cdn-upload <image-path>` | Upload an image to CDN |
+| `openyida formula evaluate <formula\|file> [--schema file]` | Static-check Yida formula syntax and field refs |
+| `openyida update` | Check and update to latest version |
+| `openyida export-conversation [options]` | Export AI conversation records |
+| `openyida feedback <setup\|url\|dismiss\|status> [options]` | Configure experience feedback form and local reminder state |
+| `openyida batch <file> [--stop-on-error] [--json]` | Run OpenYida commands in batch |
+| `openyida batch --commands "cmd1 ; cmd2" [--stop-on-error] [--json]` | Run OpenYida commands in batch |
+| `openyida flash-to-prd --file <path> --name "<project>"` | Convert flash notes or meeting notes to a PRD prompt |
+| `openyida ai <text\|image> [options]` | Call Yida AI text and image recognition APIs |
+| `openyida cdn-config [options]` | Configure CDN / OSS upload |
+| `openyida cdn-upload <image-path>` | Upload image to CDN |
 | `openyida cdn-refresh [options]` | Refresh CDN cache |
-| `openyida batch <file> [--stop-on-error] [--json]` | Run multiple commands from a file (one login, sequential execution) |
-| `openyida batch --commands "cmd1 ; cmd2" [--stop-on-error] [--json]` | Run inline batch commands |
+
+<!-- OPENYIDA_COMMANDS_END -->
+
+### CLI Notes
+
+#### Environment and Localization
+
+Environment selectors such as `--env intl`, `--intl`, `--overseas`, `--global`, and `--yidaapps` can be used on login-required commands to choose the target Yida environment for that run. The `intl` preset uses `https://www.yidaapps.com` as the built-in Global YiDA entrypoint (not the bare `https://yidaapps.com` domain) and DingTalk International OAuth at `https://login.dingtalk.io`; business API requests still use the authenticated environment `baseUrl`, so customer custom subdomains are supported.
+
+For overseas apps, pass `--locale en_US` or `--locale ja_JP` on creation commands, or set `OPENYIDA_CONTENT_LOCALE`. OpenYida writes YiDA resource names with `zh_CN`, `en_US`, and `ja_JP` values so Global YiDA does not fall back to Chinese-only metadata.
+
+#### Forms and Pages
+
+Form field definitions can include `alias` or `componentAlias` to populate Yida designer component aliases, stored as `pages[0].componentAlias.items`. Yida runtime resolves these aliases in page JS, so `this.$('phone')` can be used instead of `this.$('textField_xxx')`; OpenYida form rules, validations, and `openyida data ... --resolve-aliases` JSON inputs also accept aliases as field references. For server-side DingTalk OpenAPI calls, use `GET /v2.0/yida/forms/component/alias/{appType}/{formUuid}` to read the `{ fieldId, alias }` mapping, then translate aliases before sending form data/search JSON. That endpoint requires `systemToken`, `userId`, an access token, and the Yida form data read permission; grant that permission in DingTalk developer console API permissions and publish the DingTalk app. Yida app code and app secret are available under app settings > deployment/maintenance.
+
+`openyida publish` preserves existing custom page data sources by default. Before saving the new compiled JSX Schema, it reads the current page Schema and merges the Page-level `dataSource` with the built-in `urlParams` and `timestamp` sources, so manually configured data sources are not deleted during republish.
+
+#### Data, Permissions, and Sharing
+
+`openyida externalize-form` is useful when a form contains fields such as `AssociationFormField`, `EmployeeField`, or `DepartmentSelectField` that depend on internal organization permissions. It produces a report plus optional `--mirror-fields-output` JSON that can be used with `openyida create-form create` to build a separate public intake form while keeping the internal form and its association fields private.
+
+#### Workflow, Reports, and Integrations
+
+`openyida integration create` supports form events (`insert`, `update`, `delete`, `comment`) and approval events (`processFinish`, `activityTask`; aliases: `approval`, `approvalNode`). Approval events require `--approval-actions agree,disagree,terminated`; `activityTask` also requires `--approval-node-ids <nodeId,...>`.
 
 ## Agent Skills
 
@@ -465,11 +512,16 @@ Useful checks:
 |---------|---------|
 | `npm test` | Run Jest tests |
 | `npm run lint` | Run ESLint |
+| `npm run check:quick` | Run structure, manifest, syntax, and lint checks |
+| `npm run check:commands` | Validate router, command manifest, and README alignment |
+| `npm run docs:commands` | Regenerate the README command index from the manifest |
+| `npm run check:docs` | Verify generated README command docs are current |
 | `npm run check:syntax` | Validate JavaScript syntax |
 | `npm run check:structure` | Validate project structure |
+| `npm run check:package-size` | Validate npm package size and file-count budget |
 | `npm run check:package` | Validate npm package contents |
 
-When adding new CLI commands, register the route in `bin/yida.js`, add it to `lib/core/command-manifest.js`, update user-facing documentation here, and keep agent skills in `yida-skills/` aligned when the workflow changes.
+When adding new CLI commands, register the route in `bin/yida.js`, add it to `lib/core/command-manifest.js`, regenerate the README command index with `npm run docs:commands`, and keep agent skills in `yida-skills/` aligned when the workflow changes. `npm run check:commands` fails if the router, manifest, or README drift apart.
 
 ## Security and Configuration