docs(runbook): record Phase 1 execution and two deviations #4

Merged

john merged 1 commit from docs/phase1-executed into dev

2026-07-27 01:44:21 +00:00

john commented

2026-07-27 01:42:08 +00:00

Owner

superclean-kernel is live on lumeria against superclean-prod-db, non-routed, nine tables created, one owner principal, SuperClean data unchanged.

Records two deviations for the next company: [skip cd] did not suppress the deploy on superclean-sys2 despite the merge subject carrying it, and the first kernel deploy failed at image build because the Dockerfile read the index credential only from a BuildKit secret.

superclean-kernel is live on lumeria against superclean-prod-db, non-routed, nine tables created, one owner principal, SuperClean data unchanged. Records two deviations for the next company: [skip cd] did not suppress the deploy on superclean-sys2 despite the merge subject carrying it, and the first kernel deploy failed at image build because the Dockerfile read the index credential only from a BuildKit secret.

john added 1 commit

2026-07-27 01:42:08 +00:00

docs(runbook): record Phase 1 execution and two deviations

CI / Docker Build (pull_request) Has been skipped

Details

CI / Backend (pull_request) Has been skipped

Details

CI / Deploy (pull_request) Has been skipped

Details

CI / Detect Changes (pull_request) Has been cancelled

Details

cfea33db4b

superclean-kernel is live on lumeria against superclean-prod-db, non-routed, nine
tables created, one owner principal, SuperClean data unchanged.

Two deviations worth carrying forward. [skip cd] did not suppress the deploy on
superclean-sys2 even though the merge subject carried it, so SuperClean production was
rebuilt unintentionally; harmless here, but do not rely on the mechanism. And the first
kernel deploy failed at image build because the Dockerfile read the index credential
only from a BuildKit secret, which dokku git:sync cannot mount — every company kernel
app needs the docker-options build arg.