openyida 2026.10.28 → 2026.10.29-1

package/README.md

@@ -470,6 +470,7 @@ When preparing a PR that needs a personal Fork, or when you ask how to support t
 | `openyida app-settings <appType> [--section theme\|basic\|data-card\|cool-card] [--json]` | Read theme, frontend/backend, native data card and cool card management links |
 | `openyida cool-card <list\|templates\|create\|get> <appType> [cardPageCode] [--type im\|onebox] [--name <title>] [--page <n>] [--size <n>] [--search <text>] [--out <file>] [--json]` | Create and read native YiDA cool cards (interactive and pinned) |
 | `openyida data-card <list\|create\|get\|save\|publish\|probe\|release-get\|release-save\|release-check\|release-test\|refs> <appType> [cardCode] [--name <title>] [--description <text>] [--schema <file>\|--config <file>] [--expected-hash <hash>] [--backup <file>] [--out <file>] [--published\|--version <version>] [--page <n>] [--size <n>] [--search <text>] [--allow-send] [--json]` | Create, configure, publish and distribute native YiDA data cards |
+| `openyida plugin <dev-list\|get\|version-list\|version-get\|extensions\|installed-list\|installed-get\|runtime-list\|probe\|create\|create-version\|save-dev\|configure\|enable\|disable\|upgrade\|uninstall> [pluginId] [version] [options]` | Manage YiDA platform plugin versions, installation state, and runtime registrations |
 | `openyida app-entry get <appType> [--json]` | Read frontend and management runtime entries |
 | `openyida app-entry set <appType> [--frontend <url>\|--frontend-page <formUuid>] [--management <url>\|--management-page <formUuid>] [--clear-frontend] [--clear-management] [--json]` | Register application entries with partial update and readback |
 | `openyida app-list [--type managed\|created] [--page N] [--size N]` | Page through apps I manage or created |

package/bin/yida.js

@@ -775,6 +775,11 @@ async function main() {
       await run(args);
       break;
     }
+    case 'plugin': {
+      const { run } = require('../lib/plugin/plugin-lifecycle');
+      await run(args);
+      break;
+    }
 
     case 'app-settings': {
       const { run } = require('../lib/app/app-settings');

package/lib/agent/provider-preflight.js

@@ -139,13 +139,15 @@ function probe(executable, args, rpc, options = {}) {
       child = (options.probeSpawn || spawn)(command.executable, command.args, {
         env, cwd: os.tmpdir(), shell: false, windowsHide: true,
         windowsVerbatimArguments: command.windowsVerbatimArguments,
-        detached: platform !== 'win32', stdio: ['pipe', 'pipe', 'pipe'],
+        // Finite Windows probes do not consume input. Avoid an unused redirected
+        // stdin pipe during PowerShell startup; ACP still needs its live pipe.
+        detached: platform !== 'win32', stdio: [platform === 'win32' && !rpc ? 'ignore' : 'pipe', 'pipe', 'pipe'],
       });
       signals.once('SIGINT', interrupted);
       signals.once('SIGTERM', interrupted);
       timer = setTimeout(() => { stop(); finish({ status: 'probe_timeout' }); }, options.timeoutMs || 15000);
       child.on('error', () => finish({ status: 'launch_failed' }));
-      child.stdin.on('error', () => {});
+      if (child.stdin) { child.stdin.on('error', () => {}); }
       child.stderr.on('data', chunk => { output = (output + chunk.toString()).slice(-65536); });
       child.stdout.on('data', chunk => {
         output = (output + chunk.toString()).slice(-65536);
@@ -171,7 +173,7 @@ function probe(executable, args, rpc, options = {}) {
           ? { protocolVersion: 1, clientCapabilities: {}, clientInfo: { name: 'openyida-preflight', version: '1' } }
           : { clientInfo: { name: 'openyida-preflight', version: '1' }, capabilities: {} };
         child.stdin.write(JSON.stringify({ jsonrpc: '2.0', id: 1, method: 'initialize', params }) + '\n');
-      } else { child.stdin.end(); }
+      } else if (child.stdin) { child.stdin.end(); }
     } catch { finish({ status: 'launch_failed' }); }
   });
 }

