# Incident: debian1 seat image node drift (v22 vs v24)

Status: BLOCKED
Priority: 2
Source request: discovered 2026-08-11 while diagnosing land-queue gate failures
Task IDs: (assign)

## Outcome

`node-runtime.smoke.sh` green again: the agent-seat image on debian1 exposes
node v24.x. Until then the land queue's full gate fails for EVERY candidate
whenever a reachable builder is registered, since the remote suite runs and
fails closed on the drift.

## Evidence

`bash modules/buildbox/test/run-all.sh` (2026-08-11, twice, consistent):
`FAIL seat image exposes node 24 (want v24.x got v22.23.2)` — minimal PATH and
remote-runner PATH both correctly expose v24.18.0; only the seat image is
drifted. Registry: debian1 reachable (builder), debian2 unreachable, debian3
reachable.

## Constraints

- Seat/node image work is owned by the active k3s / node-image lane
  (`immutable-node-image`, `node-image-foundation`, k3s migration plans) — the
  drift may be that lane's in-flight WIP. Do NOT repair the image from another
  lane; hand this to the owning lane.
- Until fixed, landing uses the owner-authorized direct-land path with
  per-module verification (queue gate red for external cause).

## Next executable action

Owning lane confirms whether v22 on debian1's seat image is intended WIP;
either converge the image to v24 or update the smoke contract.
