Skip to content

feat(explore): add owner-board views walkthrough smoke for GH-C69 - #3114

Closed
rootkiller6788 wants to merge 1 commit into
huangruiteng:mainfrom
rootkiller6788:feat/gh-c69-explore-views-walkthrough
Closed

feat(explore): add owner-board views walkthrough smoke for GH-C69#3114
rootkiller6788 wants to merge 1 commit into
huangruiteng:mainfrom
rootkiller6788:feat/gh-c69-explore-views-walkthrough

Conversation

@rootkiller6788

Copy link
Copy Markdown
Contributor

15 scenarios covering canonical-only, dual-view, evidence preservation, scaffolding suppression, status/metric rendering, decision lineage, evidence lineage, semantic lane views, single-lane behavior, readability assessment, stage views, source freshness, deterministic digest, no external sink, and full pipeline.

Summary

Issue Or Task

  • Closes #
  • Contributor task ID:

Validation

  • python3 -m py_compile loopx/*.py
  • loopx check --scan-root .
  • Other:

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Refactoring (no functional changes)
  • Documentation update
  • Test update

LoopX Area

  • Control plane (goals, todos, quota, scheduler, registry, runtime)
  • Benchmark boundary (adapters, runners, verifiers, scoring, evidence)
  • Capability or extension (providers, adapters, skills)
  • Public docs or presentation surface (README, protocols, dashboard)
  • Build, packaging, installer, or CI
  • Host or runtime integration

Boundary Checklist

  • I did not commit .loopx/, .codex/goals/, live ACTIVE_GOAL_STATE.md, credentials, private benchmark traces, verifier output, raw agent sessions, internal document links, or local machine paths.
  • I did not duplicate maintainer-owned benchmark work unless a maintainer split out a public issue for it.
  • I kept the change scoped to the linked issue/task.

15 scenarios covering canonical-only, dual-view, evidence preservation,
scaffolding suppression, status/metric rendering, decision lineage,
evidence lineage, semantic lane views, single-lane behavior,
readability assessment, stage views, source freshness,
deterministic digest, no external sink, and full pipeline.

@huangruiteng huangruiteng left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review PR #3114 — exact head b6a3df0434b7cee22182a2a60a198590736909ab

详细中文评审

动机

该 PR 为 Explore owner-board 视图(GH-C69)补充一个贡献者可见的 walkthrough smoke,证明 canonical、executive、semantic lane、dual view 这四类展示视图以及决策/证据 lineage、可读性评估、stage 拆分、freshness 与 public boundary 都是已实现并可回归验证的契约。此前这些视图行为分散在 loopx.presentation.explore_views 的多个函数中,缺少一条从合成投影到最终 bundle 的端到端示例路径;本 PR 用单文件示例把完整管线串起来,是比零散断言更可执行的贡献者入口。

改动思路

改动集中在新增 examples/explore-owner-board-views-walkthrough-smoke.py,不触碰产品代码、不引入外部 sink(明确不依赖 Lark/Feishu、provider 或本地路径)。示例直接调用真实展示模块:build_explore_presentation_bundleexplore_source_digestvalidate_explore_view_freshnessPRESENTATION_MODE_* 常量,全部使用合成 fixture。15 个场景按视图选择、完整性、语义压缩、lineage、可读性、stage、freshness、公开边界和完整管线的顺序组织;每个场景的载荷都经过 _assert_public_safemain() 汇总失败并返回非零退出码。

具体改动

关键内容讲解

  • _node/_edge/_finding/_projection 与四个 fixture(_decision_tree_projection_complex_projection_lane_projection_dense_hub_projection):用最小合成投影覆盖决策树、稠密 hub、语义 lane 和大图拆分四种形态。
  • 场景 1/2(视图自动选择):小图保持 PRESENTATION_MODE_CANONICAL_ONLY;复杂图触发 PRESENTATION_MODE_DUAL_VIEW 且 reason codes 包含 low_decision_densityexcessive_terminal_branches,并要求 canonical/executive 共享同一 source_digestsource_revision
  • 场景 3/4(完整性与压缩):canonical 保留全部节点、非 lineage 边与状态标签(ACTIVE/DONE/NO-PROMOTE);executive 抑制 dense hub 的 6 条 scaffolding 边(lineage_encoded_on_node == 6),保留真实 leads_to 证据边。
  • 场景 5(状态与指标渲染):节点状态标签与摘要中的指标(如 +31.2/+72.4 bp)进入 Mermaid,node_detail_coverage.complete 为 true。
  • 场景 6/7(决策与证据 lineage):open → exploring → resolved/dead_end 状态路径、refutes/supports/leads_to 边类型、finding 的 confidence 与节点归属都被验证。
  • 场景 8/9(semantic lane):lane 节点分组为并行子图,跨 lane 证据边保留、lane 内 scaffolding 抑制;单 lane 时不会虚构第二个 lane。
  • 场景 10/11(可读性与 stage):80 个孤立根节点触发 readability_check_failed;超过 stage_node_capacity 时拆分为有界、自包含的 stage,并校验节点数上限。
  • 场景 12/13(freshness):源内容变化产生不同 digest,validate_explore_view_freshness 判定 stale;相同投影 digest 确定性一致。
  • 场景 14/15(边界与端到端):bundle 不含 api_key/password/lark/feishu/真实 URL(SVG 命名空间除外);完整管线从决策树投影到 canonical+executive+assessment 全部通过 public-safe 检查。

对主干的风险

  • 无产品代码改动,git diff --check 干净;CI dependency-reviewpytest 均为 SUCCESS。
  • 示例漂移风险存在但被结构抑制:它调用 exact-head 的真实 explore_views API 而不是硬编码输出,视图行为变化时 smoke 会失败。
  • 不新增抽象或调用方:loopx.presentation.explore_views 是已上线的展示模块,本 smoke 只补公开回归路径,不存在“无活跃调用方”的 scope-fit 问题。
  • 公开边界:所有断言覆盖序列化 bundle,禁止词用字符串拼接构造以避免源码误判;明确无外部 sink。
  • 该 PR 合入后,之前 owner 审批通过的展示面契约获得一条可执行验证;无已知回归。

我的整体评价

同意合并(APPROVE)。692 行的单文件 walkthrough smoke 覆盖了 Explore owner-board 视图的全部关键契约:视图自动选择、完整性、语义压缩、双 lineage、可读性、stage、freshness 与公开边界,且全部 15 个场景在 exact head b6a3df0434b7cee22182a2a60a198590736909ab 本地独立运行通过;CI 双检查均绿。无阻塞项,仅建议后续维护者把该示例纳入常规 smoke 清单以保持回归覆盖。

English Verdict

APPROVE — exact head b6a3df0434b7cee22182a2a60a198590736909ab.

Key finding: the walkthrough smoke exercises the real loopx.presentation.explore_views surface across 15 scenarios (view auto-selection, canonical completeness, executive scaffolding suppression, decision/evidence lineage, semantic lanes, readability, stage splitting, freshness, public safety); all 15 passed in an independent local run at the exact head, CI dependency-review and pytest are both SUCCESS, and git diff --check is clean. No production code changes and no new abstractions; no blockers found.

Validation: local run of examples/explore-owner-board-views-walkthrough-smoke.py (15/15 ok); CI checks 2/2 SUCCESS.

@huangruiteng huangruiteng left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

详细中文评审(durable_smoke_value 门槛)

精确评审头: 3114@b6a3df0434b7cee22182a2a60a198590736909ab

动机

本 PR 是单文件 examples/explore-owner-board-views-walkthrough-smoke.py(+692 行),演示 owner-board 视图。按 durable_smoke_value 门槛,例程类 PR 必须证明对仓库/产品的真实、持久价值;本 PR 不满足。

改动思路

15 个 scenario 覆盖 owner-board 视图渲染、投影、external sink 检查与完整 walkthrough pipeline。作为演示自洽,但该行为已有专门测试覆盖,且文件体积达 692 行。

具体改动(关键内容讲解)

  • existing_coverage_scantests/test_explore_presentation_views.py 已覆盖 owner-board/presentation views 的关键路径;本 walkthrough 与既有覆盖高度重叠,属重复演示。
  • same_author_batch_scan#3113#3120 为同一作者的 8 个同构 walkthrough 系列,加上 #3130/#3131/#3133 三件套,属明确批量刷 PR 信号。
  • real_product_or_repo_value_verdict:若 owner-board 视图确有未覆盖断言,应在 tests/ 补 thin focused test;692 行 example 重复既有覆盖,对仓库是噪音。

对主干的风险

代码本身无运行时风险。风险在模式:同作者以同形状 walkthrough 系列占满队列,稀释真实 runtime 改动可见度;本系列其余 PR 同理应被拦截或合并。

我的整体评价

REQUEST_CHANGES。 修复建议(择一):(1) 收敛为 thin focused pytest;(2) 与 #3113#3120 系列合并为一个有差异化价值的 walkthrough。贡献行为警告:按 PR #3134 政策,若同一作者在警告后再提交此类低价值同形状 PR,将禁止该账号继续向本仓库提交 PR(owner 执行屏蔽)。


English Verdict

REQUEST_CHANGES — exact head b6a3df0434b7cee22182a2a60a198590736909ab.

Under the durable_smoke_value gate, this 692-line example-only walkthrough duplicates existing coverage (tests/test_explore_presentation_views.py) and is part of the same author's 8-PR walkthrough series (#3113#3120). Consolidate into thin focused tests or one differentiated walkthrough. Contribution warning: further low-value same-shape PRs will lead to the account being blocked from submitting PRs.

@rootkiller6788
rootkiller6788 deleted the feat/gh-c69-explore-views-walkthrough branch August 12, 2026 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants