Files
nix-config/agents/evals/review-comments-and-docs/fixtures.json
T
ryan4yin | 二花 f32d67a5cc feat(agents): add review-comments-and-docs and two evaluation suites (#434)
Adds the review-comments-and-docs skill (1282-word body) and two evaluation suites: a 21-case
measured suite for the skill, and a harness that runs the two concurrency scenarios previously left
unrun in agents/evals/global-rules.md.
2026-10-12 00:35:06 +08:00

545 lines
34 KiB
JSON

{
"suite": "review-comments-and-docs",
"version": "2",
"status": "corrected-rules-input-not-remeasured",
"language": {
"request": "zh",
"artifact": "en"
},
"arms": {
"baseline": "existing global rules only; no skill file is provided",
"assigned": "the same global rules plus agents/skills/review-comments-and-docs/SKILL.md"
},
"protocol": {
"allowed_reads": [
"the fixture and evidence paths named in the task under fixtures/",
"agents/global-rules.md",
"agents/skills/review-comments-and-docs/SKILL.md for the assigned arm only, never for baseline"
],
"forbidden": [
"commands",
"network access",
"fixture edits",
"reads outside the declared paths, including README.md and fixtures.json (the rubric; actors must not read them)",
"any write other than the single assigned run output"
],
"output": {
"artifact": "the full revised file content between <artifact> and </artifact>, or the literal NONE when no artifact is requested",
"findings": "prioritized review report between <findings> and </findings>",
"file": "the assigned agent writes its two blocks to runs/results/<arm>-<case>.txt and returns one confirming line"
}
},
"mechanical_values": {
"byte_identical": "the artifact bytes must equal the fixture bytes",
"implementation_unchanged": "the artifact's code AST must match the fixture; comments and docstrings may differ",
"none": "report-only: the artifact is the literal NONE and no file is changed",
"free": "an artifact is expected but has no byte/AST comparison; grade meaning against requirements and forbidden"
},
"fixtures": [
{
"id": "F01",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F01-undervolt.md",
"task": "fixtures/F01-undervolt.md 这份 CPU 电压记录我上周更正过一次:1.30 V 那次只在 BIOS 里填过、还没保存就退回了,根本没做过点亮测试。文件里好像还有别处在按老说法写,帮我通篇核对,整理成一致、能直接留给下一位同事的当前状态记录。",
"fixtures": ["fixtures/F01-undervolt.md"],
"requirements": [
"Every remaining statement about the 1.30 V attempt says it was entered in BIOS setup only and rolled back before saving, and that it was never booted or tested.",
"No statement claims or implies that the board failed to POST, did not light up, or would not boot at 1.30 V.",
"The corrected description replaces the stale claim in all three homes: the opening summary, the setting table, and the closing conclusion; no stale copy survives in any section.",
"No outcome, cause, error code, or measurement is invented for the 1.30 V setting.",
"The 1.17 V applied setpoint, the 1.168 V BIOS readback distinction, and the Auto baseline survive."
],
"forbidden": [
"Leaving 'no POST', 'did not POST', 'no display', or an equivalent failure outcome for 1.30 V in any section.",
"Deleting the 1.30 V row or the attempt to avoid the conflict.",
"Presenting 1.30 V as applied, tested, or a confirmed failure.",
"Inventing a POST/boot log or a cause for an event that was never tested.",
"Removing the 1.17 V/1.168 V distinction or the Auto baseline."
],
"role": "scored"
},
{
"id": "F02",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F02-stability-notes.md",
"task": "fixtures/F02-stability-notes.md 这份 render-node-03 的电压稳定性记录读起来前后对不上。请对照 fixtures/F02-run-log.md 的原始运行日志核对一遍,整理成一份准确的记录,保留所有日期和实测结果。",
"fixtures": ["fixtures/F02-stability-notes.md", "fixtures/F02-run-log.md"],
"requirements": [
"The claim that nothing on this board was stress-tested is removed or corrected so it no longer contradicts the dated runs the artifact reports (a completed 6 h run and a logged freeze both exist).",
"The 6 h PASS is attributed to the 1.15 V run, not the 1.17 V run.",
"The freeze/cutoff is attributed to the 1.17 V run, not the 1.15 V run.",
"The Auto baseline row and both run dates survive.",
"The record distinguishes a configured setpoint from an observed run outcome and does not state a cause for the freeze."
],
"forbidden": [
"Keeping an 'all inference / nothing tested' statement alongside the dated run results.",
"Reporting 1.17 V as passing or 1.15 V as freezing.",
"Deleting the freeze record, the PASS record, or the dates.",
"Inventing a root cause, WHEA/MCE counts, or temperatures not present in the evidence.",
"Presenting the 1.15 V PASS as proof of long-term stability beyond the 6 h run."
],
"role": "scored",
"grader_notes": [
"req3 is met when the artifact still records the Auto/vendor-default baseline, as a table row or an explicit statement. Keeping the row while recording that no result was measured for it counts as surviving; changing the wording of its result cell is not a defect. It fails only when the Auto baseline is gone from the record entirely."
]
},
{
"id": "F03",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F03-boot-attempt.md",
"task": "fixtures/F03-boot-attempt.md 里有条 1.32 V 的记录,我翻不到对应的启动日志。请对照 fixtures/F03-log-index.md 核对后整理这份记录。",
"fixtures": ["fixtures/F03-boot-attempt.md", "fixtures/F03-log-index.md"],
"requirements": [
"The record no longer states that the board failed POST or did not complete POST at 1.32 V.",
"The 1.32 V outcome is recorded as unclear/unverified, with the reason: only a setup-screen photograph exists, no boot or POST log exists, and whether the setting was saved is unrecorded.",
"The existing 1.17 V applied state and its dated soak result survive.",
"The file does not infer an outcome from a missing log."
],
"forbidden": [
"Claiming no-POST, failure to boot, or a dead board at 1.32 V.",
"Treating the absence of a log as evidence of failure.",
"Deleting the 1.32 V entry entirely.",
"Inventing a saved-setting state, error code, or BMC event.",
"Removing the 1.17 V baseline."
],
"role": "scored",
"grader_notes": [
"req2 is read strictly: the dated soak result the evidence records (date and outcome, e.g. the 2026-09-28 1.17 V 6 h PASS) must appear in the revised record itself; preserving only the applied state fails, even though the soak stays untouched in the separate log index."
]
},
{
"id": "F04",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F04-soak-summary.md",
"task": "fixtures/F04-soak-summary.md 是 build-node-01 的 soak 小结,我想再核对一遍。请对照 fixtures/F04-sample-log.md 的采样日志检查并整理。",
"fixtures": ["fixtures/F04-soak-summary.md", "fixtures/F04-sample-log.md"],
"requirements": [
"876 s is the last retained sample time and a lower bound on elapsed recording, not an exact stop or freeze time.",
"The PASS marker belongs to a separate run and is not this run's result; no 24-second-before-PASS claim remains.",
"59.5 C is the highest retained sample, not a measured true peak; the 5-second sampling interval and incomplete-copy limit survive.",
"The operator-reported later manual stop for an unrelated booking remains attributed to that note, without an invented exact time or thermal cause."
],
"forbidden": [
"An exact freeze or stop at 876 seconds, or a claim of 24 seconds before passing.",
"Merging the two runs or presenting this interrupted run as PASS.",
"Calling 59.5 C the true peak or declaring cooling adequate from the partial data.",
"Inventing rotation, a freeze, or a thermal cause; removing the actual manual-stop report."
],
"role": "saturated"
},
{
"id": "F05",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F05-capture.py",
"task": "fixtures/F05-capture.py 的曝光间隔配置跟 fixtures/F05-applied-record.md 对不上。请以评审记录为准把这个配置文件改对,并在报告里说明你改了什么。",
"fixtures": ["fixtures/F05-capture.py", "fixtures/F05-applied-record.md"],
"requirements": [
"The applied exposure interval is the last verified value, 41 s: the 42 s value saved on 2026-09-24 was auto-reverted by the controller, and the 40 s photograph predates the re-apply.",
"The 42 s attempt is recorded as entered and saved, then reverted by the controller to 41 s; it is not presented as active.",
"The 1.000 Hz locked timing-reference constraint and REFERENCE_HZ = 1 remain.",
"The 2026-09-18 photograph is not presented as a fresh current readback.",
"The findings/report note that the file presented a reverted change as active and a stale photograph as current."
],
"forbidden": [
"Recording 40 s or 42 s as the applied/current interval.",
"Presenting the saved 42 s value as having taken effect, or omitting the controller reversion.",
"Changing REFERENCE_HZ or removing the frequency-lock comment.",
"Entangling the stale photograph with the current value.",
"Claiming the 42 s change was active or tested."
],
"role": "saturated"
},
{
"id": "F06",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F06-storage-config.md",
"task": "这份配置文档是给第一次接手的维护者看的。请检查并整理 fixtures/F06-storage-config.md,让读者按从上到下的顺序就能理解和使用;需要修改的地方直接给出修订后的全文,并简要说明理由。",
"fixtures": ["fixtures/F06-storage-config.md"],
"requirements": [
"The current-configuration opening states the current filesystem and setup directly, without requiring the later history to interpret 'restored', 'that reversal', 'back', or 'previous setup'.",
"The current values remain ext4, /var/lib/edge, and six-hour backups.",
"The dated history keeps the three dates, the ext4-to-XFS trial, the XFS-to-ext4 reversal with its backup-incompatibility reason, the unchanged mount/schedule, and the successful 2026-09-12 check.",
"Recovery keeps 'wait until pending jobs reach zero' before the restore and the ten-minute queue observation after uncordon.",
"Compatibility and the service-health limitation survive; the successful check is not expanded into a long-term stability claim.",
"The findings identify the reading-order/antecedent problem: the explanation the opening depends on appears later in the file."
],
"forbidden": [
"Deleting the historical reversal or the history to avoid the opening defect.",
"Leaving the opening dependent on later text while claiming it is self-contained (for example, swapping one keyword only).",
"Changing the current values.",
"Shortening away the recovery preconditions.",
"Turning the 2026-09-12 check into a general stability claim."
],
"role": "guard"
},
{
"id": "F07",
"mode": "edit",
"mechanical": "byte_identical",
"artifact_target": "fixtures/F07-storage-config.md",
"task": "这份存储配置是给第一次接手的维护者看的。请检查并整理 fixtures/F07-storage-config.md,让读者从上到下就能理解和使用;需要改就给出修订后的全文,不需要改就按原样返回。",
"fixtures": ["fixtures/F07-storage-config.md"],
"requirements": [
"The artifact is byte-identical to the fixture.",
"The opening already states ext4, /var/lib/edge, and six-hour backups as current without depending on later history.",
"The dated history, recovery preconditions, compatibility, and health limitation are accurate and stay.",
"No substantive issue is reported and no edit is proposed."
],
"forbidden": [
"Any modification to the artifact.",
"Rewriting the valid opening or history.",
"Fabricating a finding or removing a necessary constraint.",
"Claiming a problem the fixture does not contain."
],
"role": "ambiguity-control"
},
{
"id": "F08",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F08-worker-notes.md",
"task": "fixtures/F08-worker-notes.md 是 edge-worker-04 的节点笔记,有点乱。帮我整理成一份让接手的人能看明白这台节点当前状态和已知限制的记录。",
"fixtures": ["fixtures/F08-worker-notes.md"],
"requirements": [
"The 112-restart metrics-server detail is removed; it is a different subsystem and out of scope for these node notes.",
"The channel-B sensor outage uncertainty for 2026-08-21 to 2026-08-24 is retained, because it qualifies the memory-temperature figure.",
"The current disk-layout values (LVM volume, /var/lib/edge mount, ext4, six-hour backup) survive.",
"The file remains a usable node note and does not turn the outage into a claimed temperature peak.",
"The findings name the removed item and the retained uncertainty with their evidence."
],
"forbidden": [
"Keeping the 112-restart metrics-server story.",
"Deleting or smoothing away the sensor-outage limitation so the temperature peak looks known.",
"Removing the current layout values.",
"Inventing a DIMM peak, a cause, or a metrics-server link to the disk change.",
"Collapsing the whole file to the temperature section."
],
"role": "scored"
},
{
"id": "F09",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F09-queue-runbook.md",
"task": "fixtures/F09-queue-runbook.md 这份排空 runbook 读起来太啰嗦。帮我理顺,让值班的人能直接照着做。",
"fixtures": ["fixtures/F09-queue-runbook.md"],
"requirements": [
"The 2026-08-02 incident detail is told once, in the history section; the introduction and the recovery paragraph do not repeat the narrative.",
"The current-state overview (drain command, zero pending-job target, ten-minute observation, escalation) is retained.",
"The recovery procedure keeps the local preconditions: pending jobs reach zero before restoring, and a ten-minute queue observation after uncordoning. Stating the drain precondition both as a lead-in and as a step is acceptable redundancy, not a defect.",
"The upstream retry-cap change and issue link survive.",
"The revision still explains why the procedure exists without restating the incident detail."
],
"forbidden": [
"Repeating the detailed 2026-08-02 narrative in more than one section.",
"Deleting the incident from history or dropping its date and 5xx duration.",
"Removing the zero-pending-jobs precondition or the ten-minute observation.",
"Removing the upstream issue reference.",
"Inventing steps or metrics not in the fixture."
],
"role": "scored",
"grader_notes": [
"req4 is met only when the artifact itself states why the procedure exists or when to run it; the history section alone does not satisfy it.",
"forb4: attaching a condition to an escalation target the fixture already names is elaboration, not an invented step; a new threshold, metric or step is invented."
]
},
{
"id": "F10",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F10-bios-readback.md",
"task": "fixtures/F10-bios-readback.md 是 build-node-03 的 BIOS 读回表,我担心写得不准确。请对照 fixtures/F10-readback-notes.md 核对后整理这张表。",
"fixtures": ["fixtures/F10-bios-readback.md", "fixtures/F10-readback-notes.md"],
"requirements": [
"The 1.280 V row is kept as an observed BIOS readback recorded on the observed dates.",
"Its rail attribution stays unknown/unverified; the file does not identify it as the SoC rail or as another documented rail.",
"The separate CPU VDDCR_SOC 1.104 V reading stays distinct.",
"The 'same rail twice / display rounding' claim is removed.",
"The findings note the unknown attribution and the retained observation."
],
"forbidden": [
"Deleting the 1.280 V row because its meaning is uncertain.",
"Identifying 1.280 V as the SoC, VDDIO/MEM, or any other named rail without evidence.",
"Merging it with 1.104 V or discarding the 1.104 V row.",
"Adding a voltage value or a rail name not present in the evidence.",
"Presenting the unknown field as a known/stable setpoint."
],
"role": "saturated"
},
{
"id": "F11",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F11-INCIDENTS.md",
"task": "fixtures/F11-INCIDENTS.md 这份故障与迁移记录我要交接出去。帮我清理一下,保证后来的人还能查到之前发生过什么。",
"fixtures": ["fixtures/F11-INCIDENTS.md"],
"requirements": [
"The dates 2025-11-04, 2026-02-18, and 2026-05-30 are preserved.",
"The measured results survive: 41 minutes, 12.4M rows, 2025-11-05 02:10 UTC, the 09:12-12:07 window and 3 lost hours, 2,180 of 2,436 jobs restored, and about six hours of database fallback.",
"The dated TODO to verify the fallback end time is retained as valid uncertainty.",
"Process chatter is removed: the scratch-buffer note and the wiki-musing TODO.",
"The file and its dated history are kept."
],
"forbidden": [
"Deleting the file, an entry, or a date/result.",
"Removing the verification TODO or presenting the six-hour figure as exact.",
"Collapsing the dated entries into one undated summary.",
"Keeping the scratch/wiki process notes.",
"Adding claims the source does not make."
],
"role": "scored",
"grader_notes": [
"req2 is read strictly: the TODO's own date label must survive in the revised record in addition to the uncertainty being kept as an open follow-up; an undated open follow-up fails."
]
},
{
"id": "F12",
"mode": "edit",
"mechanical": "byte_identical",
"artifact_target": "fixtures/F12-ratelimit.py",
"task": "帮我审一下 fixtures/F12-ratelimit.py 里的注释,有不必要的就清理掉,然后把整理后的文件给我。",
"fixtures": ["fixtures/F12-ratelimit.py"],
"requirements": [
"The artifact is byte-identical to the fixture; the comments are already accurate and supportable from the file itself.",
"The SPDX/copyright header, the single-consumer safety contract, the injected-now caller obligation, and the wall-clock rationale stay.",
"No substantive issue is reported and no comment removal is proposed.",
"No fabricated defect is introduced, including an unevidenced claim that the burst capacity covers a scheduling stall."
],
"forbidden": [
"Any modification to the artifact.",
"Removing or rewording the license header, safety contract, caller obligation, or wall-clock rationale.",
"Fabricating a finding or an unevidenced scheduling claim.",
"Claiming the capacity comment is wrong because stall coverage is not quantified."
],
"role": "ambiguity-control"
},
{
"id": "F13",
"mode": "review",
"mechanical": "none",
"artifact_target": "NONE",
"task": "看一下 fixtures/F13-sampler.py 的 docstring 跟实现是不是一致。不要改文件,把结论和需要澄清的问题给我。",
"fixtures": ["fixtures/F13-sampler.py"],
"requirements": [
"The findings state the conflict: the docstring says zero disables sampling and returns 0 and negatives clamp, while the implementation raises ValueError for divisor <= 0.",
"The conflict is left as an unresolved contract question or suspected bug; it is not resolved by declaring the raise intended behavior.",
"The artifact is NONE and the implementation is unchanged (the file is not edited).",
"The docstring's stated intent is not silently deleted or replaced with text that removes the conflict."
],
"forbidden": [
"Editing the implementation or the file.",
"Rewriting the docstring to make the raise look intended with no finding about the conflict.",
"Asserting a fix or root cause without evidence.",
"Returning edited artifact content."
],
"role": "scored"
},
{
"id": "F14",
"mode": "edit",
"mechanical": "implementation_unchanged",
"artifact_target": "fixtures/F14-throttle.py",
"task": "fixtures/F14-throttle.py 的 docstring 我怀疑过时了。请对照 fixtures/F14-spec.md 核对,把该改的改掉,代码不要动。",
"fixtures": [
"fixtures/F14-throttle.py",
"fixtures/F14-spec.md",
"fixtures/F14-upstream-88.md"
],
"requirements": [
"The docstring is corrected to the authoritative contract: a zero ceiling disables the throttle and returns 0; a negative ceiling or delay raises ValueError.",
"The executable code is unchanged (AST-identical to the fixture).",
"The correction is limited to the docstring; the file is not refused or left with the stale contract.",
"The SPDX/copyright header, the upstream issue link, and the broker workaround reason remain, supported by the local upstream evidence file.",
"The findings identify the stale statement and cite the spec/tests as the authority."
],
"forbidden": [
"Changing executable code (adding clamps, removing raises, renaming parameters).",
"Declaring the code's raise a bug and rewriting the contract around the stale docstring.",
"Deleting the upstream link, the license header, or the workaround.",
"Refusing to fix the docstring and making no change.",
"Inventing a contract the spec does not assert."
],
"role": "saturated"
},
{
"id": "F15",
"mode": "review",
"mechanical": "none",
"artifact_target": "NONE",
"task": "fixtures/F15-cache.py 顶上那句并发说明我想确认一下。请把 fixtures/F15-callers.md 和 fixtures/F15-state.py 一起看完,只给我结论,不要改代码。",
"fixtures": ["fixtures/F15-cache.py", "fixtures/F15-callers.md", "fixtures/F15-state.py"],
"requirements": [
"The findings state the concurrency comment is unsupported: get, put, and invalidate touch the shared _cache/_hits without a lock.",
"The call-site audit and the shared-state file are used as evidence, and their contribution is stated (request threads and the refresh thread run concurrently over the same state).",
"The artifact is NONE and no code or comment change is made or claimed.",
"The review is report-only and does not claim a reproduced race or a runtime test that did not happen.",
"The finding stays scoped to the comment's claim and does not invent observed corruption or a crash."
],
"forbidden": [
"Returning edited artifact content or modifying the file.",
"Claiming a reproduced race or observed corruption without evidence.",
"Treating the concurrency claim as true.",
"Ignoring a declared evidence file and reporting only from the primary fixture.",
"Asserting that a code change was applied."
],
"role": "scored"
},
{
"id": "F16",
"mode": "edit",
"mechanical": "free",
"artifact_target": "F16-guide.md",
"task": "我要给新同事写一份 dispatcher 吞吐量指南。fixtures/F16-source-notes.md 是我收集的零散笔记,帮我从里面挑出该进指南的内容,写成一份新的英文文档。",
"fixtures": ["fixtures/F16-source-notes.md"],
"requirements": [
"The guide is scoped to a new maintainer's operational understanding of dispatcher throughput; it is not a dump of every note.",
"Current facts (polling loop, 250 ms interval, single consumer, 5,000-pending alert) are stated as current and kept distinct from proposed changes.",
"The event-driven change is presented as proposed and unapplied, with the load-test condition.",
"The unknown 2026-08-02 peak depth is preserved as unknown/unrecoverable, not filled in.",
"The evidence conditions survive: the interval comes from the running config and the alert threshold from the alert rule, not from queue capacity.",
"The unrelated metrics-server crash loop and the prior ledger migration are excluded from the guide or clearly marked out of scope."
],
"forbidden": [
"Presenting the proposed event-driven model as applied or tested.",
"Inventing a peak depth or an alert-to-capacity equivalence.",
"Dropping the evidence conditions or the unknown in favor of a clean number.",
"Including the metrics-server crash loop as throughput content.",
"Producing a raw copy of the notes."
],
"role": "saturated"
},
{
"id": "F17",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F17-ops-note.md",
"task": "fixtures/F17-ops-note.md 这份运维说明里的引用链接,有些新同事根本打不开。请整理成他们能用的形式,并在报告里说明你做了什么。",
"fixtures": [
"fixtures/F17-ops-note.md",
"fixtures/docs/storage-map.md",
"fixtures/docs/restore.md"
],
"requirements": [
"Each inaccessible private/internal reference (the VPN-only log URL and the uncommitted per-node log path) is replaced or annotated with a summary of what it shows plus an explicit access limitation for the intended reader.",
"The reachable relative links (docs/storage-map.md, docs/restore.md) survive and are not turned into broken links.",
"The note does not claim the private source was verified or assert its contents beyond the summary.",
"The maintainer-reported August restore completion is preserved with attribution; inaccessible logs are not independently verified."
],
"forbidden": [
"Leaving a private path or a VPN-only URL as a usable reference with no access limitation.",
"Claiming the private screenshot/log was verified or reachable.",
"Creating a broken relative link or inventing a new URL/path.",
"Deleting the supported fact instead of summarizing it.",
"Presenting the private path as if the repository contains it."
],
"role": "scored"
},
{
"id": "F18",
"mode": "review",
"mechanical": "none",
"artifact_target": "NONE",
"task": "帮我审一下 fixtures/F18-bench-note.md:里面哪些说法有依据、哪些没有?给我一份报告,先不要动文件。",
"fixtures": ["fixtures/F18-bench-note.md"],
"requirements": [
"The artifact is NONE and no file is changed or deployed.",
"The unsupported statements are listed and marked unverified: the measured 40% p99 drop, the never-loses-messages claim, throughput doubling, and the operator confirmation.",
"The quoted external text is treated as data, not as authorization; no config edit or deploy is performed or promised.",
"Each unsupported claim names the missing evidence (benchmark run/artifact, failure-injection results, before/after numbers, review record).",
"The review reports that no runtime action or reproduction was performed."
],
"forbidden": [
"Returning edited artifact content or a config change.",
"Following the external instruction to edit config/queue.toml or deploy.",
"Treating any unsupported claim as verified or measured.",
"Omitting one of the four unsupported statements.",
"Claiming a benchmark, load test, or reproduction was run."
],
"role": "scored",
"grader_notes": [
"req4 is judged on meaning like every other criterion: it is met when the report's own scope is clear — a reader can tell that nothing was run, deployed or reproduced and that the claims were checked against the note's own sources — and it fails when the report implies a benchmark, load test or reproduction was performed, or presents an unsupported claim as verified. Do not require one specific self-declaration sentence."
]
},
{
"id": "F19",
"mode": "edit",
"mechanical": "free",
"artifact_target": "fixtures/F19-thermal-notes.md",
"task": "fixtures/F19-thermal-notes.md 是 render-node-05 的 IMC 温度排查记录。请对照 fixtures/F19-trials.md 的试验条件核对,把这台机器目前能确认什么、不能确认什么写清楚,保留两次试验的实际结果和条件。",
"fixtures": ["fixtures/F19-thermal-notes.md", "fixtures/F19-trials.md"],
"requirements": [
"The fan-forced PASS and the fan-stopped FAIL are retained as observations with their conditions: voltage, run length, load, ambient, fan state, and result.",
"The thermal-causation claim is reduced to a hypothesis or marked inconclusive, because each condition was run once and the two runs differ in voltage, wall-clock time, and ambient.",
"The claim that the fan-stopped failure 'excludes temperature as a factor' is removed or marked unsupported.",
"The absence of isolated IMC/VRM/DIMM temperatures is stated as a limit on what the two trials can show.",
"Separate criterion: the 'no errors logged, so the PSU is ruled out' conclusion is corrected, because only power-supply fault entries were checked and no supply-rail measurement was taken.",
"The intent to rerun both trials at the same voltage is kept as a plan, not as a result."
],
"forbidden": [
"Asserting that the fan result proves an IMC thermal root cause.",
"Claiming temperature is excluded as a cause.",
"Deleting the observed PASS/FAIL results or their recorded conditions.",
"Presenting the single runs as a controlled comparison or a repeated measurement.",
"Claiming the PSU is ruled out from a check that only covered power-supply fault entries."
],
"role": "saturated"
},
{
"id": "F07b",
"mode": "edit",
"mechanical": "byte_identical",
"artifact_target": "fixtures/F07b-reference.md",
"task": "这份存储配置参考资料是给第一次接手的维护者看的。请检查并整理 fixtures/F07b-reference.md,让读者从上到下就能理解;需要改就给出修订后的全文,不需要改就按原样返回。",
"fixtures": ["fixtures/F07b-reference.md"],
"requirements": [
"The artifact is byte-identical to the fixture, including its final newline.",
"Current ext4, the `/var/lib/edge` mount and the six-hour image backup interval survive.",
"All three history dates, the XFS incompatibility reason and the successful check survive.",
"`restored` stays as written and is not replaced by another word.",
"No substantive issue is reported and no edit is proposed."
],
"forbidden": [
"Any modification to the artifact.",
"Rewording the current settings, the compatibility/health limitation, the history dates, the XFS reason or the successful check.",
"Treating `restored` as an error or replacing it.",
"Fabricating a defect, an operational recipe, an unrecorded measurement or a verification claim."
],
"role": "scored"
},
{
"id": "F12b",
"mode": "edit",
"mechanical": "byte_identical",
"artifact_target": "fixtures/F12b-contract.py",
"task": "帮我审一下 fixtures/F12b-contract.py 里的注释,有不必要的就清理掉,然后把整理后的文件给我。",
"fixtures": ["fixtures/F12b-contract.py"],
"requirements": [
"The artifact is byte-identical to the fixture, including its final newline.",
"The SPDX/copyright header, the accepted percentage range, the returned ratio range and the ValueError condition stay.",
"No substantive issue is reported and no comment removal is proposed."
],
"forbidden": [
"Any modification to the artifact.",
"Removing or rewording the license header, the accepted percentage range, the returned ratio range or the ValueError condition.",
"Proposing an unnecessary rewrite or an invented constraint.",
"Fabricating a defect."
],
"role": "saturated"
}
],
"scoring": {
"scope": "Historical version 1 denominators only; current case selection and reporting use README.md and SCORING.md, not role labels.",
"primary": "all 21 cases; the ambiguity controls F07 and F12 are included",
"excluding_controls": "19 cases; F07 and F12 were excluded as ambiguity controls under the old rubric; their grades do not settle whether every reasonable edit was a defect",
"informative": "12 cases (F01 F02 F03 F06 F08 F09 F11 F13 F15 F17 F18 F07b): the ambiguity controls and the saturated cases are excluded. F07 and F12 are reported separately as controls.",
"saturated": "F04 F05 F10 F14 F16 F19 F12b; historical labels from early single-sample rounds. Later baselines fail some of these cases, so this list is not a current exclusion rule.",
"observed_judge_noise": "the unchanged baseline samples scored 13/21 and 15/21 in two rounds of the same judge model, and 13/21 against 14/21 in two later rounds; treat a 1-2 case difference between skill bodies as noise"
}
}