recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reorder: Phase 1c before 1b (refactor first, then review/lint + full re-verify)

Browse Source 
1c (full git reproducibility: cc-ci-secrets split, cert-in-sops, genuine D8 live rebuild)
now runs before 1b. This way 1b's review/lint and its final cold re-verification of all
D1-D10 cover the final refactored state (incl. the secrets split) and the genuine post-1c
D8 — rather than reviewing pre-refactor code and re-verifying a flawed D8. Updated status
lines in 1b/1c and the README ordering. Sequence: 1 -> 1c -> 1b -> 2 -> 2b -> 3.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
notplants
2026-05-27 15:51:07 +01:00
co-authored by Claude Opus 4.7
parent c6d27b251a
commit 9d13bb0b58
3 changed files with 11 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cc-ci-plan/plan-phase1b-review-lint.md
+6 -4
View File
@@ -1,10 +1,12 @@
# cc-ci Phase 1b — Review & lint pass (Autonomous Build Plan)
**Status:** QUEUED — a **bounded** pass that runs after Phase 1 (`plan.md`) reaches `## DONE`, and
**before** Phase 2 (`plan-phase2-recipe-tests.md`).
**Status:** QUEUED — a **bounded** pass that runs after Phase 1 **and Phase 1c**
(`plan-phase1c-full-reproducibility.md`), and **before** Phase 2 (`plan-phase2-recipe-tests.md`). It
runs *after* 1c on purpose: the review/lint + full D1–D10 re-verification then covers the final,
refactored state (the `cc-ci-secrets` split, cert-in-sops, the genuine D8 live rebuild).
**Transition:** **manual** (operator kicks it off).
**Builds on:** the complete Phase-1 codebase (flake/modules, `runner/` + harness, the comment-bridge,
dashboard, scripts, the first recipes' tests, docs).
**Builds on:** the complete post-1c codebase (flake/modules, `runner/` + harness, the comment-bridge,
dashboard, scripts, the first recipes' tests, the `cc-ci-secrets` split, docs).
**Owner agents:** same Builder + Adversary loops (`plan.md` §6/§7). Here the Adversary also acts as
**white-box reviewer** (reads the code, not just black-box behavior).
**This file's path:** `/srv/cc-ci/cc-ci-plan/plan-phase1b-review-lint.md`