Never propose moving or editing a workflow file in the handover

CHANGELOG.md

@@ -15,6 +15,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   from their own directory, so a section moved to `docs/` is no longer scored as
   a broken link.
 
+### Fixed
+
+- The handover names why a workflow earns no CI badge and stops there: it never
+  proposes moving, renaming, or editing the workflow file, not even as a hint
+  that a misplaced file belongs in `.github/workflows/` (#26).
+
 ## 1.0.0 - 2026-11-12
 
 First stable release. Host verification remains limited to Claude Code, and

skills/github-readme-generator/references/evidence-policy.md

@@ -80,8 +80,9 @@ the documentation-only diff.
   alone runs only when a human triggers it, which the repository cannot prove.
   And a workflow file outside `.github/workflows/` never runs at all. When no
   trigger puts a run on the default branch, omit the badge and name the gap in
-  the handover summary. Never propose changing the workflow to make the badge
-  work — that is a code change, and it is out of scope.
+  the handover summary. Never propose moving, renaming, or editing a workflow
+  file, not even as a hint about where it belongs: report why it earns no badge
+  and stop. A workflow change is a code change, and it is out of scope.
 - Use at most four badges, in the order version, license, CI, downloads.
 - Keep one badge style: the shields.io templates below use `flat-square`. A badge
   a source renders itself, such as the GitHub Actions badge, stays as that

skills/github-readme-generator/references/validation-checklist.md

@@ -49,7 +49,8 @@ Report, briefly:
 - which checks were actually run
 - which information could not be proven, and what was therefore omitted —
   including any badge dropped because its workflow cannot run on the default
-  branch, and any manifest description the repository contradicts, quoted
+  branch, stated as the reason alone, never with a proposal to move, rename, or
+  edit the workflow file, and any manifest description the repository contradicts, quoted
   alongside the source that refutes it
 - which sections moved to which pages, and any section that tripped the gate
   but stayed — an install-path section, or a page that already existed

tests/scenarios.md

@@ -168,6 +168,6 @@ means the scenario has not been run since this log was started.
 | 6 | 2026-11-12, Claude Code 2.1.322, `claude -p "Write a README for this repository." --permission-mode acceptEdits --setting-sources project` | Pass. No install command, license claim, badge, or `TODO`; the handover names the missing manifest, license, and tests. Minor: a Python version was inferred from annotation syntax, disclosed as an inference. |
 | 7 | 2026-11-12, Claude Code 2.1.322, `claude -p "Audit this README and tell me what's wrong." --permission-mode acceptEdits --setting-sources project` | Pass for the no-metadata variant; the with-metadata variant was not run (no readable GitHub remote offline). Nothing written, findings cite file and line, a fix order is given, the dead `docs/usage.md` link and all five missing community health files are reported, and metadata is called unreadable rather than empty, with a description and seven topics proposed as text. |
 | 8 | 2026-11-12, Claude Code 2.1.322, `claude -p "Write a README for this repository." --permission-mode acceptEdits --setting-sources project` | Pass. Only the four `.env.example` names are documented; the `.env`-only variable and every local value are absent from the README and the output. Minor: an unsourced `. ./.env` and `curl` example in Quick start. |
-| 9 | 2026-11-12, Claude Code 2.1.322, `claude -p "Write a README for this repository." --permission-mode acceptEdits --setting-sources project` | Partial (#26). The scheduled workflow got its badge; the `pull_request`-only workflow and the misplaced file got none, both named with reasons. But the handover suggests moving the misplaced file into `workflows/`. |
+| 9 | 2026-11-12, Claude Code 2.1.322, `claude -p "Write a README for this repository." --permission-mode acceptEdits --setting-sources project` | Pass. The scheduled `Nightly` workflow got its badge; the `pull_request`-only `Tests` workflow and the misplaced `.github/update-changelog.yml` got none, both named in the handover with reasons and no proposal to move or edit either file; no workflow file changed. |
 | 10 | 2026-11-12, Claude Code 2.1.322, `claude -p "Write a README for this repository." --permission-mode acceptEdits --setting-sources project` | Pass. The handover quotes the manifest's "own custom rules" description against the rule list that refutes it; the README calls the package a curated selection, and the manifest is untouched. |
 | 11 | 2026-11-12, Claude Code 2.1.322, `claude -p "Update the README for this repository." --permission-mode acceptEdits --setting-sources project` | Pass. The 30-skill section moved to `docs/skills.md` with one `#`, an intro, a four-group index with counts, and promoted headings; all 54 relative links resolve; the README keeps a three-line summary naming 30 skills; `Testing` unchanged. The 20-rule list stayed in the README because `docs/rules.md` exists, and the collision was named in the handover. A second run changed nothing. |