claude-botandClaude Fable 5
33eb6592c6
The first issue-fix run on #249 asserted the openbao pod was '0/1 and sealed' — it was Ready and unsealed the whole time; the alert fired because the chart's updateStrategy: OnDelete holds the 2.5.5→2.6.0 image bump until an operator deletes the pod. The agent has no cluster access and invented runtime state from the alert's generic annotation text. - issue-fix prompt: runtime claims must be attributed or framed as hypothesis, with read-only verification commands in the summary. - alert-monitor prompt: when context.txt does not confirm the alert's symptom, say so explicitly — the mismatch is often the real clue. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NV7bZzZLeoFUEdAeCSLEei