Repository navigation
Description
🤖 Generated by the Agentic Engineer
Part of devantler-tech/monorepo#4868. Found by the kagent lane's 2026-11-14 scheduled run.
Problem
The kagent lane's Harness (k8s/providers/hetzner/apps/agentic-engineer/harness.yaml) pins its image by digest, and its comment says to "move this pin after each publish". Nothing does that. Renovate moves the agent-plugins commit in scripts/kagent-claude-harness/Dockerfile (#6198, #6247, #6249), and main publishes a new image each time. The Harness pin has not moved since #6181 (2026-11-13 06:47Z). It still names the image published at 2026-11-13 03:54Z.
So the lane runs a plugin older than the reviewed one. On 2026-11-14 the lane ran plugin-definition-currency.sh --runtime claude --installed /opt/agent-plugins/agentic-engineering. It reported DRIFT, 8 findings, against the monorepo's gitlink a5a0d77: the agentic-engineer and portfolio-surveyor agents, three portfolio-maintenance files, two Stripe skills and one missing skill. The run followed the reviewed files fetched from the gitlink, but the lane's own role is meant to load current (devantler-tech/monorepo#4868, second criterion). Every plugin bump repeats this.
Options
- The publish job opens the pin PR. After it signs and verifies the digest,
publish-kagent-claude-harness.yamlopens a pull request that moves the Harness pin to that digest. The digest is the one the job just verified, so the PR moves exactly that image. It adds a write step, withcontentsandpull-requestspermissions, to a job that publishes today. - Renovate tracks the pin. Write the Harness image as
<image>:<tag>@sha256:<digest>, and let a Renovate rule follow the newest1.0.0-<sha>tag. The tag carries a commit SHA, so ordering by version does not work. Renovate would need a rule that orders by publish date, and that may not exist. - Keep it manual. Each plugin bump PR also moves the Harness pin in a follow-up. This needs no new machinery, but it relies on someone remembering, which is the failure seen here.
Option 1 looks simplest, because the job already holds the verified digest.
Done when
- One option is chosen, and the Harness pin follows each published image without a manual step.
- A kagent run after the next plugin bump reports CURRENT, or only the gap between the image's and the monorepo's agent-plugins commits.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Effort
Projects
- StatusShow more project fields📥 Backlog
Activity
fix(agentic-engineer): run the kagent lane on the harness image with …