大交通检索修复

mappings/lifecycle.mapping.json

@@ -1,7 +1,7 @@
 {
   "contract_version": "ltjt-lifecycle-v2.9-roster-leader-contact-2026-08",
   "current_agent_parse_prompt_version": "ltjt-agent-prompt-v1.8-independent-headcount-categories",
-  "current_extension_version": "0.5.185",
+  "current_extension_version": "0.5.186",
   "original_arrangement_date_selection": "Hotel, vehicle, transport and other/filing update selection accepts MM-DD or YYYY-MM-DD; omitted year matches original ERP month/day within the exact group only. Require exactly one persisted row, then freeze its actual full dates and id. Full year is exact; mixed/cross-year endpoints are matched independently with actual range order checked. No match or ambiguity blocks before mutation; show up to five original candidates and ask to resubmit complete dates. Creation and legacy target-date changes retain existing semantics.",
   "historical_test_marker": "TEST-202609",
   "scope": "/System/Business/",
@@ -384,7 +384,7 @@
     "arrangement_transport": {
       "page": "/System/Business/teams_piao.asp",
       "action": "DoInfo_piao",
-      "ticket_description_filter": "Optional arrangement.ticket_description for create/update; normalized description substring AND supplier query on the same native candidate, unique result only. Omission retains native first-match behavior. Keyword is separate from ERP-derived item and original-date selection; revalidate before mutation. No new database migration; real ERP acceptance pending.",
+      "ticket_description_filter": "Optional arrangement.ticket_description for create/update; normalized description substring AND supplier query on the same native candidate, unique result only. Whitespace/brackets/case/full-width differences are ignored, but numeric boundaries use original label positions: C91 followed by a separated timetable can match C91, while C911 cannot. Route alone is sufficient only when unique; ambiguity stops before mutation and returns up to five bounded supplier/description candidates without internal IDs or prices. Omission retains native first-match behavior. Keyword is separate from ERP-derived item and original-date selection; revalidate before mutation. No new database migration; real ERP acceptance pending.",
       "fields": {
         "supplier.name": "danwei0",
         "supplier.id": "danweiid0",