Skip to content

[REQ-128][CODE] 抽取 Bundle 共用 planning builders 与 health probe router #705

Closed

Description

@jinjunnn

Covers

alpha-work#49 AC5 的 enabling seam:把 Agent、vendored Plugin、MCP 单装实现收敛为
可组合 planning builders 与统一 health probe router,行为保持不变;本票不激活 mixed Bundle。

Solution baseline

REQ-128 accepted baseline
§1.2、§2.8、§5。

Ground truth and boundary

  • packages/ui-mac/src/main/ext-agent-install.ts 已有 Agent file+config transaction/probe。
  • packages/ui-mac/src/main/ext-install-planner.ts 内有 vendored Plugin 与 MCP整段 executor。
  • packages/ui-mac/src/main/ext-ipc.ts 已组合生产 recovery probes。

主要产物:

  • buildAgentTxItems
  • buildVendoredPluginTxItems
  • buildMcpTxItems
  • extensionHealthProbeRouter

Development plan

  1. 从现有单装 executor 提取纯 builder,返回 items、receipt、precondition、prepared resource
    descriptor 与 typed probe;不复制执行逻辑。
  2. 单装改用 builder,仍只由 runExtensionTransaction 执行。
  3. 把 ext-ipc 的现有 probe组合提为唯一 router,recovery 与未来 Bundle 共用。
  4. nested Bundle 当前“解析传递图但只装 direct child”的模糊路径改为门前明确拒绝;
    Desktop 不递归 flatten。
  5. 不接 mixed Bundle、V3 graph、secret populate 或 managed npm。

Acceptance and named gates

  • 单装 Agent/vendored Plugin/MCP 的 before/after plan、receipt、probe 与故障语义 parity。
  • production wiring test证明单装与 recovery均经过 builders/router。
  • nested Bundle 在 download/secret/transaction前明确 unsupported,调用数为零。
  • 本票只需 unit/wiring parity;不要求 packaged mixed Bundle evidence。

Dependencies

无实现依赖;accepted baseline 后可立即开发。

Out of scope

第二套 installer、V3 ledger、mixed activation、通用 prepared-resource framework。

Exit condition

Merged behavior-preserving PR + parity/wiring tests + docs impact handled。

Activity

  1. self-assigned this
    on Jul 30, 2026
  2. added
    type:refactorInternal restructuring without behavior change
    prio:P1High-value near-term delivery
    area:runtimeServices, jobs, infrastructure, or operations
    cross-repoRequires coordinated work in multiple repositories
    on Jul 30, 2026
  3. added 3 commits that reference this issue on Aug 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:runtimeServices, jobs, infrastructure, or operationscross-repoRequires coordinated work in multiple repositoriesprio:P1High-value near-term deliverytype:refactorInternal restructuring without behavior change

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions