I3245 — The image build's cold and warm durations and its context size are read from docker-image runs, and the deployment records say what is built today

○READY wave 0 · p3 · verification profile · parallel safe

Part of fly-deployment — The container image is a projection of the repository model, and its smoke is its evidence.

Objective

Record cold, warm and one-line-edit image build times and the build-context size from docker-image runs as evidence, and rewrite the stale current_state of I0911 and I0921.

Why

c228#9-#10 and c195#2 asked for multi-stage BuildKit caches with cold and warm times recorded. The stages exist; the numbers and the records do not. Sources: chatgpt-majordomus:c195#2, chatgpt-majordomus:c228#9, chatgpt-majordomus:c228#10.

Current state

I0911 says 'No container build exists'; docker-image.yml builds a multi-stage image with an sccache mount restored via actions/cache.

Desired state

I0911 and I0921 carry measured evidence and can move toward done.

Scope

• .ai/repo/project/issues/I0911.yaml
• .ai/repo/project/issues/I0921.yaml
• .github/workflows/docker-image.yml

Out of scope

• Remote BuildKit cache backends without a benchmark (c195#2 rejected cargo-chef or a prebuilt image without one)

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

• Three measured durations with run ids
• Context size measured from the build log

Validation

• majordomus plan validate

Evidence required

• image_build_times_recorded

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3245.yaml. Read it back with majordomus plan show I3245.