recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
7c77aec7abfba0cfe7c4bb59e07d962feda8340a
cc-ci-orchestrator/cc-ci-plan
History
autonomic-bot 7c77aec7ab Add Phase-3 plan: beautiful YunoHost-style results (levels + image comment + dashboard) 
Phase 3 (after Phase-2 DONE, manual transition): compute a per-run quality LEVEL, post an
image-forward Gitea PR comment in the YunoHost shape (marker + status/level badge + a
rendered summary card containing a real app screenshot, linking to the run), and polish the
overview dashboard to a ci-apps.yunohost.org look/feel with per-recipe level badges +
screenshots. Reuses the Phase-1 dashboard/bridge/Playwright; presentation never changes the
verdict; no secrets in any artifact; cosmetics never block the pipeline. Linked from README.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-27 04:01:21 +01:00
..
prompts
Initial commit: cc-ci autonomous orchestrator
2026-05-26 20:46:28 +01:00
brief.md
Initial commit: cc-ci autonomous orchestrator
2026-05-26 20:46:28 +01:00
IDEAS.md
Add cc-ci-plan/IDEAS.md: deferred-ideas backlog; park optional webhook self-registration
2026-05-27 02:42:34 +01:00
kickoff.md
Initial commit: cc-ci autonomous orchestrator
2026-05-26 20:46:28 +01:00
launch.sh
Initial commit: cc-ci autonomous orchestrator
2026-05-26 20:46:28 +01:00
plan-phase2-recipe-tests.md
Phase-2 plan: harden Adversary mandate — no skipped tests / corners cut
2026-05-27 03:50:33 +01:00
plan-phase3-results-ux.md
Add Phase-3 plan: beautiful YunoHost-style results (levels + image comment + dashboard)
2026-05-27 04:01:21 +01:00
plan.md
plan §4.2/§4.3: MAX_TESTS via DRONE_RUNNER_CAPACITY + native queue/timeout; teardown after each run
2026-05-27 02:45:26 +01:00
README.md
Add Phase-3 plan: beautiful YunoHost-style results (levels + image comment + dashboard)
2026-05-27 04:01:21 +01:00

README.md

cc-ci-plan

Self-contained handoff package for building the cc-ci Co-op Cloud recipe CI server with two autonomous Claude loops (a Builder and an adversarial Reviewer) running over days.

Start here

  1. Read plan.md — the full plan and single source of truth (mission, Definition of Done, architecture, milestones, the two-agent coordination protocol, loop discipline).
  2. Read kickoff.md — how to launch and supervise the loops.
  3. Run ./launch.sh start to bring up both loops + the watchdog.

Files

File Purpose
plan.md The Phase-1 plan (build the CI server). Agents treat it as their single source of truth.
plan-phase2-recipe-tests.md Phase 2 (after Phase-1 ## DONE): author comprehensive per-recipe tests — port every recipe-maintainer test + ≥2 recipe-specific tests per app.
plan-phase3-results-ux.md Phase 3 (after Phase-2 ## DONE): beautiful YunoHost-style results — per-run level, image-forward PR comment (badge + summary card + app screenshot), polished dashboard.
IDEAS.md Deferred/future ideas, parked out of current scope.
brief.md The original one-page brief (context only; plan.md supersedes it).
kickoff.md Launch & supervision guide.
launch.sh Starts both loops + a watchdog; restarts dead loops; stops on ## DONE.
prompts/builder.md Builder loop prompt (fed to claude by the script).
prompts/adversary.md Adversary loop prompt.

Before launching

  • Set the org in plan.md (git.autonomic.zone/recipe-maintainers/cc-ci) and lock the six proof recipes (§8).
  • Ensure the launching shell has: SSH+sudo to cc-ci, the Gitea token, git.autonomic.zone access.
  • Preconfigure test-app DNS + TLS (plan §4.0): point a wildcard *.ci.commoninternet.net record at a gateway that TLS-passthroughs to cc-ci, and pre-issue the wildcard cert (*.ci.commoninternet.net + ci.commoninternet.net, via Gandi DNS-01) into /var/lib/ci-certs/live/ on cc-ci. The agent handles everything else on cc-ci (Traefik file provider → that cert, swarm, routing) and does no ACME; renewal (~90 days) is an out-of-band operator task, so the DNS token never goes to the agent.
  • export CC_CI_REPO=https://git.autonomic.zone/recipe-maintainers/cc-ci.git so the watchdog can detect ## DONE.

What "done" means

The loops stop only when all of plan.md §2 (D1–D10) hold and the Adversary has independently re-verified each within 24h. The watchdog then tears the loops down automatically.