Connect group allied transit custody

docs/CURRENT_STATUS.md

@@ -28,6 +28,11 @@ the original cache to a hand; that acquisition is staged, not a played purchase.
 
 **Larger-alliance integration groundwork — 28 October.** Movement-end warnings
 and losses for current games now use the shared group-capable separation quote.
+Territory entry and Basic shipment visitor custody now also recognize each
+member of an unexposed group, including a concealed zero marker. Focused
+engine cases stage the group and forces because live Nexus formation is not
+yet connected; they exercise real shipment, movement and turn-end actions. The
+related eight-file batch passes 53 cases, including existing pair behavior.
 The three-member option remains unexposed: consent, faction benefits, funding,
 movement and battle paths are not yet integrated for groups.
 
@@ -119,10 +124,10 @@ A usable preview must connect every group member to native
 alliance consent, movement and battle restrictions, funding, faction ally
 benefits, victory and minimal legal AI. Consent, leaving behavior and shared
 benefit allocation are provisional online conventions. No group option is
-enabled or claimed complete by the standalone foundation. The shipment helper
-now models several witnesses and one physical baseline, with the existing pair
-engine using the same quote. Group receipts, separation, Nexus, funding and
-other engine paths still need integration before the option can be offered.
+enabled or claimed complete by the standalone foundation. Shipment entry and
+visitor consequences now use the group-aware receipt and physical baseline.
+Nexus, funding and other engine paths still need integration before the option
+can be offered.
 Unconnected Nexus controls and a funding quote now model unanimous consent,
 explicit donor allocations and edge-bound pledge authorizations. The engine
 still must issue and revoke unique edge authorizations, settle and refund