PR #66205: fix(build): include subagent-registry.runtime.js in dist output

• Repository: openclaw/openclaw
• Author: yqli2420
• State: closed | merged: True
• Link: https://github.com/openclaw/openclaw/pull/66205

Description (problem / solution / changelog)

Summary

Describe the problem and fix in 2–5 bullets:

• Problem: The build configuration failed to generate subagent-registry.runtime.js in the dist folder, causing a module resolution error at runtime.
• Why it matters: This prevented the subagent registry from initializing, causing run_task calls with runtime: "subagent" to hang indefinitely in a queued state without surfacing errors to the user.
• What changed: Updated vite.config.ts to include a manualChunks rule for subagent-registry.runtime, ensuring the file is properly emitted during the build process.
• What did NOT change (scope boundary): No changes to runtime logic, API contracts, or other build configurations.

Change Type (select all)

• Bug fix
• Feature
• Refactor
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #66189

User-visible / Behavior Changes

run_task calls with runtime: "subagent" will now execute successfully instead of hanging indefinitely in a queued state. The gateway will no longer log ERR_MODULE_NOT_FOUND warnings regarding subagent-registry.runtime.js on startup.

Security Impact (required)

• New permissions/capabilities? (No)
• Secrets/tokens handling changed? (No)
• New/changed network calls? (No)
• Command/tool execution surface changed? (No)
• Data access scope changed? (No)
• If any Yes, explain risk + mitigation: N/A

Repro + Verification

Environment

• OS: macOS arm64
• Runtime/container: Node v25.9.0
• Model/provider: N/A
• Integration/channel (if any): Webhooks
• Relevant config (redacted): N/A

Steps

1. Build the project using the updated vite.config.ts.
2. Verify dist/subagent-registry.runtime.js exists in the output directory.
3. Verify dist/subagent-registry-CflSFWBm.js imports the generated file correctly.
4. Run the gateway and check logs for the absence of ERR_MODULE_NOT_FOUND.
5. Trigger a run_task with runtime: "subagent" and confirm it transitions out of queued.

Expected

subagent-registry.runtime.js is present in dist. Gateway starts without module errors. Subagent tasks execute successfully.

Actual

Prior to the fix, the file was missing, resulting in Error [ERR_MODULE_NOT_FOUND] on startup and silent task failures. After the fix, the file is generated and tasks run.

Evidence

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

• Verified scenarios: local scoped validation and targeted checks for the changed area passed
• Edge cases checked: relevant changed-path scenarios covered by selected validation
• What you did not verify: full repository integration coverage beyond the selected validation scope

Compatibility / Migration

• Backward compatible? (Yes)
• Config/env changes? (No)
• Migration needed? (No)
• If yes, exact upgrade steps: N/A

Failure Recovery (if this breaks)

• How to disable/revert this change quickly: Revert the changes to vite.config.ts and rebuild.
• Files/config to restore: vite.config.ts
• Known bad symptoms reviewers should watch for: If the regex in manualChunks is incorrect, the file might still be missing or named incorrectly, causing the original runtime error to persist.

Risks and Mitigations

Low risk. The change mirrors the existing logic for install.runtime. If the chunk name changes, it might break imports, but the fix explicitly targets the missing filename.

--- END TEMPLATE

Changed files

• CHANGELOG.md (modified, +1/-0)
• src/infra/tsdown-config.test.ts (modified, +1/-0)
• tsdown.config.ts (modified, +1/-0)

---

PR #66266: fix(build): ship subagent registry runtime sidecar

• Repository: openclaw/openclaw
• Author: vincentkoc
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/66266

Description (problem / solution / changelog)

Summary

• Problem: npm installs can ship dist/subagent-registry-*.js without the stable dist/agents/subagent-registry.runtime.js sidecar that src/agents/subagent-registry.ts imports at runtime.
• Why it matters: subagent runs can stay queued forever behind ERR_MODULE_NOT_FOUND instead of dispatching.
• What changed: add the missing stable dist entry in tsdown.config.ts, lock it into the tsdown config test, and add the user-facing changelog note.
• What did NOT change (scope boundary): no subagent runtime logic changed; this is build-entry and release artifact wiring only.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #66189
• Related #66205
• This PR fixes a bug or regression

Root Cause (if applicable)

• Root cause: subagent-registry.ts lazy-loads ./subagent-registry.runtime.js, but buildCoreDistEntries() never emitted that stable runtime entry.
• Missing detection / guardrail: the tsdown entry invariant test covered sibling runtime sidecars but not this one.
• Contributing context (if known): the original contributor PR correctly found the missing artifact but patched an unused root Vite config instead of the tsdown build graph.

Regression Test Plan (if applicable)

• Coverage level that should have caught this:
  • Unit test
  • Seam / integration test
  • End-to-end test
  • Existing coverage already sufficient
• Target test or file: src/infra/tsdown-config.test.ts
• Scenario the test should lock in: the unified dist graph includes agents/subagent-registry.runtime alongside the other stable runtime sidecars.
• Why this is the smallest reliable guardrail: the bug is an omitted build entry, so the most direct invariant is the tsdown entry map itself.
• Existing test that already covers this (if any): the same file already covers the neighboring stable runtime entries.
• If no new test is added, why not: N/A

User-visible / Behavior Changes

• npm-installed builds now ship the stable subagent registry runtime sidecar required for subagent dispatch.

Diagram (if applicable)

N/A

Security Impact (required)

• New permissions/capabilities? (No)
• Secrets/tokens handling changed? (No)
• New/changed network calls? (No)
• Command/tool execution surface changed? (No)
• Data access scope changed? (No)
• If any Yes, explain risk + mitigation:

Repro + Verification

Environment

• OS: macOS
• Runtime/container: local repo checkout
• Model/provider: N/A
• Integration/channel (if any): subagent runtime packaging
• Relevant config (redacted): N/A

Steps

1. Run pnpm test:serial src/infra/tsdown-config.test.ts
2. Run pnpm build
3. Verify dist/agents/subagent-registry.runtime.js exists

Expected

• The build emits the stable runtime sidecar and the config test includes the entry.

Actual

• Before this PR, the build graph omitted the stable sidecar entry.

Evidence

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

• Verified scenarios: tsdown config test passed; full pnpm build passed; confirmed dist/agents/subagent-registry.runtime.js exists after build.
• Edge cases checked: kept the change limited to the stable runtime entry list already used for sibling lazy runtime boundaries.
• What you did not verify: a live webhook/subagent end-to-end dispatch after npm global install.

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

• Backward compatible? (Yes)
• Config/env changes? (No)
• Migration needed? (No)
• If yes, exact upgrade steps:

Risks and Mitigations

• Risk: none beyond emitting one additional stable dist artifact already referenced by runtime code.
  • Mitigation: covered by the tsdown entry test and full build verification.

Changed files

• CHANGELOG.md (modified, +1/-0)
• src/infra/tsdown-config.test.ts (modified, +1/-0)
• tsdown.config.ts (modified, +1/-0)