Fold in round-2 public-readiness nice-to-haves

CLAUDE.md

@@ -72,4 +72,4 @@ Validate by running `/create-dev-loop` against any real repository you maintain
 | `CONTRIBUTING.md` | Restated conventions and the validation checklist still match this file (`CLAUDE.md`) |
 | `SECURITY.md` | The trust model still matches what Step 2 of `create-dev-loop.md` actually reads from the target repo |
 | `.github/PULL_REQUEST_TEMPLATE.md` | Doc-sync checkboxes and test-plan guidance match the current CI scope and this file (`CLAUDE.md`) |
-| `.github/ISSUE_TEMPLATE/*.md` | Restated conventions and Step names still match this file (`CLAUDE.md`) |
+| `.github/ISSUE_TEMPLATE/*.md` | Restated conventions and Step names still match this file (`CLAUDE.md`) — `config.yml` in the same directory has no restatable conventions and is outside this glob |

README.md

@@ -40,7 +40,7 @@ Register `create-dev-loop.md` itself as a slash command by symlinking it into `~
 
 ```
 mkdir -p ~/.claude/commands
-ln -s "$(pwd)/create-dev-loop.md" ~/.claude/commands/create-dev-loop.md
+ln -sf "$(pwd)/create-dev-loop.md" ~/.claude/commands/create-dev-loop.md
 ```
 
 This is a one-time setup step for this repo's own product, distinct from Step 5, which registers each *generated* skill the same way.

tests/test_check_docs.py

@@ -2,7 +2,9 @@
 
 Each of check_docs.py's three checks appends to a module-level `errors`
 list rather than returning a value, so these tests reset that list before
-each call and assert on its contents afterward.
+each call and assert on its contents afterward. Any new test class added
+here must do the same in its own setUp() — skipping the reset lets a
+prior test's errors leak into the next assertion.
 """
 import sys
 import unittest