claude-botandClaude Opus 5
b1f5d6dcbc
Review noted this file pins ci-k8s at a newer dated tag than e2e.yml, e2e-test.yml, alert-monitor.yml and issue-fix.yml, and asked for either a stated reason or a follow-up so it does not read as an oversight. There is no reason — the other four are stale. Per the latest-stable rule all five should sit on the newest dated tag. Not bumped here on purpose. Those four pipelines exercise different tooling in the image and three are cron- or event-triggered, so none of them run on this PR. Bumping them in this branch would ship four untested changes under cover of a green run that never touched them — the same shape as the digest decay in #458, where breakage sat unnoticed precisely because the affected jobs did not run for months. Each wants its own verification, so it is tracked as #461 rather than smuggled in here. Comment added above kustomize-build so the split is explained where a reader meets it, pointing at the issue rather than restating the whole argument. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>