---
id: "bug-1732"
status: "fixed"
status_updated: "2026-09-24"
status_note: ""
component: "build"
severity: "unknown"
timestamp: "2026-08-29T05:21:00Z"
last_seen: "2026-09-19T09:00:00Z"
occurrences: 2
files: ["src/tools/xce-build.sh (worker component case)"]
tags: ["build-tooling", "xce-build.sh", "worker", "xcecd_virtual", "low-priority"]
related: []
legacy: true
---

# bug-1732: src/tools/xce-build.sh's `worker` component case never builds `xcecd_virtual` (only `xcecd…

## Description
src/tools/xce-build.sh's `worker` component case never builds `xcecd_virtual` (only `xcecd xcecd_worker xrun controller_connector_test`), even though deploy-ha.sh requires xcecd_virtual whenever no real systemd manager is present (the common case in sandboxes) -- `/xce-build worker` alone leaves a deploy unable to auto-detect/generate start-worker.sh for the virtual worker.

## Environment
_Not recorded (migrated from buglog.json)._

## Reproduction
_Not recorded (migrated from buglog.json)._

## Root cause
The `worker)` case's explicit meson target list omits `xcecd_virtual`. Confirmed while dispatching a debug-profile build for a bug-1731 live repro: `/xce-build worker debug --incremental` completed successfully but did not produce `xcecd_virtual` in the build dir, requiring a manual `meson compile -C <builddir> xcecd_virtual` before deploy-ha.sh's own worker-binary auto-detection (Step 3, per the xce-deploy-ha skill) would find it and generate start-worker.sh instead of soft-skipping it.

## Fix
FIXED. Added `xcecd_virtual` to the `worker)` case's meson compile target list in src/tools/xce-build.sh (alongside the existing xcecd xcecd_worker xrun controller_connector_test), with a bug-1732-referencing comment. Verified: `xce-build.sh worker asan` now builds xcecd_virtual with a fresh mtime, and the full worker test suite (5/5, including test_uv_ipc_job_exit_severity) still passes with zero regressions.

## Verification
_Not recorded (migrated from buglog.json)._

## References
_Not recorded (migrated from buglog.json)._