Step 2 · Operations evidence · Operations evidence · Upgrade 7.2.70 and image patch PT-BREN
CLIProxyAPI 7.2.70 · kimi-k3 · Visual course

Upgrade 7.2.70 and image patch

An upgrade is safe only when it preserves the image-failure behavior users observe.

Read first (primary source)
CONFIG-MODEL-POLICY-EVIDENCE.md

A redacted local record for the running gateway and the kimi-k3 example.

Read the simple version or open technical detail in any section.
1

Big idea


An upgrade is safe only when it preserves the image-failure behavior users observe.

Think of it as… Think of replacing an engine without losing the brakes: the version changes, but the car must still stop predictably. A binary is not a car; the proof is an observable HTTP response..

Under the hood

The exact base is v7.2.70; the local patch adapts image read failures into status and JSON body. The controlled test returned HTTP 503 when the upstream closed before headers.

2

In one picture


01 · backup manifestbackup manifestgovernsexact v7.2.70 baseThe final binary is 7.2.70-local.
backup manifest — governs — The final binary is 7.2.70-local.
3

In the code


This is the real local path and a safe read-only command.

internal/runtime/executor/codex_openai_images.go
# trecho real, não editado
ruby installed-binary-http-proof/run-proof.rb
go test -v -count=1 -run "^TestCodexExecutorDirectOpenAIImage" ./internal/runtime/executor

Open it yourself

ruby installed-binary-http-proof/run-proof.rb go test -v -count=1 -run "^TestCodexExecutorDirectOpenAIImage" ./internal/runtime/executor

4

Try it


Use the controls to retrieve the evidence before reading the explanation.

02 · exact v7.2.70 baseexact v7.2.70 basematchesnarrow source diffClosing before headers produced JSON 503.
exact v7.2.70 base — matches — Closing before headers produced JSON 503.
03 · narrow source diffnarrow source diffroutes toimage request readThe isolated proof did not restart the main service.
narrow source diff — routes to — The isolated proof did not restart the main service.
04 · image request readimage request readexcludesupstream close eventThe final binary is 7.2.70-local.
image request read — excludes — The final binary is 7.2.70-local.
05 · upstream close eventupstream close eventprovesstatus 503 mappingClosing before headers produced JSON 503.
upstream close event — proves — Closing before headers produced JSON 503.
06 · status 503 mappingstatus 503 mappingboundsJSON error bodyThe isolated proof did not restart the main service.
status 503 mapping — bounds — The isolated proof did not restart the main service.
07 · JSON error bodyJSON error bodymaps tofocused Go testThe final binary is 7.2.70-local.
JSON error body — maps to — The final binary is 7.2.70-local.
08 · focused Go testfocused Go testrestarts asinstalled binary SHAClosing before headers produced JSON 503.
focused Go test — restarts as — Closing before headers produced JSON 503.
09 · installed binary SHAinstalled binary SHApreservestemporary proxy portThe isolated proof did not restart the main service.
installed binary SHA — preserves — The isolated proof did not restart the main service.
10 · temporary proxy porttemporary proxy portcompares withfake upstream portThe final binary is 7.2.70-local.
temporary proxy port — compares with — The final binary is 7.2.70-local.
11 · fake upstream portfake upstream portreturnsPID cleanupClosing before headers produced JSON 503.
fake upstream port — returns — Closing before headers produced JSON 503.
12 · PID cleanupPID cleanupconfirmsmain service healthThe isolated proof did not restart the main service.
PID cleanup — confirms — The isolated proof did not restart the main service.
13 · main service healthmain service healthqualifiesbackup manifest verification recordThe final binary is 7.2.70-local.
main service health — qualifies — The final binary is 7.2.70-local.
14 · backup manifest verification recordbackup manifest verification recordrecordsbackup manifestClosing before headers produced JSON 503.
backup manifest verification record — records — Closing before headers produced JSON 503.

Three-frame summary

1 Preserve the rollback artifact
2 Port only the image error behavior
3 Exercise the installed binary
The exact base is v7.2.70; the local patch adapts image read failures into status and JSON body. The controlled test returned HTTP 503 when the upstream closed before headers.
Record the observation, preserve the exception, and choose the next narrow proof.
retrieveVerifiable backupclick to flip
The final binary is 7.2.70-local.
retrieveFocused patch testclick to flip
Closing before headers produced JSON 503.
retrieveIsolated HTTP proofclick to flip
The isolated proof did not restart the main service.
Predict before revealing

What proves the image patch survived upgrade?

The isolated HTTP result exercises the installed binary and observes the consumer-visible JSON contract.

Worked example
1Read the backup manifest and binary hash.
2Run the focused image executor test on v7.2.70.
3Run the isolated close-before-headers HTTP proof.
Retrieval review
What proves the image patch survived upgrade?

The isolated HTTP result exercises the installed binary and observes the consumer-visible JSON contract.

Ask which boundary you would prove next; the next lesson narrows a different operational risk.