feat(recipe-report): link recipe names in the lead to their mirror repos; 3-para concise lead

render() auto-links whole-word recipe mentions in the editorial lead to
git.autonomic.zone/recipe-maintainers/<recipe> (single regex pass, longest-name-first,
no href corruption). Skill: lead is ~3 short paragraphs (~150-180 words) incl. an
'anything strange worth looking into' paragraph. example-spec.json lead updated to the
concise target.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.claude/skills/recipe-report/SKILL.md

@@ -29,11 +29,14 @@ Helper: `python3 /srv/cc-ci/cc-ci-plan/recipe-report.py {survey|render|publish}`
      of the version bumps) for upgrades that fix **CVEs / security issues**. Anything **critical/high**
      leads the page → the `security` bulletin (recipe · CVE id(s) + severity · what it fixes · PR link).
      This is the most important section; be specific about severity and what's exposed if not merged.
-   - **Lead / editorial.** Write the `lead`: the **overall state of the recipe fleet** this week (how
-     healthy, what moved, any worrying trend) and **specific, opinionated suggestions of what to focus
-     on** — opus's voice, useful and concrete. **Keep it TIGHT: 2 short paragraphs, ~120 words total** —
-     lead with the single most important thing, then security/focus in a sentence or two. (Trim hard;
-     the rest of the page carries the detail.)
+   - **Lead / editorial.** Write the `lead` in opus's voice — useful, concrete, opinionated. **~3 short
+     paragraphs, ~150–180 words:**
+     1. **Fleet state** in a line or two — how healthy, what moved, any trend.
+     2. **What to focus on** — security/critical merges first, then the key failures.
+     3. **Anything strange worth looking into** — odd or unexpected failures, parser snags, PR-state
+        oddities (e.g. a recipe carrying two open PRs to reconcile), drift from the summary, leftover
+        artifacts. This is the "editor's eye" paragraph; flag what a careful maintainer would want to notice.
+     Lead with the single most important thing; the rest of the page carries the detail.
    - **Needs attention** — GREEN PRs ready to merge + errors/failures to investigate (RED `!testme`,
      recipe bugs). Short, specific prose + links. Flag cross-cutting issues (e.g. two open PRs to reconcile).
    - **Routine** — minor/clean bumps, stale-test PRs (need operator `--with-tests`), up-to-date / skipped.