package/lib/core/agent-capabilities.js

@@ -5,7 +5,7 @@ const fs = require('fs');
 const path = require('path');
 const { version } = require('../../package.json');
 const { t } = require('./i18n');
-const { buildCommandManifest } = require('./command-manifest');
+const { buildCommandManifest, buildEntryDeliveryPolicy } = require('./command-manifest');
 const { buildEnvironmentSnapshot } = require('./env');
 const coreUtils = require('./utils');
 const { buildHostAssetCapabilities } = require('../asset/host-capabilities');
@@ -497,7 +497,7 @@ function buildApplicationEntryPolicy(builderPath, env = process.env) {
   return {
     schema_version: 1,
     environment: injectedAuthUsable ? 'managed_cloud_agent' : 'non_cloud_agent',
-    delivery_unit: 'single_application_entry_group',
+    ...buildEntryDeliveryPolicy(),
     resource_delivery: 'summary_only',
     internal_artifact_delivery: 'never',
     frontend_delivery: 'Infer standalone for a scoped service frontend, persist page navigation hiding and return the verified publish/get-form-config standaloneUrl. No extra flag or navigation URL parameter. Missing verification is incomplete delivery; never silently omit the frontend or replace it with workbench/admin.',
@@ -701,7 +701,7 @@ function buildAgentCapabilities() {
       ],
       retry_policy: 'Do not repeat the same failed command without changing login state, organization, parameters, files, or field IDs.',
       completion_contracts: {
-        full_app: 'Default full-app build is complete after creating or reusing the app, core forms, primary page, publishing it, and returning one named application entry group. Summarize business resources in prose; do not deliver one artifact or link card per resource.',
+        full_app: 'Default full-app build is complete after creating or reusing the app, core forms, primary page, publishing it, and returning up to three verified application entry URLs, with runtime access and developer admin included by default. Summarize business resources in prose; do not deliver one artifact or link card per resource.',
       },
       full_app_data_contract: 'Default full-app page code must not call this.dataSourceMap.* unless the same run created and bound a designer data source; use this.utils.yida.* or an entry-only page by default.',
     },

package/lib/core/command-manifest.js

@@ -10,6 +10,29 @@ const { DIVIDER_TYPES, DEFAULT_DIVIDER_TYPE } = require('../app/form-field-valid
 const { FORMULA_COMMANDS } = require('../formula/cli-contract');
 const { printTemplateCommand, printTemplateEffects, printTemplatePermission } = require('../print-template/contract');
 
+/** 应用交付只约定入口内容；展示方式由宿主负责。 */
+function buildEntryDeliveryPolicy() {
+  return {
+    delivery_unit: 'application_entries',
+    presentation: 'host_managed',
+    entry_delivery: {
+      max_count: 3,
+      deduplicate_by: 'verified_url',
+      order: ['frontend', 'management', 'admin'],
+      by_scope: {
+        'service-management': ['frontend', 'management', 'admin'],
+        'frontend-only': ['frontend', 'admin'],
+        'backend-only': ['management', 'admin'],
+        unified: ['management', 'admin'],
+      },
+      explicit_user_exclusions: 'take_precedence',
+      resource_only: 'current_resource_only',
+      missing_entry: 'report_incomplete_without_guessing',
+    },
+  };
+}
+
+
 const SIDE_EFFECT_BASES = Object.freeze({
   local_read: Object.freeze({
     kind: 'local_read',
@@ -564,6 +587,13 @@ const COMMAND_SIDE_EFFECTS = new Map([
     note: 'Direct enable writes a durable local request receipt before the one-shot platform copy. AI build only validates the template and returns the native builder handoff.',
   })],
   ['data-card', sideEffect('mixed', { mutates_yida: true, mutates_local: true, read_actions: ['list', 'get', 'probe', 'release-check', 'refs'], mutating_actions: ['create', 'save', 'publish', 'release-get', 'release-save', 'release-test'], note: 'release-get reads broadcast settings but the native backend may initialize the application cool app; classify it conservatively as a possible mutation.' })],
+  ['plugin', sideEffect('mixed', {
+    mutates_yida: true,
+    mutates_local: true,
+    read_actions: ['dev-list', 'get', 'version-list', 'version-get', 'extensions', 'installed-list', 'installed-get', 'runtime-list', 'probe'],
+    mutating_actions: ['create', 'create-version', 'save-dev', 'configure', 'enable', 'disable', 'upgrade', 'uninstall'],
+    note: 'Organization-level YiDA plugin lifecycle. Writes require --confirm and deterministic readback; save-dev also writes a local backup.',
+  })],
   ['print-template', sideEffect('mixed', printTemplateEffects)],
   ['form-view', sideEffect('mixed', {
     mutates_yida: true,
@@ -864,6 +894,9 @@ const COMMAND_PERMISSIONS = new Map([
   ...permissionEntries(['cool-card'], actionDependentPermission({ preauthorized_actions: ['create'] })),
   ...permissionEntries(['solution-template'], actionDependentPermission({ ask_actions: ['enable'] })),
   ...permissionEntries(['data-card'], actionDependentPermission({ preauthorized_actions: ['create', 'save', 'publish', 'release-get'], ask_actions: ['release-save', 'release-test'] })),
+  ...permissionEntries(['plugin'], actionDependentPermission({
+    ask_actions: ['create', 'create-version', 'save-dev', 'configure', 'enable', 'disable', 'upgrade', 'uninstall'],
+  })),
   ...permissionEntries([
     'form-view',
   ], actionDependentPermission({
@@ -1237,6 +1270,25 @@ const COMMAND_GROUPS = [
         examples: ['openyida data-card create APP_XXX --name "Sales summary" --json', 'openyida data-card get APP_XXX CARD-XXX --out card-schema.json --json'],
         notes: ['Native dataCardRpc resources. Agent use requires an explicit user choice of native YiDA data cards or continuation of an already explicit native-card task; generic cards, KPIs, dashboards or broadcasts do not trigger this capability. Metric cards rendered by custom page code belong to the page; an embedded CARD reference alone does not authorize changes to its native source. get defaults to the draft; --published reads the online schema. --out exports the complete schema without overwriting a file. save accepts either a complete exported --schema or a simplified --config with charts and optional select filters (legacy indicators remains compatible), appending verified native components. Supports indicator/bar/line/pie/table/combo/gauge/funnel/calendarheatmap with real form fields, aggregates and date grain. Six-column layout, full-width tables and optional gauge min/max ranges. Five chart maximum; filters link only within the same source. probe performs read-only CARD runtime queries and returns component data; a saved schema alone is not runtime evidence. Numeric fields support COUNT/SUM/AVG/MIN/MAX; text and serial fields support COUNT. Config generation preserves the existing page and rejects unsupported keys/types. save requires its original --expected-hash; backs up and rereads before writing, then verifies readback. publish requires the current draft hash, backs up, and verifies the published schema, version and state; it does not save unsent local edits. Hash checks are not atomic server locking. New i18n bindings are synchronized before saving. Writes are not automatically replayed. Preserve platform permission and entitlement errors; never alter quotas or app tags. release-get exports broadcast configuration and releaseHash; the native GET may initialize a cool app and is conservatively classified as a possible mutation; release-save requires its original --expected-hash, backup and verified readback. Enabled schedules require explicit --allow-send; release-test also requires --allow-send and only requests a test to the current operator. release-check checks published state and broadcast entitlement; refs queries portal usage records. Group delivery still requires installation in DingTalk. Successful save or test acceptance does not prove delivery. The CLI does not mount portal components or delete cards. Mutation receipts refresh the app using the existing update_app_setting operation.'],
       }),
+      command('plugin', ['plugin'], 'plugin <dev-list|get|version-list|version-get|extensions|installed-list|installed-get|runtime-list|probe|create|create-version|save-dev|configure|enable|disable|upgrade|uninstall> [pluginId] [version] [options]', 'plugin_lifecycle.description', {
+        managedRun: { scope: 'denied', reason: 'organization_level_plugin_lifecycle' },
+        output: 'json',
+        args: [
+          { name: 'action', type: 'string', source: 'positional', position: 0, required: true },
+          { name: 'pluginId', type: 'string', source: 'positional', position: 1 },
+          { name: 'version', type: 'string', source: 'positional', position: 2 },
+          { name: 'config', type: 'file', source: 'option', builder_options: ['--config'] },
+          { name: 'expectedHash', type: 'string', source: 'option', builder_options: ['--expected-hash'] },
+          { name: 'backup', type: 'file', source: 'option', builder_options: ['--backup'] },
+          { name: 'extensions', type: 'string', source: 'option', builder_options: ['--extensions'] },
+          { name: 'checkResource', type: 'boolean', source: 'option', builder_options: ['--check-resource'] },
+          { name: 'type', type: 'string', source: 'option', builder_options: ['--type'], description: 'create only: connector (default) or other; custom-page extensions use other.' },
+          { name: 'confirm', type: 'boolean', source: 'option', builder_options: ['--confirm'] },
+          { name: 'json', type: 'boolean', source: 'option', builder_options: ['--json'] },
+        ],
+        examples: ['openyida plugin dev-list --search AI --json', 'openyida plugin runtime-list --extensions yida.app.custom-page.component --json', 'openyida plugin create --type other --name Timeline --description "Custom page timeline" --logo https://example.com/logo.png --confirm --json'],
+        notes: ['YiDA platform plugins, not npm packages or Codex plugins. Read commands separate persisted developer configuration, static resource reachability, runtime registry candidates, enabled state, and actual consumer execution. runtime-list includes disabled candidates and does not prove that an application consumed one. probe --check-resource sends a read-only HEAD request to the resolved HTTPS entry. save-dev and configure require the original hash and a non-overwriting backup; save-dev validates extension IDs and never publishes. Organization-wide writes require --confirm and readback. disable follows platform semantics: it blocks new selection but may not unload existing uses. The CLI intentionally does not publish/release/delete developer plugins or install from the market.'],
+      }),
       command('app-entry.get', ['app-entry', 'get'], 'app-entry get <appType> [--json]', 'app_entry.desc_get', { managedRun: {'scope':'app','appPosition':1},
         args: [{ name: 'appType', type: 'string', source: 'positional', position: 0, required: true },
           { name: 'json', type: 'boolean', source: 'option', builder_options: ['--json'] }],
@@ -2364,7 +2416,7 @@ function summarizeLocalizedCommands(commands) {
         product_design_policy: 'yida-requirement-analysis owns shared facts and first-time intake. yida-prd owns business planning; yida-design owns visual design. Reuse the same confirmed brief and supplied details. Prepare business and base visuals concurrently, then bind visuals to settled page tasks. yida-app merges and checks the artifacts before creating resources. Plan authors scope, data and rules, page organization, business interactions and acceptance once. Ordered blocks {name,purpose} supply default priority and content layers; explicit designs remain authoritative. Project-specific acceptance criteria are merged with generated resource checks. Plan uses the compact authoring contract and selected theme context; the CLI reads full templates and renders all artifacts. Fast, Plan and single-page design share yida-design/templates/design-themes and visual_decision_policy: infer directly from supplied style intent or extracted reference DNA, and use the shared three-direction rule only when comparison is needed. Theme templates declare application-global variables from basic-tokens.json with fixed typography, spacing and Tooltip colors, plus scoped custom-page variables; component recipes consume those variables. Each selected template is the authority for navTheme, its six navigation color tokens, and its selected-item shadow token; free-creative authors its own navigation tone and tokens. Explicit project customization stays in visualStyle.tokens. The CLI declares each fixed application palette once in a shared :root and platform-mode selector block. The CLI preserves mode-independent navigation appearance tokens. Light, dark, white and gray mode classes consume the same project tokens; navTheme remains platform metadata, not a second palette. Legacy generated mode blocks are consolidated on update, while unrelated custom CSS is preserved.',
         ui_guidance_policy: 'Page implementation consumes yida-prd prd.md for positioning, information architecture, page prototype, native form entry policy, material strategy, business-specific checks, resource creation order, page implementation delivery order, navigation order, and acceptance criteria; it consumes yida-design design.md for app custom theme CSS delivery, themeColor/navTheme, visual states, visualScaffold, surface material, rounded rules, density rules, components, state styling, and page-level imageNeed. When a page is imageNeed=required, or beneficial with declared image slots, yida-image-assets prepares a traceable asset manifest alongside page layout and interaction work; wait for final images only at that page\'s image binding and acceptance. imageNeed=none skips the branch. prd.md and design.md remain the only design sources of truth. Page implementation may extract page-spec.json as a derived implementation handoff from prd.md + design.md; conflicts are resolved by sending business conflicts to yida-prd and visual conflicts to yida-design before regenerating the spec. Core normal forms default to 1-3 business sample records before page implementation, followed by query readback. An explicit opt-out, configuration dictionary, sensitive data, or lack of safely constructible values requires a recorded skip reason. Screenshots, public sharing, data-source deep binding, and fine navigation grouping are optional after explicit user request or PRD acceptance criteria.',
         default_nav_order_policy: 'For application-wide custom navigation, implement each entry menu and verify app/page navigation hiding. A standalone frontend preserves platform navigation for the management workspace; frontend-only delivery skips platform ordering. After all scoped resources and page publications finish, perform exactly one navigation order operation. Use management tasks and their default destination, without creating a homepage or putting a frontend page first. When execution.entryRecommendation exists, derive navigationOrder from its management/workspace menus. Call openyida nav-group order <appType> <items...> for an explicit order; otherwise call openyida nav-group auto-order <appType> once for legacy single-workspace plans. Do not use openyida publish ... --auto-nav-order for per-page application builds. Explicit and automatic ordering are mutually exclusive; never generate per-item move loops.',
-        final_link_policy: 'Return exactly one user-visible application entry group, never one artifact or link card per form, process, report, schema, manifest, PRD, design file, or intermediate artifact. Include one verified management entry when a management or unified workspace is in scope: the app workbench URL or a planned workbench/formUuid URL with its real viewUuid. Backend-only returns its verified business backend entry and developer admin URL without adding a frontend. Native management does not require a display homepage; frontend-only delivery includes its verified frontend entry and developer admin URL, without inventing a business backend. For scoped service frontend pages, infer standalone when entryMode is missing; preserve an explicit platform-shell choice and its verified workbenchUrl. Add the clean custom page URL only for standalone pages when get-form-config readback confirms renderNav=false (fallback to isRenderNav only when renderNav is absent). Complete application delivery defaults to 2-3 distinct entries: frontend or unified workspace, business backend when separately planned, and developer admin. agent-capabilities application_entry_policy.entries.admin=include is independent of auth runtime. Read adminUrl from create-app or app-list results; route construction does not verify recipient permissions. Explicit user exclusions take precedence; single-page tasks retain their scope. Put the business summary, verification results and remaining work in the terminal delivery artifact description; when no delivery tool is available, return the same content and entry group in the final response. Summarize business resources by capability or count, but every resource count, seed-record count, and completed/verified claim must come from that resource\'s own successful result or readback. When the user or caller explicitly requests a resource manifest, resource UUIDs/IDs, publish status, or test-data summary, include one concise verified delivery manifest in that description (or the final response when no delivery tool is available).',
+        final_link_policy: 'Return up to three verified application entry URLs in frontend, business management, developer admin order; default complete delivery includes runtime access and developer admin. Never emit one artifact or link card per form, process, report, schema, manifest, PRD, design file, or intermediate artifact. Include one verified management entry when a management or unified workspace is in scope: the app workbench URL or a planned workbench/formUuid URL with its real viewUuid. Backend-only returns its verified business backend entry and developer admin URL without adding a frontend. Native management does not require a display homepage; frontend-only delivery includes its verified frontend entry and developer admin URL, without inventing a business backend. For scoped service frontend pages, infer standalone when entryMode is missing; preserve an explicit platform-shell choice and its verified workbenchUrl. Add the clean custom page URL only for standalone pages when get-form-config readback confirms renderNav=false (fallback to isRenderNav only when renderNav is absent). agent-capabilities application_entry_policy.entries.admin=include is independent of auth runtime. Read adminUrl from create-app or app-list results; route construction does not verify recipient permissions. Explicit user exclusions take precedence; single-page tasks retain their scope. QwenWork owns link, file and result presentation; return the verified summary and URLs without prescribing styles, card counts, display tools or update identifiers. Other hosts may use their terminal delivery artifact description; return the same concise content when no delivery tool is available. Summarize business resources by capability or count, but every resource count, seed-record count, and completed/verified claim must come from that resource\'s own successful result or readback. When the user or caller explicitly requests a resource manifest, resource UUIDs/IDs, publish status, or test-data summary, include one concise verified delivery manifest in that description (or the final response when no delivery tool is available).',
         entry_navigation_contract: {
           reference: 'yida-skills/skills/yida-app/references/entry-navigation.md',
           brief_path: 'entryRecommendation',
@@ -2407,10 +2459,10 @@ function summarizeLocalizedCommands(commands) {
           },
         },
         application_entry_policy: {
-          delivery_unit: 'single_application_entry_group',
+          ...buildEntryDeliveryPolicy(),
           persistence: {
             command_ids: ['app-entry.get', 'app-entry.set'],
-            policy: 'Before final complete-application delivery, registration and readback of all verified in-scope business runtime entries is required by default: service-management writes both, frontend-only writes frontend, backend-only/unified writes management. Resolve each planned default resource/view independently; never reuse the last published page or substitute a root workbench for a task URL. Use readback urls.frontend/management for final cards. Existing identical entries can reuse the readback; set performs partial merge and readback. Missing verification or failed persistence is incomplete delivery, not a reason to emit guessed links. Respect explicit no-write constraints. Do not register admin/design URLs. Incremental resource-only work preserves existing entries. Clear only on explicit removal. Conflicts require reread and review, never blind retries.',
+            policy: 'Before final complete-application delivery, registration and readback of all verified in-scope business runtime entries is required by default: service-management writes both, frontend-only writes frontend, backend-only/unified writes management. Resolve each planned default resource/view independently; never reuse the last published page or substitute a root workbench for a task URL. Use readback urls.frontend/management for final entry URLs. Existing identical entries can reuse the readback; set performs partial merge and readback. Missing verification or failed persistence is incomplete delivery, not a reason to emit guessed links. Respect explicit no-write constraints. Do not register admin/design URLs. Incremental resource-only work preserves existing entries. Clear only on explicit removal. Conflicts require reread and review, never blind retries.',
           },
           workbench: {
             include: 'when_workspace_in_scope',
@@ -2462,7 +2514,7 @@ function summarizeLocalizedCommands(commands) {
           'yida-data-source-connectors',
           'yida-dashboard',
         ],
-        completion_contract: 'Clarify core functions and actual usage first, then resolve the required resource context and settle entry navigation before PRD planning. Fast generates prd.md and design.md in parallel; Plan uses design-plan init/preview/materialize/patch and confirms the current revision. Validate both artifacts, create or reuse app and core forms/processes, seed and query-check core normal-form samples or record an allowed skip reason, then implement the primary page in PRD resource order, publish it, apply PRD navigation order or lightweight fallback navigation order for platform navigation, or verify app and per-page hiding for application-wide custom navigation. For a standalone frontend in a platform-navigation app, verify that page independently and retain workspace navigation. Before returning one named application entry group, persist and read back the verified in-scope frontend/management access addresses through app-entry get/set; final business links come from urls.frontend/management, not the last publish result. Include workbench when a management or unified workspace is in scope; backend-only delivers its business backend and developer admin URL without adding a frontend; frontend-only delivery includes its verified frontend entry and developer admin URL, without inventing a business backend. Always include developer adminUrl for complete application delivery unless explicitly excluded by the user, regardless of auth runtime; this is separate from the optional business backend. Use create-app or app-list URL fields and state any unavailable entry instead of silently omitting it. Put the verified business summary, results and remaining work in the delivery artifact description; use the final response when no delivery tool is available.',
+        completion_contract: 'Clarify core functions and actual usage first, then resolve the required resource context and settle entry navigation before PRD planning. Fast generates prd.md and design.md in parallel; Plan uses design-plan init/preview/materialize/patch and confirms the current revision. Validate both artifacts, create or reuse app and core forms/processes, seed and query-check core normal-form samples or record an allowed skip reason, then implement the primary page in PRD resource order, publish it, apply PRD navigation order or lightweight fallback navigation order for platform navigation, or verify app and per-page hiding for application-wide custom navigation. For a standalone frontend in a platform-navigation app, verify that page independently and retain workspace navigation. Before returning up to three verified application entry URLs, persist and read back the verified in-scope frontend/management access addresses through app-entry get/set; final business links come from urls.frontend/management, not the last publish result. Include workbench when a management or unified workspace is in scope; backend-only delivers its business backend and developer admin URL without adding a frontend; frontend-only delivery includes its verified frontend entry and developer admin URL, without inventing a business backend. Always include developer adminUrl for complete application delivery unless explicitly excluded by the user, regardless of auth runtime; this is separate from the optional business backend. Use create-app or app-list URL fields and state any unavailable entry instead of silently omitting it. Put the verified business summary, results and remaining work in the delivery artifact description; use the final response when no delivery tool is available.',
       },
     },
   };
@@ -2498,6 +2550,7 @@ function buildCommandManifest(options = {}) {
 module.exports = {
   COMMAND_GROUPS,
   buildCommandManifest,
+  buildEntryDeliveryPolicy,
   findCommandSuggestion,
   findForbiddenAliasSuggestion,
   flattenCommandManifest,

package/lib/core/locales/en.js

@@ -4,6 +4,7 @@
 'use strict';
 
 module.exports = {
+  plugin_lifecycle: { description: 'Manage YiDA platform plugin versions, installation state, and runtime registrations', failed: 'Plugin operation stopped: {0}', usage: 'Usage: openyida plugin <dev-list|get|version-list|version-get|extensions|installed-list|installed-get|runtime-list|probe|create|create-version|save-dev|configure|enable|disable|upgrade|uninstall> [pluginId] [version] [options]; create accepts --type connector|other; use other for custom-page extensions' },
   print_template: {
     'description': 'Manage native YiDA print templates, generate document layouts, back up, restore and request PDFs',
     'error': 'Print template operation failed: {0}',

package/lib/core/locales/zh.js

@@ -4,6 +4,7 @@
 'use strict';
 
 module.exports = {
+  plugin_lifecycle: { description: '管理宜搭平台插件开发版本、安装状态与运行时注册', failed: '插件操作已停止：{0}', usage: '用法：openyida plugin <dev-list|get|version-list|version-get|extensions|installed-list|installed-get|runtime-list|probe|create|create-version|save-dev|configure|enable|disable|upgrade|uninstall> [pluginId] [version] [options]；create 可选 --type connector|other，自定义页面扩展使用 other' },
   print_template: {
     'description': '管理宜搭原生打印模板、按字段生成多种单据、备份恢复与生成PDF',
     'error': '打印模板操作失败：{0}',