recipe-report: harden spec-in/page-out determinism contract
Make explicit that ALL formatting/HTML is owned by recipe-report.py render() and the model's only artifact is the spec JSON — never hand-write/edit HTML. Matters now that glm-5.2 drives the report. Also fix stale 'default opus' refs (report now defaults to opencode-go/glm-5.2, overridable via REPORT_BACKEND/REPORT_MODEL). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
165eb62070
commit
9e91d47205
@@ -227,8 +227,8 @@ PR list** (the actionable output):
|
||||
End with the report path and a reminder that **nothing was merged**.
|
||||
|
||||
## 6. Launch the public Recipe Report
|
||||
Once the summary is written, kick off the weekly public report (its own agent, separate model — default
|
||||
opus): **`python3 /srv/cc-ci/cc-ci-plan/launch-report.py fresh`** (use `fresh`, not `start` — the report
|
||||
Once the summary is written, kick off the weekly public report (its own agent; model overridable via
|
||||
REPORT_BACKEND/REPORT_MODEL, defaults to opencode-go/glm-5.2): **`python3 /srv/cc-ci/cc-ci-plan/launch-report.py fresh`** (use `fresh`, not `start` — the report
|
||||
is a one-shot and must always run a NEW session for THIS week, even if a previous report session is
|
||||
still around). It runs `/recipe-report`, reviews this run + the live recipe/PR state, and publishes to
|
||||
https://report.ci.commoninternet.net. Fire-and-forget — it runs independently; you can then go idle.
|
||||
|
||||
Reference in New Issue
Block a user