Add Phase-2 plan: comprehensive per-recipe test authoring (after Phase-1 DONE)
Phase 2 fills the CI machine with good tests for every maintained Co-op Cloud app, using references/recipe-maintainer as the corpus: port a comparable cc-ci test for EACH existing recipe-maintainer test (parity, tracked in PARITY.md) + >=2 new recipe-specific functional tests per recipe, plus real backup data-integrity and SSO dependency handling. Reuses the Phase-1 harness/stages/trigger/resource-caps; adds test content + small shared-harness ports from helpers.py. Linked from the package README. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -14,7 +14,9 @@ autonomous Claude loops (a Builder and an adversarial Reviewer) running over day
|
||||
|
||||
| File | Purpose |
|
||||
|---|---|
|
||||
| `plan.md` | The plan. Agents treat it as their single source of truth. |
|
||||
| `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** (starts after Phase-1 `## DONE`): author comprehensive per-recipe tests — port every recipe-maintainer test + ≥2 recipe-specific tests per app. |
|
||||
| `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`. |
|
||||
|
||||
Reference in New Issue
Block a user