fix(firstleg): decouple manual container nodes from tracking

firstleg/src/main/resources/db/phase3-carrier-schedule-query-schema.sql

@@ -114,7 +114,8 @@ CREATE TABLE IF NOT EXISTS fl_carrier_schedule_query_history (
 
 CREATE TABLE IF NOT EXISTS fl_carrier_schedule_node_fact (
   id BIGINT UNSIGNED NOT NULL COMMENT '标准船节点事实ID',
-  query_id BIGINT UNSIGNED NOT NULL COMMENT '所属查询任务ID',
+  query_id BIGINT UNSIGNED NULL COMMENT '自动跟踪任务ID；人工补录时为空',
+  container_booking_id BIGINT UNSIGNED NOT NULL COMMENT '所属真实货柜ID',
   event_key VARCHAR(192) NOT NULL COMMENT '供应商编码与供应商事件ID组成的幂等键',
   provider_code VARCHAR(32) NOT NULL COMMENT '轨迹供应商编码',
   provider_event_id VARCHAR(128) NOT NULL COMMENT '供应商稳定事件ID',
@@ -130,9 +131,11 @@ CREATE TABLE IF NOT EXISTS fl_carrier_schedule_node_fact (
   raw_payload_hash CHAR(64) NOT NULL COMMENT '原始响应SHA-256；不保存敏感原文',
   created_at DATETIME(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3) COMMENT '事实入库时间',
   PRIMARY KEY (id),
-  UNIQUE KEY uk_carrier_schedule_node_event (query_id,event_key),
+  UNIQUE KEY uk_carrier_schedule_node_event (container_booking_id,event_key),
   KEY idx_carrier_schedule_node_timeline (query_id,node_sequence,observed_at,id),
+  KEY idx_container_shipping_node_timeline (container_booking_id,observed_at,id),
   CONSTRAINT fk_carrier_schedule_node_query FOREIGN KEY (query_id) REFERENCES fl_carrier_schedule_query(id),
+  CONSTRAINT fk_carrier_schedule_node_container FOREIGN KEY (container_booking_id) REFERENCES fl_container_booking(id),
   CONSTRAINT chk_carrier_schedule_node_standard CHECK
     (standard_node IN ('DEPARTED_WAREHOUSE','AT_ORIGIN_PORT','LOADED_ON_VESSEL','DEPARTED_ORIGIN_PORT',
       'IN_TRANSIT','ARRIVED_DESTINATION_PORT','DISCHARGED_FROM_VESSEL','PICKUP_READY','PICKED_UP','EMPTY_RETURNED')),

firstleg/src/main/resources/openapi/carrier-schedule-query-v1.yaml

@@ -65,17 +65,6 @@ paths:
         '200':
           description: Stable task detail
           content: {application/json: {schema: {$ref: '#/components/schemas/DetailEnvelope'}}}
-  /api/platform/v1/carrier-schedule-queries/containers/{containerBookingId}/ensure:
-    post:
-      summary: Idempotently ensure the carrier task for a departed container before manual entry
-      x-permission: platform:firstleg:port-schedule-query:manual
-      parameters:
-        - {name: containerBookingId, in: path, required: true, schema: {type: integer, format: int64, minimum: 1}}
-        - {$ref: '#/components/parameters/IdempotencyKey'}
-      responses:
-        '200':
-          description: Existing or newly created task detail; platform-owned consolidated bookings use customerId 0
-          content: {application/json: {schema: {$ref: '#/components/schemas/DetailEnvelope'}}}
   /api/platform/v1/carrier-schedule-queries/{queryId}/history:
     parameters: [{$ref: '#/components/parameters/QueryId'}]
     get:

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

@@ -14,6 +14,7 @@ paths:
   /api/platform/v1/terminal-drayages/{containerBookingId}:
     get:
       summary: 查询单柜码头拖车详情
+      description: 已确认国内离仓的货柜即使船节点跟踪任务尚未建立也返回WAITING_FOR_ARRIVAL空详情；实际操作仍按到港、清关和卸柜节点校验
       x-permission: platform:firstleg:terminal-drayage:list
       parameters: [{$ref: '#/components/parameters/ContainerBookingId'}]
       responses: {'200': {$ref: '#/components/responses/ViewResponse'}}
@@ -63,6 +64,7 @@ paths:
   /api/platform/v1/terminal-drayages/{containerBookingId}/emails:
     get:
       summary: 查询最近100封车队邮件及发信开关
+      description: 已确认国内离仓的货柜允许读取空邮件列表，不以船节点跟踪任务是否已经建立作为货柜存在性条件
       x-permission: platform:firstleg:terminal-drayage:list
       parameters: [{$ref: '#/components/parameters/ContainerBookingId'}]
       responses: