🐛 修正基线建表脚本与迁移脚本不一致

- blade_customer_archive：补 kingdee_status / kingdee_fail_reason / kingdee_sync_time
  与 idx_kingdee_status（迁移 20260917 已加，基线漏写，新环境按基线建库会缺列）
- blade_invoice_receipt：删掉 20260923 已废弃的 kingdee_bill_no / kingdee_status
  与 idx_invoice_receipt_kingdee（迁移里已 DROP，基线仍在声明）
- 依据：scripts/repo/audit-migrations.py 从「缺列(建表语句) 2 + 基线脚本未同步 3」跑到 ✅

doc/sql/transport/blade_customer_archive.sql

@@ -40,6 +40,9 @@ CREATE TABLE `blade_customer_archive` (
   `current_node` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT NULL COMMENT '当前节点',
   `current_processor` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT NULL COMMENT '当前处理人',
   `approved_time` datetime NULL DEFAULT NULL COMMENT '审核通过时间',
+  `kingdee_status` varchar(20) NOT NULL DEFAULT 'none' COMMENT '金蝶协同状态：none未推送/exist金蝶已有/synced已推送/failed推送失败',
+  `kingdee_fail_reason` varchar(500) NULL DEFAULT NULL COMMENT '金蝶推送失败原因',
+  `kingdee_sync_time` datetime NULL DEFAULT NULL COMMENT '金蝶推送时间',
   `create_user` bigint NULL DEFAULT NULL COMMENT '创建人',
   `create_dept` bigint NULL DEFAULT NULL COMMENT '创建部门',
   `create_time` datetime NULL DEFAULT NULL COMMENT '创建时间',
@@ -51,7 +54,8 @@ CREATE TABLE `blade_customer_archive` (
   UNIQUE KEY `uk_customer_archive_code` (`tenant_id`, `customer_code`, `is_deleted`) USING BTREE,
   UNIQUE KEY `uk_customer_archive_credit_code` (`tenant_id`, `unified_credit_code`, `is_deleted`) USING BTREE,
   KEY `idx_customer_archive_access` (`tenant_id`, `access_type`, `approval_status`) USING BTREE,
-  KEY `idx_customer_archive_name` (`tenant_id`, `full_name`, `short_name`) USING BTREE
+  KEY `idx_customer_archive_name` (`tenant_id`, `full_name`, `short_name`) USING BTREE,
+  KEY `idx_kingdee_status` (`kingdee_status`) USING BTREE
 ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_general_ci COMMENT = '客商档案';
 
 -- ----------------------------