docs(catalog): align pattern details order with the catalog table - #4324
huangruiteng merged 1 commit into
Conversation
The catalog keeps two ordered views of the same patterns: the per-family catalog table and the Pattern Details block. Two families disagreed, so the details order did not mirror the table it summarizes. Work Routing lists IP-029 Handoff Todo Gate State in its table and in the pattern-to-canary matrix, and the IP-026 cross-references describe it as a routing gate, but the details block placed it under Human Decision. Move the IP-029 detail entry into the Work Routing block, between IP-003 and IP-021. State And Boundary lists IP-026 Agent-Scoped No-Candidate Gap as a P0 row directly after IP-006, but the details block placed it after IP-022, inside the P1 group, so a P0 boundary pattern read as if it were P1. Move the IP-026 detail entry to sit after IP-006 and before IP-011. Both entries are relocated verbatim. No IP wording, priority, or family membership changes, and the file keeps its line multiset (190 insertions against 190 deletions). Signed-off-by: BigDataDZ <76271875+BigDataDZ@users.noreply.github.com>
ccd3841 to
c2fe2f5
Compare
huangruiteng
left a comment
There was a problem hiding this comment.
动机
该 PR 修正目录表格与 Pattern Details 之间的展示顺序:IP-029 应归入 Work Routing,IP-026 应归入 State And Boundary。目标是让读者从每个 family 的目录表进入详情时看到一致的顺序;不改变任何模式内容、优先级或语义。
改动思路
改动只在 docs/concepts/interaction-pattern-catalog.md 内移动两个完整详情块:将 IP-029 放到 Work Routing 的目录位置,将 IP-026 放到 State And Boundary 的目录位置。采用整块原文搬移而非重写,降低链接、契约和示例内容漂移的风险。
具体改动
- 单文件
190 insertions / 190 deletions,独立Counter比较确认当前文件与origin/main的 2445 行 line multiset 完全相同。 - 逐 family 结构检查确认五个目录表的条目顺序与对应 Pattern Details 顺序一致;IP-029 位于 Work Routing,IP-026 位于 State And Boundary。
interaction-pattern-catalog-smoke.py通过,git diff --check通过,git merge-tree --write-tree origin/main HEAD无冲突。
对主干的风险
没有发现可归因于该 exact head 的阻塞 finding。由于内容是逐块搬移,模式文本、代码引用、验证清单和优先级没有变化;风险主要是 Markdown 锚点或 family 边界误移,已由 line-multiset 与 family-order 两个独立检查覆盖。GitHub 将分支标为 BEHIND 但仍 MERGEABLE,未发现内容冲突。
loopx check --scan-path docs/concepts/interaction-pattern-catalog.md 的整体命令同样受到本机全局 registry 中无关的缺失字段错误影响;public-boundary scan clean,目录专用 smoke、line-multiset 和 family-order 检查均通过。这不构成该文档搬移的回归证据。
我的整体评价
没有阻塞 finding。该 PR 以最小、可回滚的文档搬移恢复了目录与详情的 family 顺序一致性,且证明没有增删内容或改变行为。结论:批准该 exact head c2fe2f583d5807f96ab9c78d9f2023fbed61533e。
English verdict: APPROVE: Exact head c2fe2f583d5807f96ab9c78d9f2023fbed61533e is a relocation-only catalog fix. The 2445-line multiset is unchanged, family-order and catalog smoke checks pass, and the branch is mergeable without conflicts. The repository-wide check saw unrelated registry baseline errors but a clean public-boundary scan; no blocking finding is attributable to this PR.
Summary
docs/concepts/interaction-pattern-catalog.md. Two families disagreed; both entries are relocated verbatim.Handoff Todo Gate State: the Work Routing table and the pattern-to-canary matrix both list it under Work Routing, and the IP-026 cross-references describe it as a routing gate, but the details block had it under Human Decision. Moved into the Work Routing block, between IP-003 and IP-021.Agent-Scoped No-Candidate Gap: the State And Boundary table lists it as a P0 row directly after IP-006, but the details block had it after IP-022, inside the P1 group, so a P0 boundary pattern read as if it were P1. Moved to sit after IP-006 and before IP-011.Issue Or Task
Validation
c2fe2f583d5807f96ab9c78d9f2023fbed61533estaticpassedloopx check --scan-path docs/concepts/interaction-pattern-catalog.md→ok: True,errors=0,public boundary scan clean: 1 files.unitnot_rungit diff --statreports 190 insertions / 190 deletions (symmetric), and a sorted line-multiset comparison of the file before and after reports equality at 2445 lines. Family order was re-checked programmatically after both moves: all five families now have a details order identical to their table order.Frontend / Visual Evidence
Type of Change
LoopX Area
Technical Direction
Core control-plane hardening
Long-horizon benchmark evidence
Operator surface and IM integration
Shared Goal Authority and cross-host coordination
Architecture and research incubator
Target base branch: main