launch-*: hardcode the default tier to go + glm-5.3-flash (zen model ids are dead on this host)
Every manual launch of launch-report/launch-upgrader bypasses the systemd EnvironmentFile (/srv/cc-ci/upgrader.env sets LOOP_TIER=go + the go models) and fell back to hardcoded zen defaults, which die instantly here (ProviderModelNotFoundError: opencode/glm-5.2 — the host holds no ZEN key and zen models vanished from the provider catalogue, 2026-09-14). This crashed the 2026-09-11 report agent at launch and again on every manual retry. - launch-upgrader.py + launch-report.py: default TIER go, go-tier model default glm-5.3-flash (mirrors the 2026-09-08 operator choice in upgrader.env); zen stays an explicit opt-in on a host with a key. - launch-supervisor.py: default SUPERVISOR_MODEL glm-5.3-flash. - docstrings updated to match. Verified with env -i: bare invocation resolves tier=go, model=opencode-go/glm-5.3-flash on all three. The 2026-09-11 weekly report is published live (report.ci.commoninternet.net/week-2026-09-11.html) after a fresh glm-5.3-flash report run.
This commit is contained in:
@@ -2,8 +2,9 @@
|
||||
"""cc-ci recipe-report launcher — one-shot agent that runs /recipe-report after the weekly upgrade.
|
||||
|
||||
The report agent's model is configured SEPARATELY from the upgrader (REPORT_BACKEND/REPORT_MODEL),
|
||||
but defaults to the same OpenCode subscription on glm-5.2 as the upgrader. The model default tracks
|
||||
the backend+tier (opencode+zen→opencode/glm-5.2, opencode+go→opencode-go/glm-5.2, claude→opus).
|
||||
but defaults to the same OpenCode subscription as the upgrader (now OpenCode GO — the only tier
|
||||
with a key on this host; ZEN models are dead here, see launch-upgrader.py). The model default tracks
|
||||
the backend+tier (opencode+go→opencode-go/glm-5.3-flash, opencode+zen→opencode/glm-5.2, claude→opus).
|
||||
|
||||
Usage:
|
||||
launch-report.py start [DATE] use-or-create the session; runs /recipe-report [DATE]
|
||||
|
||||
Reference in New Issue
Block a user