chore(pm-agent): pin agent-runner to the run-394 digest (466f63e, PR #99), bump config-generation #100

Merged
jakman85 merged 1 commits from chore/pm-agent-digest-99 into main 2026-10-31 17:23:19 +00:00
Owner

Pins the pm-agent dispatcher and worker to the agent-runner image that CI built from PR #99's merge commit (466f63e). That build includes the CLI failure envelope in triage errors and the PM_DECISION_MAX_TURNS knob.

  • platform/pm-agent/deployment.yaml: dispatcher image: changes from sha256:df36d9b7… to sha256:14a42ba8281ecd98005f5d99ecda4fb729104c783b01584097c32e104ced1bb2. config-generation goes from "4" to "5".
  • platform/pm-agent/configmap.yaml: PM_WORKER_IMAGE gets the same digest, plus one provenance comment.
  • No other values change. PM_DRY_RUN stays "false". No *.sops.yaml files are touched.

Provenance. This digest is the publish from images run 394 (task 643, push, success) on 466f63ec3c3d. I read it with a registry manifest HEAD (OCI and Docker Accept headers). agent-runner:sha-466f63ec3c3d and agent-runner:main both return docker-content-digest: sha256:14a42ba8…1bb2.

Toolbox gate, run from the worktree with all three workarounds: rc 3, UNDETERMINED. The only stage that did not run is gitea-settings, because there is no SETTINGS_API_TOKEN locally. spec-immutability passed. L0 had 25 cases and L1 had 3, with 0 failures and 0 skips. This is not a green result.

Approval policy: platform/pm-agent/*.yaml should not be a sensitive path. CI's approval-policy stage is the authority on that.

Handoff: decisions/2026-10-31-pm-agent-digest-99.md.

🤖 Generated with Claude Code

Pins the pm-agent dispatcher and worker to the `agent-runner` image that CI built from PR #99's merge commit (`466f63e`). That build includes the CLI failure envelope in triage errors and the `PM_DECISION_MAX_TURNS` knob. - `platform/pm-agent/deployment.yaml`: dispatcher `image:` changes from `sha256:df36d9b7…` to `sha256:14a42ba8281ecd98005f5d99ecda4fb729104c783b01584097c32e104ced1bb2`. `config-generation` goes from "4" to "5". - `platform/pm-agent/configmap.yaml`: `PM_WORKER_IMAGE` gets the same digest, plus one provenance comment. - No other values change. `PM_DRY_RUN` stays "false". No `*.sops.yaml` files are touched. **Provenance.** This digest is the publish from `images` run 394 (task 643, push, success) on `466f63ec3c3d`. I read it with a registry manifest HEAD (OCI and Docker Accept headers). `agent-runner:sha-466f63ec3c3d` and `agent-runner:main` both return `docker-content-digest: sha256:14a42ba8…1bb2`. **Toolbox gate, run from the worktree with all three workarounds:** rc **3**, UNDETERMINED. The only stage that did not run is `gitea-settings`, because there is no `SETTINGS_API_TOKEN` locally. `spec-immutability` passed. L0 had 25 cases and L1 had 3, with 0 failures and 0 skips. This is not a green result. **Approval policy:** `platform/pm-agent/*.yaml` should not be a sensitive path. CI's approval-policy stage is the authority on that. Handoff: `decisions/2026-10-31-pm-agent-digest-99.md`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
gitea-admin added 1 commit 2026-10-31 17:20:19 +00:00
chore(pm-agent): pin agent-runner to the run-394 digest (466f63e, PR #99), bump config-generation
gate / gate (pull_request) Successful in 2m57s
gate / conformance (pull_request) Has been skipped
19097e4d4f
Dispatcher image and PM_WORKER_IMAGE both move to
sha256:14a42ba8281ecd98005f5d99ecda4fb729104c783b01584097c32e104ced1bb2, the digest the
registry returns for agent-runner:sha-466f63ec3c3d and :main. config-generation 4 -> 5.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
jakman85 approved these changes 2026-10-31 17:20:51 +00:00
jakman85 scheduled this pull request to auto merge when all checks succeed 2026-10-31 17:20:57 +00:00
jakman85 merged commit a1d89f4a5f into main 2026-10-31 17:23:19 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Home-Network/home-network-k3s-impl#100