gate: clause 3 holds on b11081 by a direct direct-io A/B; the compose .env names 0.34.4

[glennneuber]

This updates the 0.34.4 promotion record in docs/maxusai/amd-upgrade-gate.md (#391) in two places.

Clause 3 (--direct-io) is now validated directly on b11081. The record said (b), and (c) only by transitivity, because the payload moved and no direct A/B had run. The maintainer asked for one. It is the same check the 0.34.2 promotion ran on b10969 on 2026-09-21:

• the vision suite, think off, on qwen3.6 and gemma4:31b, with a cold server per model;
• the promoted image, in production's environment: f16, flash attention on, two slots, two-pass;
• 0/54 blocks differ between direct-io on and off, with every scored cell equal (0 of 978 and 0 of 986);
• both arms verified at the runner flag line: on passed --load-mode dio on both runner starts, and off (OLLAMA_IGPU_DIRECT_IO=0) passed it on neither;
• all 108 blocks finished with valid JSON.

The script's output is pasted verbatim under the clause table.

The compose .env line. The decision said the .env still named 0.32.1, and warned against a compose redeploy. The .env names the 0.34.4 image since MaxusAI/ollama-deployments 55e2fa2. docker compose config matches production, except for three things:

• label=disable, which has no effect on this host;
• an added healthcheck;
• a compose network in place of the default bridge.

Verification

• check_source_paths.py --changed-since origin/main is clean.
• The name scan of the diff finds nothing.

amd-server/rocm-gfx1151

🤖 Generated with Claude Code