Masthead + opus 'lead' editorial (overall fleet state + what to focus on), a Security Bulletin of critical-CVE upgrades up top (mined from per-recipe upgrade_notes_md), then needs-attention/routine, and the comprehensive table as 'the full wire' at the end. survey now includes each recipe's upgrade_notes_md (breaking-change/CVE analysis) so opus can lead with security. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
4.1 KiB
name, description
| name | description |
|---|---|
| recipe-report | Generate the weekly public "Recipe Report" after the cc-ci /upgrade-all run. Reviews how the upgrade went and the state of every recipe + open PR, classifies what needs attention vs routine, and publishes a self-contained HTML page to report.ci.commoninternet.net (one page per week + a home index). Read-only — reports, never merges or edits PRs. Runs as its own agent (model configured separately from the upgrader; default opus). Invoke as /recipe-report [YYYY-MM-DD]. |
recipe-report
Produce the weekly "The Recipe Report" — a public HTML page reviewing the latest /upgrade-all run
and the live state of every recipe + open PR. Served at https://report.ci.commoninternet.net (one
week-<date>.html per run + a home-page index). You are read-only: you report, you never merge,
edit, or comment on PRs. The page is public + unauthenticated — include only public-safe data
(recipe names, version bumps, PR titles/links, CI verdicts, concise error summaries); never secrets,
tokens, internal IPs, or raw logs.
Helper: python3 /srv/cc-ci/cc-ci-plan/recipe-report.py {survey|render|publish} (see its header).
Procedure
-
Pick the date.
DATE= the argument, else today (UTC). The/upgrade-allsummary for that run is/srv/cc-ci/.cc-ci-logs/upgrades/upgrade-all-<DATE>.md. -
Survey.
python3 /srv/cc-ci/cc-ci-plan/recipe-report.py survey <DATE> > /tmp/survey.json. This gives you: the raw/upgrade-allsummary; for every recipe mirror its open PRs + thecc-ci/testmeverdict; and each recipe's per-recipe upgrade notes (upgrade_notes_md— the breaking-change / CVE / security analysis the upgrade did). Read it all. -
Review & classify — this is a front page, write it like an editor.
- Security first. Scan the per-recipe
upgrade_notes_md+ the summary (and use your own knowledge of the version bumps) for upgrades that fix CVEs / security issues. Anything critical/high leads the page → thesecuritybulletin (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. - 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.
- Security first. Scan the per-recipe
-
Write the spec
/tmp/report-spec.json(shape in the helper header):date,subtitle("Week of "),lead(the editorial, blank-line-separated paragraphs),security[](critical-CVE upgrades — may be empty),needs_attention[],routine[], and a comprehensivetable[]with EVERY recipe (recipe,change"a → b",statusGREEN/STALE/FAILED/SKIPPED/UPTODATE,cias a level/result number+info string e.g.build 154 ✓orRED · restorewithci_url,pr/pr_url,notes). CI = link + number/info only; no images. -
Render & publish.
python3 .../recipe-report.py render /tmp/report-spec.json /tmp/week-<DATE>.htmlpython3 .../recipe-report.py publish /tmp/week-<DATE>.html <DATE>(publish copies the page tocc-ci:/var/lib/cc-ci-reports/and regenerates the index.) -
Verify & stop.
curl -fsS https://report.ci.commoninternet.net/week-<DATE>.htmlrenders and the index lists it. Print the report URL andRECIPE REPORT COMPLETE, then go idle (one-shot — do not loop).
Guardrails
- Read-only. Never merge/edit/comment on PRs or touch recipes/tests. You only describe + link.
- Public-safe. No secrets/tokens/internal hostnames/raw logs on the page. Summarize errors.
- One page per run; always regenerate the index so all weeks are listed (newest first).