- Verified acb-enrichment source and Dockerfile are correct
- Confirmed WorkflowTemplate acb-images-build includes enrichment build
- Verified deployment manifest in declarative-config has placeholder SHA
- Confirmed iad-ci proxy exists at http://traefik-iad-ci.tail1b1987.ts.net:8001 but is read-only
- Blocker: iad-ci.kubeconfig missing at /home/coding/.kube/iad-ci.kubeconfig
- Cannot submit workflows to build images without write access
- Image does not exist on Docker Hub (verified via API)
- Resolution path documented in notes/bf-22vc5-summary.md
- Database cluster cnpg-apexalgo has 0/3 instances ready
- cnpg-apexalgo-3 pod stuck Pending for 23 days (Insufficient cpu)
- Schema-init pod Running but cannot connect to database
- All ai-code-battle workloads Pending due to missing DB
Migration code is complete and deployed (commit 1ec0c25).
Verification awaits cluster CPU resolution.
- Verified combat_turns migration already in schema (line 46, 305)
- Rollout annotation bumped to v11
- declarative-config up to date with origin
- Blocked on infrastructure: postgres cluster broken (23 days), cluster at CPU capacity
- Cannot verify index-builder until pods can schedule
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- combat_turns migration already present in declarative-config
- checksum already bumped to v10-combat-turns-force-apply-2026-06-03-bf-1bvca
- BLOCKED: apexalgo-iad cluster out of CPU
- cnpg-apexalgo-3 pod Pending 23+ days (Insufficient cpu)
- acb-postgres service has no endpoints
- index-builder also Pending (Insufficient cpu)
- Migration will auto-apply once postgres pod schedules
- combat_turns migration already in schema (line 305)
- Annotation bumped to v10, already pushed
- Cluster CPU exhaustion preventing all pods from scheduling
- PostgreSQL (CNPG) down - endpoints empty
- Schema-init running but cannot connect to DB
- Nothing more to do at code level - awaits cluster recovery
- combat_turns migration SQL was already present in schema
- Bumped rollout annotation from v7 to v10
- Pushed to declarative-config (commit 6d7439d)
- ArgoCD triggered rollout, but blocked on cluster CPU exhaustion
- Code changes complete; awaiting infrastructure resolution
- Migration SQL already present in schema-init (line 46, line 305)
- Bumped checksum annotation from v9 to v10 and pushed to declarative-config
- Cluster CPU constraint blocking all pods including PostgreSQL
- No CNPG cluster resource found - DB cannot start
- Schema-init cannot apply migrations without DB connection
- Index-builder cannot verify fix without DB
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
## Summary
The combat_turns column migration has been successfully deployed to declarative-config.
All code changes are complete, committed, and pushed.
## Status
- Migration SQL: ✅ Present in acb-schema-init.yml (line 305)
- Rollout annotation: ✅ Bumped to v7
- Pushed to declarative-config: ✅ (commit 503724e)
- Cluster verification: ⏸️ BLOCKED - apexalgo-iad has insufficient CPU
## Blocking Issue
All pods in ai-code-battle namespace are stuck in Pending state due to
'Insufficient cpu' error. Index-builder cannot schedule to verify the fix.
- Migration SQL already present in schema (line 305)
- Committed and pushed to declarative-config (503724e)
- Rollout annotation bumped to v7-combat-turns-migration-2026-06-03-m
- BLOCKED: apexalgo-iad cluster has insufficient CPU for pod scheduling
- Verification pending cluster resource availability
- combat_turns migration code is complete and deployed
- Rollout annotation bumped to v4-combat-turns-migration-2026-06-03-b
- apexalgo-iad cluster has insufficient CPU - pods stuck Pending
- Migration will apply once resources are available
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Schema migration already present in declarative-config (line 305)
- Rollout annotation bumped to v3-combat-turns-redeploy-2026-06-03
- All changes committed and pushed to origin/main
- Awaiting ArgoCD sync to apply migration to apexalgo-iad
P0 fix for acb-index-builder crash:
- Added ALTER TABLE matches ADD COLUMN combat_turns migration
- Pushed to declarative-config@845d59d
- ArgoCD will sync and restart schema-init Pod
The migration file migrations/0001_initial.sql was created in commit 31678be
and contains the complete schema matching cmd/acb-api/db.go.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Bead-Id: bf-67io
Verified that the mobile bottom tab bar specified in §16.4 is implemented
in web/index.html as inline styles, not in external CSS files.
The implementation matches specification:
- Four bottom tabs: Home, Watch, Compete, Board
- Persistent bottom tab bar on mobile (<640px)
- Proper z-index layering and responsive behavior
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The migration file migrations/0001_initial.sql was added in commit 31678be.
This bead was filed based on an outdated plan inventory.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Verified that migrations/0001_initial.sql contains all 20 tables from
cmd/acb-api/db.go schema. Work was completed prior to bead assignment.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Verified all required components are in place:
- CI workflow at starters/csharp/.github/workflows/build.yml (added in 7bf6566)
- Plan §5.8 coverage at line 986 (added in 55c594c)
- Directory listing at line 2565 (added in 9d4a311)
- Plan §11.2 template repos at line 2629 (added in 55c594c)
C# starter kit fully registered alongside 8 other language starter kits.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Re-verified that all required components are in place:
- CI workflow exists at starters/csharp/.github/workflows/build.yml
- Plan §5.8 includes acb-starter-csharp at line 986
- Plan §11.2 includes acb-starter-csharp at line 2629
- Directory listing includes csharp/ at line 2565
The task was originally completed in commits 55c594c and 9d4a311.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The POST /api/register endpoint sets status='active' for newly registered
bots, and the matchmaker queries for all active bots. Integration is complete;
no code changes required.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Verified that commit 7e8c9d7 completed all registration requirements:
- Added to §5.8 Starter Kit table
- Added to file structure section
- Added to published template repos table
- CI workflow already exists
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The bead task indicated missing CI workflow and plan §5.8 coverage,
but verification found all components already in place from commit 55c594c.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The JavaScript starter kit was officially registered via commit 7e8c9d7,
which added it to plan §5.8, the file structure section, and the published
template repos table. This notes file documents the completion status.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Verified complete implementation of §16.9 directed attack arrows feature:
- Engine emits combat_death events with killers array (bot_id, owner, position)
- TypeScript types properly define CombatDeathKiller and CombatDeathDetails
- Viewer draws solid arrows from each killer to victim with attacker player color
- Arrowheads point to victim tile center
- Backward compatibility maintained for old replays (proximity-inference fallback)
- Red explosion flash and X marker for death visualization
Related commits: 8e0aa5e (engine), 323c1e8 (viewer)
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The feature was already fully implemented in commits 8e0aa5e and 323c1e8.
This commit documents the verification of that implementation.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Investigated why all matches have enriched: false. Root cause is
corrupted R2 credentials in OpenBao that prevent the acb-enrichment
service from uploading AI commentary.
Key findings:
- R2 credentials at secret/rs-manager/ai-code-battle/r2 are corrupted
- endpoint/secret-key values are swapped
- Enrichment service cannot upload to R2
- Fix script exists but requires cluster access
Blocker: Expired kubeconfig (bf-5nap) prevents cluster access
and execution of the fix.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The bug fix was already applied in commit 9bcbd56. Updated notes to reflect:
- Fix is already in the codebase (using p.Won instead of p.BotID == m.WinnerID)
- Index builder will automatically regenerate static JSON on next 15m cycle
- No manual intervention required - production deployment will pick up the fix automatically
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
