feat: show shortage names and explain unavailable delivery results

capabilities/am516-delivery-prediction/docs/acceptance_samples.md

@@ -26,6 +26,8 @@ Expected:
 - Feishu output uses rich-text `post`; the report title, overall-judgment heading, numbered candidate headings, and unavailable-candidate heading are bold;
 - the judgment level and fixed disclaimer provide the global human-review boundary;
 - inventory output is limited to summary-level available quantity and coverage; non-reducer shortage output never exposes material codes or raw ERP details;
+- each usable model includes `缺料物料明细` listing only names from the API shortage records (`物料名称`, with `缺料物料名称` as the fallback), preserving order and deduplicating names; the same behavior applies to continuation replies;
+- missing names are reported explicitly without substituting codes or inferring names; an empty shortage list says `API未返回缺料记录`, and missing shortage data or invalid BOM keeps the unavailable-data reminder;
 - reducer shortages are the sole exception: when `缺料物料` starts with `20.30.`, output only the reducer code, inventory, inspection, in-transit, existing-demand quantities, and in-transit coverage conclusion in the Skill-defined order;
 - shortage items outside the `20.30.` reducer prefix never expose their material codes or quantity details;
 - result is marked as internal candidate;
@@ -38,7 +40,7 @@ Expected:
 - the appended record contains query metadata, model parsing, and a complete Markdown table with one row per model queried in the current batch;
 - each future appended candidate row records the same query-completion time in `YYYY-MM-DD HH:mm:ss +0800` form (with the actual local UTC offset), without rewriting or backfilling historical records;
 - record-table columns follow this order: 序号、记录时间、型号、推荐类型、差异项、API状态、AM516预测交期、可用库存、主导因素;
-- unavailable candidates remain in their original rule order and are recorded as `❌ 不存在` with unavailable result fields shown as `—`;
+- unavailable candidates remain in their original rule order and are recorded as `❌ 不可用` with unavailable result fields shown as `—`; lack of a result does not itself establish that the model does not exist;
 
 ## Sample 1B | API Workdays And Final Delivery Date
 
@@ -51,6 +53,9 @@ Rules and expected results:
 - a valid API date in another calendar year remains usable without a local holiday calendar;
 - accept zero workdays; reject negative, fractional, boolean, or non-numeric workday values and invalid dates;
 - if either new field is missing or invalid, report the lead-time result as unavailable instead of falling back to old fields or estimating;
+- a stopped original-model reply includes `原因：` identifying each missing, empty, or invalid field and a suggestion to check the API data; no record is appended;
+- each unavailable candidate is listed with its own reason; HTTP 404 or missing fields must not be summarized as a confirmed nonexistent model;
+- controlled-query failures show their safe category (configuration, authentication/permissions, HTTP, TLS, DNS/network, timeout, or JSON format), without displaying raw response bodies or secret-bearing error strings;
 - choose the fastest candidate using the API workday count, even when the natural-day totals would rank candidates differently.
 
 ## Sample 1A | Continue With Other Candidates