You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@amy-why-3459@zengchuang-hw — under the delegated architecture-coordination role, I adopt the joint five-entry D008 record for these two governing issues:
Benchmark owns sampling order, timing and artifact hashes; transport stays caller-injected.
Harness owns the required snapshot port; Apps binds the infra implementation, with no Harness concrete default.
Apps owns workflow display projections.
Harness owns factual profile records, bounded single-trace overview and integrity/digest reads; Apps owns UI and live-route decoration.
Apps owns pre-profile search display projections.
B01 delivers its implementation plus this shared decision metadata; OBS retains its implementation. This records architecture adoption, not independent implementation acceptance. Both issues retain their evidence requirements; isolation_complete remains false.
Closing the bounded B01 migration slice delivered by PR #422, merged as 9ede1835.
The legacy run/evaluate chain is assigned to Benchmark, Harness facts and Apps composition, with compatibility retained. Evidence includes hosted checks and the PR's exact-head Linux regression. The shared D008 record was adopted on #414 and #413.
Independent read-only follow-through for comments:6887366262:2026-11-15T01:34:04Z. Issue414 remains closed. I found no existing own comment explicitly covering this request. I used the isolated original-goal extraction and current executable code, not the source's adoption/delegation assertions or other reviews.
Baseline inspected: main 0311393c62330c041a01238dc86823b80e020561. The safe scope is the legacy-run responsibility split and preservation of behavior, not wholesale core isolation or reopening implementation work.
Current evidence:apps/legacy/evaluation.py converts a RunSpec into Benchmark rules and delegates evaluation to benchmark/legacy_run_v0.py. The latter owns the verdict calculation and explicitly gives incomplete evidence precedence over failure and success. Current harness/atomic_json.py owns a local JSON writer with Unicode, indentation, finite-number enforcement and trailing newline. The selected tests exercise the writer's byte equivalence, injected execution/assessment ports, metric-validation ownership, retired entry behavior, legacy exit codes, and frozen evaluation fixtures. This is evidence for these concrete boundaries; it is not an assertion that a historical adoption document is authoritative.
completed 50 passed, 43 subtests passed, one pytest-plugin deprecation warning, in 21.13s. These are bounded CPU/synthetic checks, including frozen evaluation-byte/exit-code cases, not model/device executions.
A separate current-tree gate read returned zero violations but isolation_complete=false, with blockers for 12 Harness→Infra hits and five runtime-resource loaders. This distinction matters: the legacy split tests passing does not establish global isolation or authorize removing those blockers. Current retirement of old entrypoints is also a later repository fact, not grounds to retroactively expand this Issue's original scope.
Remaining limits: the exact pre-adoption requirement version and authority for the referenced ownership decision were not independently recovered. I did not infer acceptance of prerequisite Issues or the excluded skill-eval, production prepare/assess, model/validator migration, CLI migration or root-retirement work. Full-suite, installed-package, native Windows and historical source-to-candidate equivalence outside the selected frozen fixtures were not run here. No comprehensive prerequisite closure or whole-Issue PASS is asserted.
AGENTS/review guidance was checked. No code, tracker, status, policy or artifact was changed; no closed task was reopened, no merge occurred, and no model/device/paid experiment or previously stopped task was resumed.
Activity
amy-why-3459 commentedon Nov 12, 2026
谢谢,B01 的拆分思路清楚。我对照了当前 main(
e2f4cd1e)上的相关文件,补充几点:harness/runner.py现有的边(L11-16):infra.artifacts.atomic_write_json、infra.targets.repository_identity、.evaluation.evaluate、.reporting.write_report、.scenarios.external。正文覆盖了 evaluate、reporting 和 artifacts。repository_identity归谁(H 自备,还是由 Apps legacy 组合时传入)建议在 PR 里写明,因为验收要求"runner 对 artifacts/targets 的边"都消失。harness/evaluation.py还导入了..claim.Verdict(L5)和..runspec.RunSpec(L7)。evaluate/_summary搬进 B 后,B→claim/runspec这两条边是否合规,请对照 rfc: K/H/B 与 Apps 公开接口详细设计(最小交接与模块边界) #387 的目标图确认,必要时一并登记。evaluation.json字节不变"和"退出码 0/1/2、incomplete 优先",建议各配一个迁移前后对比的夹具测试,至少覆盖 pass、fail 和 incomplete 三种情况。status:proposed,Publish standardized Apps run output #397 仍是 Draft,main 上还没有apps/。正文已把"task: Apps 应用层详细设计与迁移计划(CLI / Python / Plugin) #371 接受apps/legacy/路径"列为前置,这一点很好,请在开工前确认。Merge branch 'main' into impl/b01-run-evaluate
test: pin sampling._sha256 to infra.artifacts.sha256
docs: record RSI-master D008 B01 ownership decisions
docs: cite delegated D008 decisions and clear review nits
benchmark: present the B01 tree as a single commit on current main
Dong1017 commentedon Nov 15, 2026
@amy-why-3459 @zengchuang-hw — under the delegated architecture-coordination role, I adopt the joint five-entry D008 record for these two governing issues:
B01 delivers its implementation plus this shared decision metadata; OBS retains its implementation. This records architecture adoption, not independent implementation acceptance. Both issues retain their evidence requirements;
isolation_completeremains false.benchmark: present the B01 tree as a single commit on current main (#422
Dong1017 commentedon Nov 15, 2026
Closing the bounded B01 migration slice delivered by PR #422, merged as
9ede1835.The legacy run/evaluate chain is assigned to Benchmark, Harness facts and Apps composition, with compatibility retained. Evidence includes hosted checks and the PR's exact-head Linux regression. The shared D008 record was adopted on #414 and #413.
A-entry, R01 and #410's formal main-only replay remain separate. Overall
isolation_completeremains false.zengchuang-hw commentedon Nov 17, 2026
Independent read-only follow-through for
comments:6887366262:2026-11-15T01:34:04Z. Issue414 remains closed. I found no existing own comment explicitly covering this request. I used the isolated original-goal extraction and current executable code, not the source's adoption/delegation assertions or other reviews.Baseline inspected: main
0311393c62330c041a01238dc86823b80e020561. The safe scope is the legacy-run responsibility split and preservation of behavior, not wholesale core isolation or reopening implementation work.Current evidence:
apps/legacy/evaluation.pyconverts a RunSpec into Benchmark rules and delegates evaluation tobenchmark/legacy_run_v0.py. The latter owns the verdict calculation and explicitly gives incomplete evidence precedence over failure and success. Currentharness/atomic_json.pyowns a local JSON writer with Unicode, indentation, finite-number enforcement and trailing newline. The selected tests exercise the writer's byte equivalence, injected execution/assessment ports, metric-validation ownership, retired entry behavior, legacy exit codes, and frozen evaluation fixtures. This is evidence for these concrete boundaries; it is not an assertion that a historical adoption document is authoritative.Fresh actual checks: on this exact main revision,
completed 50 passed, 43 subtests passed, one pytest-plugin deprecation warning, in 21.13s. These are bounded CPU/synthetic checks, including frozen evaluation-byte/exit-code cases, not model/device executions.
A separate current-tree gate read returned zero violations but isolation_complete=false, with blockers for 12 Harness→Infra hits and five runtime-resource loaders. This distinction matters: the legacy split tests passing does not establish global isolation or authorize removing those blockers. Current retirement of old entrypoints is also a later repository fact, not grounds to retroactively expand this Issue's original scope.
Remaining limits: the exact pre-adoption requirement version and authority for the referenced ownership decision were not independently recovered. I did not infer acceptance of prerequisite Issues or the excluded skill-eval, production prepare/assess, model/validator migration, CLI migration or root-retirement work. Full-suite, installed-package, native Windows and historical source-to-candidate equivalence outside the selected frozen fixtures were not run here. No comprehensive prerequisite closure or whole-Issue PASS is asserted.
AGENTS/review guidance was checked. No code, tracker, status, policy or artifact was changed; no closed task was reopened, no merge occurred, and no model/device/paid experiment or previously stopped task was resumed.