2 Commits

Author	SHA1	Message	Date
autonomic-bot	f7971d949d	2pc: drop the pull-through registry cache — single host makes it marginal; keep PC1 prune-policy only ... Operator (2026-05-29): on one host Docker's local image store already IS the cache; the churn was over-pruning, not a missing cache. So 2pc = conservative prune policy + confirm local-store retention + daemon auth (PC1-3). Registry pull-through cache deferred to IDEAS with a concrete revisit condition (multi-node, or measured cold-deploy bottleneck on recreate-surviving storage). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-05-29 09:24:56 +01:00
autonomic-bot	0352cb5607	plan: Phase 2pc — image pull-through cache + sane prune policy (front-loaded perf interjection) ... Operator-directed (2026-05-29): front-load the two EVIDENCE-BASED image wins before grinding the remaining deploy-heavy recipes — Phase 2 pauses, 2pc runs, Phase 2 resumes (seq: …2w 2pc 2 2b 3 4). PC1: conservative prune (no reflexive `prune -af`, never mid-run, keep base images) — kills the documented prune→re-pull→rate-limit churn. PC2: local registry:2 pull-through cache for docker.io, PAT-authenticated, Nix-reconciled, daemon registry-mirror → transparent to abra/swarm; subsequent pulls (across recipes/runs/post-prune) are local → faster deploys + rate-limit gone. Bounded scope: these two only; concurrency/readiness-tuning stay in measurement-driven 2b. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-05-29 09:20:30 +01:00