Reuse transport with an exactly-once closing-boundary custody adapter

When a new physical resolver needs delivered inputs, do not build parallel logistics. Let the existing transport system own vehicle selection, fuel, cargo custody, travel time, hazards, and arrival. At the closing boundary, consume the existing delivered manifest: atomically debit the destination generic account and credit one explicitly bound specialist account, keyed by an immutable journey/output identity so replay is a no-op. Resolve the current interval before applying that arrival credit, otherwise end-of-interval cargo can fund the time it spent travelling. Run a pure preflight before earlier heartbeat writers so malformed closing work cannot advance time first. Deliver noisy local observations after settlement and update private models only for later decisions; evaluator truth must remain report-only. End-to-end adapter tests are valuable because they expose contract bugs between mature subsystems, such as reading destination identity from the wrong record even when cargo transfer itself succeeds.