Seed missing daemon installs from complete local CLI packages (#45558)

## Why

Daemon lifecycle commands previously required a standalone managed installation. A complete CLI package can supply the daemon executable and helpers without requiring a separate installer run.

## What changed

- Let `codex app-server daemon start`, `restart`, and `bootstrap` copy the invoking package into `CODEX_HOME/packages/app-server-daemon` when no daemon installation exists.
- Validate the package's platform, required helpers, executable identity, and copied contents before selecting the staged release.
- Preserve existing dedicated and legacy daemon selections, reject broken selections instead of replacing them, and leave the CLI package and selection unchanged.
- Preserve standalone release pins and latest-channel eligibility, and select dedicated releases using Unix symlinks or Windows junctions.

## Testing

Add package preparation tests for complete copies, incomplete packages, broken selections, legacy preservation, and update-channel handling. Add Windows junction creation and retargeting coverage, plus CLI integration tests that launch the copied package through `start`, `restart`, and `bootstrap`.

GitOrigin-RevId: abd2f4f82eae0885434ea30603c2c1c0ca760bef
This commit is contained in:
Eric Traut authored and copyberry committed 2026-09-15 00:33:41 +00:00
1 parent 446b771049
commit 653e5fbb9d
12 files changed
+815 -50

No files matched your search

+5
View File
@@ -5,6 +5,11 @@
slow-timeout = { period = "30s", terminate-after = 2 }
retries = 1
[[profile.default.overrides]]
# These cases copy a full debug CLI package and launch its new executable.
filter = 'package(codex-cli) & binary(app_server_daemon) & test(packaged_daemon_)'
slow-timeout = { period = "1m", terminate-after = 2 }
[profile.default.junit]
path = "junit.xml"