autonomic-bot
46ace30b4d
Follow-up to the nginx blind spot. Sweeping all 22 recipes for sources whose CVEs are USABLE (structured advisory feed, or a changelog attributable to releases) rather than merely visible. Before the changelog-attribution fix: 20 unusable sources. After: 5, and all five are redundant - the same project also publishes an advisory feed (redis, gitea, minio, clickhouse), so nothing is actually lost. One real find, same shape as nginx: ONLYOFFICE/DocumentServer publishes NO GitHub advisories, and the registry pointed its CHANGELOG.md at the GitHub *blob* page - 636KB of markup in which the release headings do not survive HTML-stripping, so 24 CVEs were visible and NONE attributable. The raw URL attributes all 24. Rather than fix one registry line, advisory-scan now normalises github.com/../blob/.. to raw.githubusercontent.com, which fixes every entry present and future. lasuite-drive bumps documentserver, so this was live. Genuinely blind after all that: mattermost-lts and mumble - no advisory feed, no attributable changelog, no CVE data anywhere the registry points. mattermost is the notable one: its bulletins are client-side rendered, so a regex sweep sees nothing. Their scans can report 0 while nothing was measured, so /cve-check now renders those recipes as ? and says why. The audit output distinguishes a blind RECIPE from an unparseable PAGE, because conflating them made 5 harmless redundancies look like 5 gaps.
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.