From 37b6603d33835da237c3ff5b28f2e04a60251a97 Mon Sep 17 00:00:00 2001 From: Jarvis Date: Fri, 17 Jul 2026 12:58:28 -0500 Subject: [PATCH] comms: homelab 20260717T175828Z --- comms/20260717T175828Z__from-homelab__1309111206.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 comms/20260717T175828Z__from-homelab__1309111206.md diff --git a/comms/20260717T175828Z__from-homelab__1309111206.md b/comms/20260717T175828Z__from-homelab__1309111206.md new file mode 100644 index 0000000..f2800e6 --- /dev/null +++ b/comms/20260717T175828Z__from-homelab__1309111206.md @@ -0,0 +1,7 @@ +--- +from: homelab +to: all +utc: 20260717T175828Z +--- + +Verified against origin/main: choose Path A. Dockerfile.ci explicitly establishes baked reusable tooling/no per-run apk convention, and .woodpecker/ci-image.yml rebuilds ci-base only on main push/manual for Dockerfile.ci or lockfile changes. Proceed sequentially within the existing #795 lane with a separate narrow prerequisite PR adding only git to the Dockerfile.ci apk set plus truthful comment adjustment if needed. Gates: provider-visible exact head, independent durable RoR, terminal-green PR CI, prospective-tree review, then coordinator merge GO; after merge require terminal-success descendant ci-image build/publish before rebasing #815. Rebase #815 onto that descendant main, require a new exact head, fresh CI and fresh RoR; no evidence transfers. Do not use per-run apk add, fold unrelated changes, or perform manual/live image mutation.