[FEATURE] Expose loading dock state and vehicle occupancy

[ifBars]

What would you like to see?

Add a managed LoadingDock wrapper reachable from S1API property and delivery surfaces.

The initial wrapper should expose:

• stable GUID and display name;
• the owning PropertyWrapper when available;
• wrapped input and output ItemSlotInstance collections;
• accepting-items and destroyed state;
• wrapped static and dynamic LandVehicle occupants;
• occupancy and accepting-state change notifications;
• enumeration of a property's loading docks.

Why would this help?

The delivery API exposes only LoadingDockIndex, and PropertyWrapper exposes only LoadingDockCount. Automation, warehouse, delivery UI, and vehicle-routing mods still need the native ScheduleOne.Delivery.LoadingDock to inspect the actual dock, its transit slots, and its current vehicle.

Extra Context (Optional)

Keep the first version observational except for native authority-safe state already intended for public use. Custom dock creation, GUID mutation, delivery rerouting, outline UI, and direct transit-network calls should remain out of scope.

Validate deferred property resolution, vehicle arrival/departure, save reload, and host/client state separately on Mono and IL2CPP.

[ifBars]

Implementation plan

I traced the current stable API plus the native Mono and IL2CPP ScheduleOne.Delivery.LoadingDock shapes before choosing the seam. The native dock owns its GUID/name, parent property, transit slots, accepting/destroyed flags, and separate dynamic/static occupants. Dynamic occupancy changes in RefreshOccupant through SetOccupant; delivery arrival/departure changes static occupancy through SetStaticOccupant. Both runtimes expose the same callable seams.

Public API

• Add a cached, read-only S1API.Deliveries.LoadingDock wrapper so the same native dock reached through different API paths shares wrapper identity and event subscriptions.
• Expose GUID, Name, nullable owning PropertyWrapper, immutable managed snapshots of InputSlots and OutputSlots, IsAcceptingItems, IsDestroyed, IsInUse, and nullable managed DynamicOccupant / StaticOccupant values.
• Reuse ItemSlotInstance and cached LandVehicle wrappers; no native or generated IL2CPP types will cross the public boundary.
• Add instance notifications for dynamic occupancy, static occupancy, and accepting-items transitions, including previous/current managed values and suppressing no-op assignments.
• Add PropertyWrapper.LoadingDocks for property enumeration and Delivery.LoadingDock for the selected destination/index. Both will resolve defensively while the property graph is still hydrating.

Native integration

• Keep the surface observational: no GUID mutation, custom dock creation, rerouting, outline controls, transit insertion helpers, or new authority-changing setters.
• Patch only LoadingDock.SetOccupant, LoadingDock.SetStaticOccupant, and the IsAcceptingItems setter, capturing old state before the native call and publishing after a real change.
• Keep wrapper/cache lifecycle bounded across destroyed docks and scene/save transitions so stale native proxies are not retained.

Regression coverage

• Add compile/reflection contracts for every public member, managed argument type, nullability shape, and event signature.
• Add focused bridge tests for dynamic/static arrival and departure, accepting-state changes, no-op suppression, shared wrapper identity, property/delivery navigation, and empty/deferred collections.
• Preserve all existing public APIs and document source, binary, behavioral, save, and network compatibility as additive/unchanged.

Validation

• Restore, build, and run the full S1API test suite sequentially for MonoMelon and Il2CppMelon.
• Run DocFX/public-documentation coverage and ApiCompat against stable.
• Run loaded-save smoke coverage separately on Mono and IL2CPP for property enumeration, deferred owner resolution, slot wrapping, dynamic vehicle arrival/departure, static delivery-vehicle arrival/departure, and save reload.
• Run same-backend two-peer host/client checks for both runtimes, recording dock/vehicle identity and event transitions independently on each side. The events will report locally observed native state; they will not introduce a new network protocol.
• Keep game assemblies, generated wrappers, saves, probes, logs, and screenshots local and out of the PR.

If implementation reveals that a native transition bypasses these verified setters, I will update this comment with the narrower additional seam before expanding the patch.