feat: add record time to delivery prediction records
This commit is contained in:
@@ -33,7 +33,8 @@ Expected:
|
||||
- when the full report exceeds one Feishu rich-text message, it is split into ordered continuation posts and no candidate is dropped;
|
||||
- record is appended.
|
||||
- the appended record contains query metadata, model parsing, and a complete Markdown table with one row per queried candidate;
|
||||
- record-table columns follow this order: 序号、型号、推荐类型、差异项、API状态、AM516预测交期、可用库存、主导因素;
|
||||
- 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 `—`;
|
||||
|
||||
## Sample 2 | Missing Quantity
|
||||
|
||||
Reference in New Issue
Block a user