fix: use release-local Bun for scheduled work

Summary

Use the maintained ts-cloud 0.16.70 release for Open Farming's scheduled work. Remove the obsolete 0.16.11 override and explicitly assign the single scheduler to the main site's release-local Pantry runtime.

main release -> pantry/.bin/bun -> native scheduler -> app/Scheduler.ts
api release  -> API service

The source fix was released through native bun run release:patch in ts-cloud #198. This app consumes the public package through a normal Bun update and frozen lockfile install.

Refs #42 and stacksjs/ts-cloud#197.

Evidence

• Before: live scheduler uses host Bun 1.4.2 while main and API use private Bun 1.4.4; the app override resolves ts-cloud 0.16.11.
• After: native installed SDK/core/AWS types all resolve 0.16.70. Fresh public consumer exercises eight deployment combinations and ten actual native scheduler/queue entry cases, including contained runtime aliases and rejected missing, mismatched, escaped and wrong-PATH runtimes. Published type checks and archive integrity pass.
• App lint and typecheck pass. All 114 tests pass with 3,564 assertions. Native docs build renders 54 pages, including the scheduler guidance. Independent standards and specification reviews cover the pinned authored change.
• Live customer-row fingerprints retained before publication. Actual deployed scheduler/child runtime and customer-data comparison remain post-deploy acceptance gates.

Merge Danger

Door: Two-way.

Blast Radius: Deployment.

The adopted source reconciles stale background units even when a site's desired set is empty and fails deployment if a managed service refuses to stop. A failed replacement after draining can need a recovery deploy. This change explicitly preserves one main scheduler and leaves the API without a second copy. Scheduler planning records do not dispatch aircraft or mark flights complete.