readme-checklisted

Audits all README.md files for staleness after significant code changes. Only triggers a review when the change volume warrants it. ## README discovery Discover all READMEs dynamically in Step 2. Common locations: | File | Audience | Key content to verify | | ----------------------------- | ------------ | ----------------------------------------- | | `README.md` | Contributors | Project table, script table, .NET version | | `scripts/README.md` | Contributors | Script tables match `scripts/help.sh` | | `src/*/README.md` | Package users| Rule tables, version, install snippets | ## Step 1: Check threshold **Skip this step if invoked with `--skip-threshold`** — proceed directly to Step 2. Count `.cs` file changes in the last 30 commits: ``` scripts/status.sh --history 30 ``` If **fewer than 50** `.cs` files changed, report "README check skipped — below threshold" and stop. ## Step 2: Discover READMEs ```bash scripts/solution-inventory.sh --readmes ``` Verify the inventory above is still complete. If a new README exists, flag it. ## Step 3: Audit each README ### Root README.md 1. Read `README.md` 2. Cross-reference project tables against `scripts/solution-inventory.sh --json` (`solution` + `projects[].path`) 3. Cross-reference script table against `scripts/help.sh` output 4. Check .NET version against `Directory.Build.props` or the global.json SDK pin (`scripts/sdk-version.s