优化

firstleg/src/main/resources/openapi/firstleg-v1.yaml

@@ -523,26 +523,6 @@ paths:
         content: {application/json: {schema: {$ref: '#/components/schemas/SmartLoadingWarehouseRemarkRequest'}}}
       responses:
         '200': {description: 成功或业务失败，data 为最新 SmartLoadingPlan}
-  /api/platform/v1/first-leg/smart-loading/plans/{planId}/push-preload:
-    post:
-      summary: 推送智能装柜计划到预装清单
-      description: >-
-        需要 platform:firstleg:smart-loading:push 权限。push-preload 不要求真实柜号，
-        只冻结 EDITING 柜次计划的明细并建立稳定预装关联，不创建 PDA 作业任务；计划必须处于 EDITING 且版本匹配。
-        预装页面随后补录真实柜号；只有预装 CONFIRMED、真实柜号存在、已关联 RELEASED 订舱时才创建待领取 PDA 任务，领取后才进入 LOADING。
-        智能装柜首次分配会创建入库单级 PENDING 预装聚合；push 会在同一事务内对全部实际分配再次确保该聚合存在且仍为 PENDING，
-        但不会覆盖 CONFIRMING/CONFIRMED 记录，也不会在 LOADING 后补建。
-        推送事务会先为所有已分配入库单建立 PENDING 预装计划与 EDITING 柜次计划的正式关联，
-        任一关联缺失、版本冲突或分配数量为零都会整体失败并禁止 PDA/LOADING；不得在 LOADING 后补关联。
-      parameters:
-        - {name: planId, in: path, required: true, schema: {type: string, pattern: '^[1-9][0-9]*$'}}
-        - {$ref: '#/components/parameters/IdempotencyKey'}
-      requestBody:
-        required: true
-        content: {application/json: {schema: {$ref: '#/components/schemas/SmartLoadingPushRequest'}}}
-      responses:
-        '200': {description: 推送成功或业务失败，按响应体 code 判断}
-        '403': {description: 无智能装柜推送权限}
   /openapi/v1/inbound-measurements:
     post:
       summary: 提交一条第三方箱规测量结果和一张图片
@@ -1651,11 +1631,6 @@ components:
       properties:
         version: {type: integer, minimum: 0}
         data: {$ref: '#/components/schemas/ContainerSaveRequest'}
-    SmartLoadingPushRequest:
-      type: object
-      required: [expectedVersion]
-      properties:
-        expectedVersion: {type: integer, minimum: 0}
     SmartLoadingAssignRequest:
       type: object
       required: [inboundId, inboundDetailId, packageCount, expectedVersion, operationId]

firstleg/src/main/resources/openapi/loading-lists-v1.yaml

@@ -49,7 +49,7 @@ paths:
     patch:
       summary: 修改预装运输信息
       description: >-
-        已推送后可在 EDITING 或 LOADING 阶段首次补录真实集装箱号；已有柜号的纠正仅限仍为 EDITING、PDA任务尚未领取且无任何物理作业事实时，并必须提供原因和当前版本；
+        可在 EDITING 或 LOADING 阶段首次补录真实集装箱号；已有柜号的纠正仅限仍为 EDITING、PDA任务尚未领取且无任何物理作业事实时，并必须提供原因和当前版本；
         containerNo 为 null 表示保持当前值，非空时服务端移除格式空白、转大写并校验ISO 6346结构、设备类别和校验位，空白字符串非法且禁止清空。
       x-permission: platform:firstleg:preload:edit
       parameters:
@@ -301,9 +301,8 @@ components:
         readiness: {$ref: '#/components/schemas/PreloadReadiness'}
     PreloadReadiness:
       type: object
-      required: [preloadPushed, containerNoReady, preloadLinkCount, confirmedPreloadCount, confirmationStatus, canConfirm, readyForPda, blockingReasons]
+      required: [containerNoReady, preloadLinkCount, confirmedPreloadCount, confirmationStatus, canConfirm, readyForPda, blockingReasons]
       properties:
-        preloadPushed: {type: boolean, description: 是否已完成 push-preload}
         containerNoReady: {type: boolean, description: 是否已录入真实集装箱号 containerNo}
         preloadLinkCount: {type: integer, format: int32, minimum: 0, description: 计划关联的入库预装票据数}
         confirmedPreloadCount: {type: integer, format: int32, minimum: 0, description: 已确认预装票据数}
@@ -317,7 +316,7 @@ components:
         blockingReasons:
           type: array
           description: 阻止计划确认的稳定原因码
-          items: {type: string, enum: [PRELOAD_NOT_PUSHED, LOADING_PLAN_NOT_EDITING, PRELOAD_LINK_MISSING, OCEAN_BOOKING_NOT_LINKED, OCEAN_BOOKING_NOT_RELEASED, PDA_TASK_ALREADY_CREATED, PRELOAD_ALREADY_CONFIRMED]}
+          items: {type: string, enum: [LOADING_PLAN_NOT_EDITING, PRELOAD_LINK_MISSING, OCEAN_BOOKING_NOT_LINKED, OCEAN_BOOKING_NOT_RELEASED, PDA_TASK_ALREADY_CREATED, PRELOAD_ALREADY_CONFIRMED]}
     ConfirmPreloadRequest:
       type: object
       required: [expectedVersion, operationReason]

firstleg/src/main/resources/openapi/phase3-loading-model-bridge-v1.yaml

@@ -2,7 +2,7 @@ openapi: 3.0.3
 info:
   title: Phase 3 Preload and Container Loading Bridge API
   version: 1.0.0
-  description: Links must be created while preload=PENDING and loadingPlan=EDITING. Smart-loading push creates all allocated links atomically before any PDA task creation; push-preload never requires containerNo and never advances LOADING. LOADING plans cannot be repaired through post-hoc binding.
+  description: The container loading plan is created atomically with the container. Adding an inbound allocation creates its preload aggregate and link in the same transaction while loadingPlan=EDITING or LOADING; plan confirmation remains the gate before PDA task creation.
 paths:
   /api/platform/v1/inbounds/{inboundId}/preload/loading-plans:
     get: