Open Farming release 110992205bd21e7515032468938cffd89e0e56f6 runs its main and API services, including bare Bun children, with the required release-local Bun 1.4.4. Separate host readback found that the native generated openfarming-main-scheduler.service still uses the host Bun 1.4.2.
Fix this in the owning ts-cloud source issue #197, release it through bun run release:patch, then consume the qualified public release through native frozen installs and deploy. Do not edit installed packages, manually rewrite production units or replace the global host runtime.
Acceptance:
- Qualify native generated scheduler and queue executable selection and child PATH using the actual selected release-local runtime.
- Preserve release/current lifecycle, including children admitted before the current symlink changes, and preserve existing default and Laravel behavior.
- Consume the qualified maintained source release through native dependency installation.
- Deploy and verify actual remote background processes and their children while leaving the shared host runtime unchanged.
- Retain the verified main/API catalog recovery and customer-data protections.
Scheduled Mission records remain distinct from physical dispatch, treatment or flight completion. This runtime fix does not qualify physical operations.
Qualified completion, October 25
Implemented at the owning source in ts-cloud #198, released through native bun run release:patch as 0.16.70, and consumed with normal Bun update and frozen installs in Open Farming #43.
Exact main CI and native deployment passed at 7399f13701a935f8bee6e1e975154ce2d7e9c0ed. Actual main/API packages are Stacks/cloud 0.75.301 and ts-cloud/core/aws-types 0.16.70. Fresh public artifact qualification passed eight deployment combinations and ten real scheduler/queue entry cases; the source lifecycle suite covers release switching, pruning, replacement, failed drain and retained assets.
Live readback proves exactly one main scheduler, zero restarts, the physical release-local Bun 1.4.4 executable and working directory, and an absolute release-local child PATH. A finite child probe using the observed process executable/cwd/PATH reports parent and child 1.4.4. This is launch-context qualification, not a claim that a scheduled production job executed. Main/API probes also pass. The shared host Bun remains 1.4.2. No deployed-unit or installed-package rewrites were used.
All seven protected customer groups match complete-row fingerprints from before deployment and the immediate native backup 2026-10-25T11-07-28-849.sqlite.sqlite. Demo farm 89, field 98 and aircraft 92 retain their identities. Existing null imagery metadata stays null. The marketing homepage and the new deployment docs section return HTTP 200. Scheduled planning remains separate from physical dispatch.