notes: document bf-22vc5 complete infrastructure blocker summary

Documented all blockers preventing acb-enrichment deployment:
- Forgejo registry down (503)
- forgejo-container-registry secret missing on apexalgo-iad
- iad-ci kubeconfig missing
- Docker Hub image doesn't exist (404)
- Docker daemon access denied

The task cannot be completed without iad-ci kubeconfig to trigger
acb-enrichment-build workflow or Forgejo registry being fixed.

Related: bf-22vc5

notes/bf-22vc5-complete-blocker-summary-2026-06-04.md

@@ -0,0 +1,130 @@
+# bf-22vc5 Complete Infrastructure Blocker Summary
+
+**Date**: 2026-06-04
+**Task**: Deploy P0: build acb-enrichment Docker image and re-enable deployment (apexalgo-iad)
+**Status**: **BLOCKED - Cannot complete without infrastructure access**
+
+## Current Deployment State
+
+### apexalgo-iad Cluster
+- **Deployment**: acb-enrichment
+- **Current image in git**: `forgejo.ardenone.com/ai-code-battle/acb-enrichment:sha-af188b5`
+- **Current image in cluster**: `ronaldraygun/acb-enrichment@sha256:placeholder` (OLD)
+- **Pod status**:
+  - Old pod: `InvalidImageName` (trying to pull placeholder image)
+  - New pod: `Pending` (trying to pull from Forgejo registry)
+- **Replicas**: 0/1 available
+
+### What Changed
+Commit `f57e058` (2026-06-04 07:03) updated the deployment to use Forgejo registry instead of Docker Hub:
+- Old: `ronaldraygun/acb-enrichment@sha256:placeholder` (docker-hub-registry secret)
+- New: `forgejo.ardenone.com/ai-code-battle/acb-enrichment:sha-af188b5` (forgejo-container-registry secret)
+
+## Blockers
+
+### 1. Forgejo Registry Down (PRIMARY BLOCKER)
+```
+HTTP/2 503 from https://forgejo.ardenone.com/v2/
+```
+The Forgejo container registry is not accessible, preventing image pulls.
+
+### 2. Forgejo Registry Secret Missing
+```
+kubectl --server=http://traefik-apexalgo-iad:8001 get secrets -n ai-code-battle
+```
+Shows only `docker-hub-registry`, not `forgejo-container-registry`.
+
+The deployment manifest requires `forgejo-container-registry` but it doesn't exist on apexalgo-iad.
+
+### 3. Docker Hub Image Doesn't Exist
+```
+HTTP/2 404 from https://registry-1.docker.io/v2/repositories/ronaldraygun/acb-enrichment/tags/latest
+```
+The enrichment image was never published to Docker Hub.
+
+### 4. iad-ci Kubeconfig Missing
+```
+~/.kube/iad-ci.kubeconfig: DOES NOT EXIST
+```
+Cannot access iad-ci cluster to:
+- Submit Argo Workflows to build images
+- Check workflow status
+- Trigger manual builds
+
+### 5. Docker Daemon Access Denied
+Cannot build images locally due to socket permissions:
+```
+permission denied while trying to connect to the Docker daemon socket
+```
+
+## What Needs to Happen
+
+To complete this task, ONE of the following paths must be available:
+
+### Path A: Use iad-ci Argo Workflows (RECOMMENDED)
+1. **Obtain iad-ci kubeconfig** from Rackspace Spot UI
+2. Save to `/home/coding/.kube/iad-ci.kubeconfig`
+3. Trigger `acb-enrichment-build` workflow:
+   ```bash
+   kubectl --kubeconfig=/home/coding/.kube/iad-ci.kubeconfig create -f - <<EOF
+   apiVersion: argoproj.io/v1alpha1
+   kind: Workflow
+   metadata:
+     generateName: acb-enrichment-build-manual-
+   spec:
+     workflowTemplateRef:
+       name: acb-enrichment-build
+   EOF
+   ```
+4. Wait for build to complete
+5. Image will be pushed to Docker Hub: `ronaldraygun/acb-enrichment:sha-<commit>`
+6. Revert deployment to use Docker Hub
+7. Push to declarative-config
+
+### Path B: Use Forgejo Registry
+1. **Fix Forgejo registry** (currently returning 503)
+2. **Create forgejo-container-registry secret** on apexalgo-iad
+3. Trigger build via `acb-build-images` workflow (requires iad-ci access)
+4. ArgoCD will sync and deploy
+
+### Path C: Manual Docker Build (NOT RECOMMENDED)
+1. **Fix Docker daemon permissions**
+2. **Provide Docker Hub credentials** for ronaldraygun account
+3. Build and push manually:
+   ```bash
+   docker build -t ronaldraygun/acb-enrichment:sha-af188b5 -f cmd/acb-enrichment/Dockerfile .
+   docker push ronaldraygun/acb-enrichment:sha-af188b5
+   ```
+4. Update deployment with real SHA
+5. Push to declarative-config
+
+## Why This Task Cannot Be Completed Currently
+
+1. **No build infrastructure access** - iad-ci kubeconfig is the only way to trigger CI builds
+2. **No working registry** - Forgejo is down, Docker Hub image doesn't exist
+3. **No local build capability** - Docker daemon not accessible
+4. **No credentials** - No Docker Hub credentials available
+
+## Files That Would Need Updates Once Build Completes
+
+1. `/home/coding/declarative-config/k8s/apexalgo-iad/ai-code-battle/acb-enrichment-deployment.yml`
+   - Option A: Revert to Docker Hub with real SHA
+   - Option B: Keep Forgejo registry (once it's fixed)
+
+## Workflow Templates Available (on iad-ci)
+
+1. `acb-enrichment-build` - Builds enrichment to Docker Hub
+2. `acb-build-images` - Builds all ACB images to Forgejo registry
+
+Both workflows exist but cannot be triggered without iad-ci access.
+
+## Conclusion
+
+This task requires **iad-ci kubeconfig** to proceed. The workflow templates are configured and ready, but there's no way to trigger them without cluster access.
+
+The Forgejo registry approach (commit f57e058) was a good attempt to work around the missing Docker Hub image, but:
+1. The registry is down
+2. The required secret doesn't exist
+3. We still need a way to build the image
+
+**Next Action Required**: Obtain iad-ci kubeconfig from Rackspace Spot UI and save to `/home/coding/.kube/iad-ci.kubeconfig`