Repository navigation
Conversation
- 新增 E 补货决策边界文档(instock=累计入库、inventory/receipt 未接入、超发错抵、QC 门、Closed stage3)→ docs/solutions/architecture-patterns/ - 新增 SO→DN→货代 job→ZMT Snapshot 查询链(用 job 不是 tracking)→ docs/solutions/integration-issues/ - 更新 produced_qty 参考,补「工序完成/完工入库/可发」三层口径 → supply_chain_visibility/docs/reference/ - 更正 README/AGENT_HANDOFF 的生产部署状态与 E 覆盖边界 - 级联更新 solutions / module 索引与日志、CONCEPTS、skill 链接 已同步更新根目录索引。无客户数据/凭证;无隐私外泄。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
做了什么
docs/solutions/architecture-patterns/en-supply-line-e-replenishment-decision-boundary.md—— EN「供给线 E」(
key_test.so_chain) 用于补货/下单决策的边界:instock是累计入库不是可用库存、inventory/receipt=not_integrated、超发负open_qty会错抵需求、质检未放行、Closed 落 stage 3、partial只警示不阻断、千单性能未验证。含 P0/P1 改进清单。docs/solutions/integration-issues/en-so-dn-forwarder-job-status-lookup.md—— SO→DN→
Shipment→货代 job→ZMT Shipment Snapshot查询链;Snapshot 用job不是tracking;Shipment.status长期 Draft;签收为货代回传;同票 ETA 可多源冲突。supply_chain_visibility/docs/reference/en-produced-qty-vs-jobcard.md,补 §7「工序完成 / 完工入库 / 可发」三层口径。supply_chain_visibilityREADME / AGENT_HANDOFF:生产已部署(实测 200);线上 E 已有shipment_progress,但库存/收货仍未接入;
WO.status不可信而produced_qty可信。CONCEPTS.md、erpnext-wo-auditskill 链接,重建根索引。为什么
2026-11-12 按三张 SO 查生产/出库/在途,并由独立 Codex worker 只读复核。复核纠正了
「完工未入库」「停 2 个月」「E 只到 DN」「全部签收」等口径,并把「E 能不能直接做补货决策」
这个边界固定下来,避免下一个 Agent 重复踩坑。
怎么测
python scripts/update_index.py→ 41 modules / 676 docspython scripts/check_solutions_health.py --strict→ 通过(索引/平表/篇数/链接一致,孤儿 0)python scripts/check_secrets.py→ OK(649 files,无明文凭证)遗留
key_test__so_chain.py是 v4,线上版本已超过它(shipment_progress/partial/qc_*)。待把线上源码同步回仓库后再做代码级评审。