fix(firstleg): expose container documents and aggregate departure gates

2026-08-26 13:07:30 +08:00
parent 1584c7a0a3
commit fc0a6ea7ca
22 changed files with 407 additions and 39 deletions
@@ -37,6 +37,7 @@ paths:
  /api/platform/v1/first-leg/outbound-dispatches/{containerBookingId}/gate:
    get:
      summary: Evaluate every inbound binding in the fail-closed container outbound gate
+      description: Loading evidence is evaluated once for the physical container/loading plan and the same result applies to every inbound binding. Customs clearance is also resolved once at container scope. A missing standalone sailing schedule is reference-only and never affects gate.passed.
      x-permission: platform:firstleg:outbound-dispatch:check
      parameters:
        - {$ref: '#/components/parameters/ContainerBookingIdPath'}
@@ -98,7 +99,7 @@ components:
        loadingPlanId: {type: integer, format: int64}
        loadingPlanStatus: {type: string}
        oceanBookingId: {type: integer, format: int64, nullable: true}
-        oceanBookingStatus: {type: string, nullable: true}
+        oceanBookingStatus: {type: string, nullable: true, description: Booking reference retained independently from the non-blocking standalone sailing schedule}
        truckAppointmentId: {type: integer, format: int64, nullable: true, description: Reference-only truck appointment; absence never blocks manual outbound confirmation}
        truckAppointmentStatus: {type: string, nullable: true, description: Reference-only status; PENDING or any non-terminal state never affects gate.passed}
        dispatchStatus: {type: string, description: One visible container-level status}