From 0e52040c86ea1fbe1a738bebe57f8994908bdc1a Mon Sep 17 00:00:00 2001 From: hathach Date: Fri, 4 Sep 2026 05:12:54 +0700 Subject: docs: drop the pr3840 no-boards handoff, both halves are done The doc half landed in this branch. The test half it asked for already exists: NoBoardsExitRespectsFreshness and TheNoBoardsCallSiteIsWired in test/hil/test/test_hil_report.py (375e20090) cover the fresh and --accumulate no-boards exits through mark_report_no_boards. --- .../followup/pr3840-skill-md-no-boards-drift.md | 22 ---------------------- 1 file changed, 22 deletions(-) delete mode 100644 docs/superpowers/followup/pr3840-skill-md-no-boards-drift.md diff --git a/docs/superpowers/followup/pr3840-skill-md-no-boards-drift.md b/docs/superpowers/followup/pr3840-skill-md-no-boards-drift.md deleted file mode 100644 index 840d2a074..000000000 --- a/docs/superpowers/followup/pr3840-skill-md-no-boards-drift.md +++ /dev/null @@ -1,22 +0,0 @@ -# `SKILL.md` no-boards bullet: the regression test is still missing - -**Origin:** split out of PR #3840, surfaced by its second review round. Delete this file -when its own PR lands. - -The documentation half landed in PR #3881. `.claude/skills/hil/SKILL.md`'s -`**HIL run selected no boards.**` bullet (under "Reporting") now describes both cases: a -fresh run renders no table, and an `--accumulate` run keeps the previous attempt's rows -under the notice, which are not this run's and must not be reported as such. That matches -the code, which deliberately preserves accumulated rows on a no-boards exit because wiping -them destroyed real results. - -**What remains:** a test asserting that the fresh no-boards case renders no matrix while -the `--accumulate` case keeps the prior rows under the notice, so the two halves cannot -drift again. The behaviour lives in `test/hil/helper/hil_report.py`'s no-boards exit -(`accumulate_report` with `fresh`); `test/hil/test/test_hil_report.py` is the suite. - -## Why it was split out - -PR #3840 fixed the findings that changed a verdict. This is a documentation drift: the -behaviour is correct and the doc describing it is not, so it is better reviewed on its own -than appended to a branch already carrying a module consolidation. -- cgit v1.3.1