fix: adopt released native runtime APIs

Summary

Drone needed copied process, filesystem, JSON and stream implementations because its installed framework lacked the required public exports. Consume released Stacks 0.75.301 and auto-import generator 0.4.5, retire all six bridge implementations, and preserve application authority, deadlines, private publication and exact-view stream credit.

copied runtime bridges -> maintained public package exports
native generation -> consistent first-registered export selection
Bun 1.4.4 -> explicit patrol engine support and requalified encoder bound

The native upgrade also synchronizes framework defaults and generated declarations. Keep the immutable maintained TUF 6.0.1 archive and BunPress 0.2.25. Patrol replay still requires the exact recorded runtime and fresh consent. Setup documentation now matches Bun 1.4.4.

Evidence

• Source releases have passing exact-source CI and public package integrity/readback. Native requested-version upgrade, targeted transitive generator update and frozen Bun/Pantry installs were used without distribution patches.
• Before: duplicate generated exports prevented a cold function-barrel import. After: native generation and an actual fresh import expose 1,050 runtime exports. Native docs build renders 100 pages; browser keyboard search opens the correct /docs result without warnings/errors.
• Pickier reports zero errors/warnings. App/runtime/view types, roadmap/parity checks, five docs-search tests and 13 camera-helper tests pass. Both independent review axes pass all 55 authored paths.
• All eight copied standalone update/trust/SDK/store/preparation/candidate/host-slot/maintenance campaigns pass on the rebuilt executable. Copied patrol commands record and exactly replay an actual Bun 1.4.4 neutral dataset, then reject a copy marked with another supported runtime after raw manifest hashes are updated.
• The actual encoder/runtime proof retains the 26,995,930-byte managed bound and all eight encoder/profile source hashes. CI now repeats that proof with exact Bun revision and architecture guards.
• Lifetime diagnostics preserve native exit/signal/watchdog state and failed fixtures without changing the 60-second retention, stop grace, assertions or test guards. A real evidence-write fault reproduced lost forensic data; the corrected cleanup retains the database and surviving evidence after the same successful child.

Final qualification passes at 06547e6f292ed7e85571d6ab94e5fc694f3bf999: the Mac native Buddy suite reports 2,187 passed, 28 platform skips, zero failed and 523,013 assertions across 248 files. Exact-head CI passes all five jobs, including its Linux full suite (2,174 passed, 41 skips, zero failed), native browser jobs, firmware cross-compilation, filesystem isolation and copied standalone CLI campaigns. The complete original CI archive and local output are retained with hashes.

The earlier local full run remains incomplete and failed: it was stopped after actual disk exhaustion and also reported a near-expiry lifetime read failure. Its original output is retained, and #60 remains unresolved. The new full passes do not establish that earlier failure's cause.

Closes #109. No physical commissioning is inferred.

Merge Danger

Door: Two-way source/dependency adoption. Retain the matching executable for recorded-runtime replay; no replay version conversion is introduced.

Blast Radius: Runtime. Framework defaults and the installed dependency graph change across application boot, commands and private artifact operations. Existing independent authority and inhibited physical outputs remain intact. No physical flight, hardware power-loss or complete bundled-server deployment qualification is claimed.