指令问题修复

schemas/standard_system_operation.schema.json

@@ -2161,7 +2161,7 @@
     "An HTTP 200 response without an explicit success signal and a matching fresh requery is never a completed lifecycle write.",
     "For shared-plan order_cancel, the adapter must discover every concrete child from a fresh SP_OrderList response, fetch every child detail afresh, and require every child status to equal 已取消 before completion.",
     "Shared-plan order_restore restores only the parent; every child status must be re-read and no child may be reported restored without its own order_restore operation.",
-    "Update parsing preserves all recognized business-visible targets and allows multiple actions; the browser adapter automatically submits only its live-validated target map (currently independent twin_room_count, rooms.SGL, rooms.TWN and the mapped passenger counts, shared-plan planned_capacity and shared-child lodging_note), while other recognized targets require manual review. Exact clear_generated_zero receivable cleanup remains a separate internal operation on the same route.",
+    "Update parsing preserves all recognized business-visible targets and allows multiple actions; the browser adapter automatically submits only its implemented target map (currently independent twin_room_count, rooms.SGL, rooms.TWN, rooms.DBL and the mapped passenger counts, shared-plan planned_capacity and shared-child lodging_note; newly mapped room and passenger counts still require authorized live ERP validation), while other recognized targets require manual review. Exact clear_generated_zero receivable cleanup remains a separate internal operation on the same route.",
     "Arrangement create uses status 未安排 for hotels and 未确认 for other arrangement types. Arrangement update targets one exact existing hotel row, status 未安排 or 未确认. Legacy updates change end_date/room_count at slot 0; Program date-selected updates may replace resource and its ERP-linked room_type plus room_count at the resolved slot. Program-only guide/vehicle/transport/other replacements now target a unique existing record; dates only locate it. Native selection supplies linked fields, optional fields remain unchanged when omitted, payment/audit/confirmed/realized guards and historical test-context restrictions still apply.",
     "A multi-date shared_plan_create carrying customer/passenger split facts remains restricted to the explicit shared_batch_split_order_probe test context; E2E3/E2E4 established the ERP behavior, but ordinary release still requires business approval and every date must retain native response plus object-level requery.",
     "confirmation_export reads and validates the ERP source; visitor-list retains the original ERP XLS as a platform archive artifact and generates a real XLSX delivery artifact, with AgentBus/WeChat limited to the XLSX. If XLSX conversion fails, external attachment delivery is blocked instead of returning the raw XLS. Other types are converted to PDF before attachment delivery and fall back to their source file if conversion fails. It must not accept a requested output format or claim scheduling or external delivery."