1bcb2ed8fe
status(rcust): ## DONE — M1 ( 01f9f70) + M2 ( 3245150) both PASS, no VETO; phase complete
continuous-integration/drone/push Build is passing
2026-06-11 01:16:27 +00:00
3245150982
review(rcust): M2 PASS — merged-main regression sweep cold-verified. Canaries 7/7 (re-ran myself incl. false-green detector); all 21 recipes reconciled (every baseline deviation proven rcust-neutral via same-ref old-vs-new A/B or stale-schema w/ coverage preserved, all in DEFERRED); drone-path 356/357 custom success; customizations execute (manifest 21/21, mumble tcp, ghost overlay+chaos, immich seeds); zero leaks; both fix-forwards cleared. M1+M2 both PASS → DoD handshake satisfied, Builder may write ## DONE. No VETO.
continuous-integration/drone/push Build is passing
2026-06-11 01:15:45 +00:00
f7b9b6f167
status(rcust): Current section → M2 CLAIMED
continuous-integration/drone/push Build is passing
2026-06-11 01:07:13 +00:00
d7f85c3f28
claim(rcust): M2 — merge+2 approved fix-forwards green, canaries 7/7, 21/21 reconciled vs corrected baseline (3 lasuite via accepted L5≡L4+OIDC equivalence, bluesky-pds justified exclusion), drone path covered (356/357), zero leaks
continuous-integration/drone/push Build is passing
2026-06-11 01:06:48 +00:00
89dec5188f
inbox(rcust): consumed 01:12Z be2026a-cleared note; bluesky-pds filed in DEFERRED.md as non-rcust upstream image breakage (justified M2 exclusion, A/B-proven harness-neutral)
continuous-integration/drone/push Build is passing
2026-06-11 01:00:32 +00:00
24a203a098
review(rcust): be2026a fix-forward CLEARED (all 3 conditions met, independently verified) + ACCEPT L5≡L4+OIDC-pass equivalence — lasuite-* L5 baselines stale ( c51cd84 4-rung predates rcust, git-proven), rcust innocent, OIDC coverage preserved. Consumed 01:10Z inbox. M2 still open: bluesky upstream-breakage note, drone-path runs, zero-leak, my sample re-check
continuous-integration/drone/push Build is passing
2026-06-11 00:59:29 +00:00
f359069d40
inbox(rcust): m2p2 GREEN rc=0 3m19s (both fix-forwards exercised end-to-end; OIDC+MinIO pass) — level=4 vs condition-1 'L5' explained: 6-rung ladder removed on MAINLINE 06-09 (46e2cdb/c51cd84 PR#6) pre-merge; equivalence proposed (L4 all-pass + requires_deps OIDC PASSED)
continuous-integration/drone/push Build is passing
continuous-integration/drone Build is passing
2026-06-11 00:57:12 +00:00
a13a83a775
status(rcust): discourse A/B CLOSED — old==new byte-identical upgrade-HC1 at baseline ref+invocation (harness-neutral, env drift since 06-05; branch-tip/tag/abra-pin drift eliminated); m2p2 lasuite-drive binding proof started
continuous-integration/drone/push Build is passing
2026-06-11 00:51:10 +00:00
4428e76f48
review(rcust): be2026a merge cold-verified — merged lifecycle.py + test file byte-identical to branch (condition #2 met); m2p-lasuite-drive L0 = diagnosed pre-fix symptom; awaiting discourse A/B + post-fix L5
continuous-integration/drone/push Build is passing
2026-06-11 00:42:54 +00:00
b4505acbbd
status(rcust): disclosed SIGINT shortcut of doomed m2p overlay install burn (KeyboardInterrupt at the diagnosed converge line); m2p2 is the binding proof
continuous-integration/drone/push Build is passing
2026-06-11 00:39:44 +00:00
9715ab5c50
status(rcust): be2026a merged as 6cabbe7 (build 350 green on 914c166); m2p2-lasuite-drive post-fix proof queued behind discourse A/B
continuous-integration/drone/push Build is passing
2026-06-11 00:38:06 +00:00
914c1663b5
inbox(rcust): consumed 00:31Z conditional APPROVE — merging be2026a, post-merge lasuite-drive re-run queued behind discourse A/B pair
continuous-integration/drone/push Build is passing
2026-06-11 00:33:07 +00:00
6cabbe73b7
fix(harness): merge fix/converged-oneshot @ be2026a — services_converged completed-one-shot rule (rcust M2 fix-forward #2 , Adversary-approved a531746)
2026-06-11 00:33:07 +00:00
a531746e53
review(rcust): APPROVE fix-forward be2026a (services_converged completed-one-shot rule) — cold-verified diff+7 tests+199 unit+lint on fresh checkout, no false-green path (HTTP floor + minio custom test independent); conditional on post-merge lasuite-drive L5 + merged-diff==branch-diff + discourse PR=2 A/B cold re-check. Consumed 00:40Z inbox
continuous-integration/drone/push Build is passing
2026-06-11 00:31:54 +00:00
49d796d9ac
status(rcust): m2p-lasuite-drive WILL land L0 — second P2b regression (completed one-shot 0/1 vs services_converged) root-caused live; fix on branch be2026a awaiting approval
continuous-integration/drone/push Build is passing
2026-06-11 00:28:33 +00:00
73421dabb4
inbox(rcust): lasuite-drive SECOND P2b regression root-caused live (completed one-shot 0/1 poisons services_converged after hook moved pre-assert) — fix-forward on branch fix/converged-oneshot @ be2026a, 199 unit + lint green, awaiting approval
continuous-integration/drone/push Build is passing
2026-06-11 00:27:49 +00:00
be2026aafb
fix(harness): services_converged — a replica deficit explained entirely by Complete tasks is converged (triggered one-shot, rcust M2 lasuite-drive root cause)
continuous-integration/drone/push Build is passing
2026-06-11 00:26:53 +00:00
77a9415b37
inbox(rcust): consumed Builder 00:20Z reply — proof runs confirmed queued; m2b-discourse/sidekiq/bluesky facts noted for independent cold-verify (not taken on trust)
continuous-integration/drone/push Build is passing
2026-06-11 00:06:42 +00:00
4dcfb5ba96
review(rcust): M2 proof in flight — Builder running discourse PR=2 A/B (new vs old main) + lasuite-drive post-fix; self-correct my m2b L1 finding (PR=0 confound on HC1 re-checkout) — awaiting PR=2 results to cold-verify
continuous-integration/drone/push Build is passing
2026-06-11 00:06:16 +00:00
1ec0e772e8
inbox(rcust): consumed 23:53Z asks — lasuite-drive proof RUNNING, discourse same-ref 2x2 queued (new-main PR=2 + old-main PR=2 @7ae7b0f); m2b-discourse HC1 facts pinned (re-checkout persisted, eb96de94=base tag, sidekiq line benign); bluesky-pds = upstream image breakage (MODULE_NOT_FOUND x3, harness-neutral)
continuous-integration/drone/push Build is passing
2026-06-11 00:06:13 +00:00
40b59b356b
review(rcust): M2 proof-run cold analysis — 3/6 (immich/mattermost/plausible) reproduce baseline L4 at baseline ref on merged main (restructure innocent); discourse L4->L1 upgrade-HC1 at baseline ref UNexplained (A/B was at wrong ref) + lasuite-drive needs fresh L5 post-fix-forward; M2 OPEN
continuous-integration/drone/push Build is passing
2026-06-10 23:54:36 +00:00
5c0676b7d0
note(rcust): M2-prep hook-port audit — only lasuite-drive flipped best-effort->fatal (fix approved); lasuite-docs exit1->exit0 is intentional P2b (F2-11-gated); all other ops.py pure mechanical ctx migration. Closes M1-method gap (key-diff missed hook bodies)
continuous-integration/drone/push Build is passing
2026-06-10 20:55:01 +00:00
efd7efc32b
inbox(rcust): consumed 20:53Z approval — fix-forward pushed as 57c66ad; proof re-run at baseline REF queued behind tests 2+3
continuous-integration/drone/push Build is passing
2026-06-10 20:53:52 +00:00
1357544301
fix(tests): restore best-effort semantics of lasuite-drive pre_install bucket trigger (rcust M2 regression)
...
continuous-integration/drone/push Build is passing
The P2b port of setup_custom_tests.sh -> ops.py::pre_install made the 90s bucket-poll timeout a
fatal AssertionError; the original shell hook fell through on timeout BY DESIGN (best-effort) and
the custom-tier MinIO storage test is the real gate for a genuinely missing bucket. Live evidence:
in both M2 sweep failures the bucket landed just after the window and every later tier including
the custom MinIO test passed. Warn loudly + continue, exactly the old semantics.
Adversary-approved fix-forward (REVIEW-rcust 57c66adnoreply@anthropic.com >
2026-06-10 20:53:31 +00:00
57c66add51
review(rcust): APPROVE lasuite-drive pre_install fix-forward (scoped to line-54 bucket-poll raise→best-effort; verified old=best-effort, custom MinIO test is real gate, no coverage loss); conditioned on L5 re-run + my diff re-verify. Auditing other shell->python hook ports for same drift
continuous-integration/drone/push Build is passing
2026-06-10 20:52:53 +00:00
a95fad4fa0
inbox(rcust): lasuite-drive P2b port regression root-caused (best-effort poll became fatal assert) — trivial fix-forward proposed, awaiting Adversary approval
continuous-integration/drone/push Build is passing
2026-06-10 20:50:31 +00:00
b9abf48116
inbox(rcust): consumed 20:33Z ACK — ref-mismatch independently confirmed; tests 2+3 concurred; proceeding
continuous-integration/drone/push Build is passing
2026-06-10 20:34:36 +00:00
4cb1f57e2c
inbox(rcust): consumed Builder 20:35Z ref-mismatch heads-up + ACK — independently confirmed sweep ran default-branch heads (7d53d4ec/da159375) != baseline PR refs; concur tests 2+3 separate harness×content; will run own cold A/B at claim
continuous-integration/drone/push Build is passing
2026-06-10 20:33:56 +00:00
e30a414ce1
inbox(rcust): heads-up — restore cluster is a REF-mismatch vs baseline (sweep ran old default heads; baselines were PR-head runs); baseline-REF re-runs + old-main A/B queued
continuous-integration/drone/push Build is passing
2026-06-10 20:32:33 +00:00
41033b4500
inbox(rcust): consumed 20:15Z follow-up — restore cluster confirmed pre-existing, VETO threat withdrawn; proceeding to satisfy the 4 M2 PASS conditions (re-runs at baseline, canary+zero-leak, log sample, !testme x2)
continuous-integration/drone/push Build is passing
2026-06-10 20:19:12 +00:00
a7a558ada3
note(rcust): M2 follow-up — confirmed restore cluster is the PRE-EXISTING truncated-dump race (documented in discourse BACKUP_VERIFY docstring on pre-merge 49fb818); VETO-threat withdrawn; stated M2 PASS conditions (re-runs at baseline + spot-checks)
continuous-integration/drone/push Build is passing
2026-06-10 20:18:26 +00:00
37dcfab07d
inbox(rcust): consumed Adversary 20:13Z restore-cluster heads-up — ACK: serial re-runs of all 6 already in flight (/root/m2-rerun-logs/, results m2rr-*); will ALSO run immich on OLD main (pre-merge c2508c7) serially in the same env as the requested A/B regardless of re-run outcome; no M2 claim until both legs are documented in STATUS
continuous-integration/drone/push Build is passing
2026-06-10 20:18:13 +00:00
ffc88848f3
note(rcust): M2 heads-up — restore-failure cluster (discourse/immich/plausible/mattermost ci_marker-missing) blocks M2 PASS; evidence says infra/pre-existing not restructure (restore orchestration unchanged, no BACKUP_VERIFY correlation, peers pass); suggest A/B vs old main (NOT a verdict)
continuous-integration/drone/push Build is passing
2026-06-10 20:17:14 +00:00
85d14101ef
status(rcust): M2 sweep first pass — canaries 7/7, 15/21 at baseline, 6 flake-shaped reds re-running serially; spot-grep evidence + zero leaks
continuous-integration/drone/push Build is passing
2026-06-10 20:14:05 +00:00
9aa0c5d624
status(rcust): fix stale Current section — M2 in progress
continuous-integration/drone/push Build is passing
2026-06-10 19:33:23 +00:00
4d342a2c5d
status(rcust): M1 PASS — merged to main 01e6d49, push build 326 green; M2 canaries running, sweep driver staged
continuous-integration/drone/push Build is passing
2026-06-10 19:33:05 +00:00
01e6d497ba
Merge branch 'restructure/recipe-custom' — recipe-customization restructure (rcust M1 PASS @858e0f5, REVIEW-rcust 01f9f70)
...
continuous-integration/drone/push Build is passing
Single registry-backed meta loader, legacy key/path deletion, uniform ctx hooks, custom-test
placement rule + fixtures, customization manifest, docs. M2 real-CI regression sweep follows.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com >
2026-06-10 19:28:38 +00:00
01f9f70970
review(rcust): M1 PASS @858e0f5 — cold unit 192+conc 23+lint PASS; coverage diff 0 real deltas/21 (mumble byte-identical, deleted keys all accounted); 18=18 asserts no weakening (no VETO); validation gaps closed; R2 delivered end-to-end; HC2/F2-11/generic-floor intact; manifest secret-redaction verified surgical. DONE still gated on M2 (real-CI sweep).
continuous-integration/drone/push Build is passing
2026-06-10 19:27:49 +00:00
c2508c7fd2
claim(rcust): M1 — P1–P6 complete on restructure/recipe-custom @ 858e0f5; unit 192 + concurrency 23 + lint PASS; baseline matrix committed
continuous-integration/drone/push Build is passing
2026-06-10 19:13:36 +00:00
8984b57b35
status(rcust): P6 complete ( da558ca) + Adversary inbox consumed — manifest redaction landed ( 858e0f5); M1 prep starting
continuous-integration/drone/push Build is passing
2026-06-10 19:10:00 +00:00
858e0f582f
fix(harness): redact secret-named meta values in the customization manifest (rcust)
...
continuous-integration/drone/push Build is passing
Adversary heads-up (inbox 2026-06-10T19:06Z): meta values are repo-public by construction, but
the manifest lands on the dashboard — a field literally named SECRET_KEY_BASE showing a value
(plausible's committed CI dummy) is needless secret-scan noise. Mask values whose key NAME is
secret-shaped (SECRET|PASSWORD|TOKEN|CREDENTIAL|word-segment KEY), top-level and nested dict
keys; the key name stays visible. Unit test pins redacted vs passthrough (KEYCLOAK_URL).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com >
2026-06-10 19:09:09 +00:00
da558ca946
docs: P6 — rewrite customization docs to the restructured end state (rcust)
...
continuous-integration/drone/push Build is passing
recipe-customization.md: review spec -> reference. Single registry-backed loader + validation
rules + HookCtx convention (§4); generated key table kept byte-identical (sync test); §5 end-state
shape (op_state/deps fixtures, ctx ops.py, placement rule, first-class compose.ccci.yml, no
setup_custom_tests.sh); §7 manifest block + dev-only CCCI_SKIP_GENERIC*; §8 rewritten as
restructure outcomes (R1/R2/R3/R5/R6/R7/R8 resolved + how, R4 mitigated by manifest, R9
rejected-by-decision); §9 index updated to the new symbols.
testing.md: install-time deps isolation replaces the setup_custom_tests step in the invariant
(generic still never depends on custom — failure isolation via requires_deps/F2-11); ops.py
example to pre_<op>(ctx); placement rule; generic opt-out now documented LOCAL-DEV-ONLY env with
CI !! warning (declarative SKIP_GENERIC gone); partial key list points at the generated table.
enroll-recipe.md: tree + worked examples updated (lasuite-docs install-time OIDC wiring +
install_steps.sh; mumble post-F2-14c shape — UPGRADE_EXTRA_ENV native overlay, private _
constants, no CHAOS_BASE_DEPLOY); deps fixture (entry.domain) replaces deps_apps; ctx hook
signatures; compose.ccci.yml first-class bullet; key list points at the generated table.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com >
2026-06-10 19:07:41 +00:00
5ccc0d1c34
note(rcust): interim pre-review of frozen P5 ( 68954be) — cold unit 191 + lint PASS reproduced; manifest exposes NO generated/real secrets (HC2-honoring, pure presentation); one non-blocking heads-up re plausible SECRET_KEY_BASE public-dummy on dashboard (NOT an M1 verdict)
continuous-integration/drone/push Build is passing
2026-06-10 19:07:24 +00:00
52f5266dfb
status(rcust): P5 complete on branch ( 68954be) — unit 191 green + lint PASS; starting P6
continuous-integration/drone/push Build is passing
2026-06-10 18:58:33 +00:00
68954be53e
feat(harness): P5 — customization manifest (rcust)
...
continuous-integration/drone/push Build is passing
One block at run start answering "what does this recipe customize?" across every surface
(non-default recipe_meta keys, ops.py pre-ops, install_steps.sh, compose.ccci.yml, lifecycle
overlays by source, custom-test counts, active CCCI_SKIP_GENERIC* env overrides — !!-flagged when
riding a CI run, P2c), printed to the run log and embedded verbatim in results.json under
"customization". Pure presentation — building/printing it never influences a verdict; the
manifest honors the HC2 repo-local gate so it never advertises code the run will not execute.
Unit tests: synthetic recipe exercising every surface -> complete + deterministic + JSON-clean;
HC2 invisibility; env-override flagging; render golden lines; build_results threads the dict
verbatim (key always present, None when absent).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com >
2026-06-10 18:57:26 +00:00
270476beb3
note(rcust): interim pre-review of frozen P4 ( 29a28e2) — cold unit 184 + lint PASS reproduced; placement-rule claim holds (0 non-lifecycle top-level customs), HC2 intact, tests strengthened not weakened (NOT an M1 verdict)
continuous-integration/drone/push Build is passing
2026-06-10 18:53:32 +00:00
ff09c4075b
status(rcust): P4 complete on branch ( 29a28e2) — unit 184 green + lint PASS; starting P5
continuous-integration/drone/push Build is passing
2026-06-10 17:14:38 +00:00
63befd05b0
note(rcust): interim pre-review of frozen P3 — mechanical migration held (0 changed asserts), HookCtx complete, legacy-sig guard live-probed PASS, coverage diff still 0/21 (NOT M1)
continuous-integration/drone/push Build is passing
2026-06-10 17:14:37 +00:00
29a28e2028
feat(harness): P4 — custom-test ergonomics (rcust)
...
continuous-integration/drone/push Build is passing
Placement RULE: discovery.custom_tests covers ONLY functional/ + playwright/ —
the top-level test_*.py glob for recipe dirs is removed (top level is reserved
for lifecycle overlays; zero in-repo users of top-level custom tests, verified
by sweep). Lifecycle-name exclusion inside the subdirs stays as the double-run
safety net. HC2 default-deny unchanged (repo-local custom now pinned via
functional/ in the gate test).
New conftest fixture op_state: parses $CCCI_OP_STATE_FILE (op context: versions,
artifact paths), skipping with a clear reason when unset/absent/unparseable —
overlay tests read op facts from the fixture instead of hand-parsing env (zero
existing hand-parsers found; the fixture is the documented path forward). deps
fixture landed in P2d.
Unit tests: placement-rule discovery tests (top-level custom NOT discovered;
functional/playwright are; misfiled lifecycle names excluded), op_state fixture
contract (reads file / skips without env / skips on missing file), deps fixture
attribute sugar.
Verified on cc-ci: cc-ci-run -m pytest tests/unit -q -> 184 passed; scripts/lint.sh -> PASS.
2026-06-10 17:14:21 +00:00
802b2792a7
note(rcust): interim pre-review of frozen P1+P2 — fallout clean, typo gate PASS, coverage diff 0/21 deltas, validation gaps closed (NOT an M1 verdict; M1 unclaimed)
continuous-integration/drone/push Build is passing
2026-06-10 17:11:41 +00:00
