autonomic-bot
1daf0fa616
Operator disbelieved discourse's '133 CVEs fixed' — correctly. Two defects made it confidently wrong: 1. ONE WINDOW APPLIED TO EVERY IMAGE. The scan queries all source repos in the recipe's registry (app + redis/postgres/nginx sidecars) but judged them all with the APP's version window. 34 of the 133 were redis advisories, including CVE-2021-21309 — patched in redis 6.0.11 back in 2021 — scored as 'fixed by this upgrade' purely because 6.0.11 sits numerically inside discourse's 3.5.3 -> 2026.7.1 range. Only the PRIMARY app repo is now classified; other sources are reported as unclassified so they stay visible without inflating the count. 2. VERSION-SCHEME CHANGES BREAK ORDERING. discourse moved semver -> calver (3.5.3 -> 2026.7.1), so 2025.12.2 compares 'newer' than 3.5.3 while shipping earlier. Numeric comparison cannot order that. The scan now detects a leading- component jump >= 100, refuses to classify, and says so in the block: the count is '0 by refusal, not by evidence — read the vendor's release notes'. Refusing to answer beats answering wrongly: a fabricated 133 in a public security report is worse than an explicit 'cannot determine'. Verified after the fix: discourse 133 -> 0 (with the refusal caveat), gitea still exactly 2 (both criticals, patched 1.27.1), keycloak 7 all genuinely from keycloak/keycloak patched in 26.7.1, plausible 1. No other count changed.
cc-ci-orchestrator
Orchestrator workspace for building the cc-ci Co-op Cloud recipe CI server. The plan, launch
tooling, and loop prompts live in cc-ci-plan/; see AGENTS.md for the
roles and operating model. Secrets (.testenv) are gitignored — never commit them.
Run the orchestrator in tmux (survives disconnects + closing your laptop)
Keep this supervising session alive on the host with tmux, and use --remote-control so you can
watch/steer it from claude.ai/code (or the mobile app).
# 0. Exit any running orchestrator session first — a conversation can't be resumed while it's live:
# /exit (inside Claude) or Ctrl-D
# 1. Start a detachable tmux session on this host
tmux new -s orchestrator
# 2. Inside tmux, resume the orchestrator conversation WITH remote control:
claude --resume autonomous-orchestrator \
--remote-control "autonomous-orchestrator" \
--dangerously-skip-permissions
# - If name-resume opens a picker instead of resuming directly, choose "autonomous-orchestrator".
# - Or resume by the stable session id (more deterministic in a fresh pane):
# claude --resume 34a80a99-b37e-4809-b8da-ccc9fafe785e \
# --remote-control "autonomous-orchestrator" --dangerously-skip-permissions
# 3. Detach — the process keeps running: press Ctrl-b, then d
Reconnect later
- On this host:
tmux attach -t orchestrator - From anywhere: claude.ai/code → the
autonomous-orchestratorsession
Why it survives: tmux keeps the claude process alive across SSH disconnects and your laptop
closing; remote-control runs outbound from this host to Anthropic, so it stays connected
regardless of the viewer. After a host reboot, re-run steps 1–2.
Two different "names":
--resume <name|id>selects the conversation to restore (shown in the/resumepicker); the--remote-control "<name>"value is only the web display label and resumes nothing. Resuming reuses the same session id each time (stays34a8…) — don't pass--fork-sessionunless you intend to branch a new conversation.Already inside a live session and just want the web surface? Run
/remote-control— no exit/resume.
Kick off / supervise the loops
cd /srv/cc-ci/cc-ci-plan
./launch.sh start # Builder + Adversary loops (interactive --remote-control in tmux) + watchdog
./launch.sh status # session + DONE state
./launch.sh logs builder|adversary|watchdog
./launch.sh stop
Full supervision guide, credential map, and the Incus VM fallback are in
cc-ci-plan/kickoff.md and cc-ci-plan/plan.md §1.5.