feat(recipe-report): use approved 2026-06-02 report as the style template; tighter lead for future runs

Save the operator-approved 2026-06-02 spec as example-spec.json (gold standard
for voice/structure/specificity). Skill now tells the agent to match it, with
one deliberate change: keep the editorial lead TIGHT (~2 short paragraphs,
~120 words). The live 2026-06-02 page stays as the reference.

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

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

@@ -29,9 +29,11 @@ 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 a short `lead` (2–4 short paragraphs): 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** — like a newspaper lead. This is opus's voice; be useful, concrete.
+   - **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.)
    - **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.
@@ -43,6 +45,11 @@ Helper: `python3 /srv/cc-ci/cc-ci-plan/recipe-report.py {survey|render|publish}`
    GREEN/STALE/FAILED/SKIPPED/UPTODATE, `ci` as a level/result number+info string e.g. `build 154 ✓`
    or `RED · restore` with `ci_url`, `pr`/`pr_url`, `notes`). **CI = link + number/info only; no images.**
 
+   **Template — match this.** `.claude/skills/recipe-report/example-spec.json` is the gold-standard
+   example (the 2026-06-02 report; the operator approved its style/format). **Match its editorial voice,
+   structure, field shapes, and level of specificity** — the only deliberate change is the **shorter
+   `lead`** described above. Read it before writing your spec.
+
 5. **Render & publish.**
    `python3 .../recipe-report.py render /tmp/report-spec.json /tmp/week-<DATE>.html`
    `python3 .../recipe-report.py publish /tmp/week-<DATE>.html <DATE>`