Reproduced the Digesta "engine#0 crash-loops despite backend.type=cpu and
engine_specs" report on the published 0.2.83 image, GPU-less, with their
config — and it is not the front failing to propagate the engine spec.

coderai-entrypoint creates $CODERAI_CONFIG_DIR/coderai and symlinks
~/.coderai to it (lines 49, 70); the app resolves config from the HOME-style
path. A config.json written at $CODERAI_CONFIG_DIR is therefore never read.
On first start the app writes a DEFAULT coderai/config.json — backend null,
engine_specs null, engines null — reads that, and the engine auto-detects,
finds no GPU and aborts. Which is exactly the "backend: null" they saw and
read as the front regenerating the config.

Documents the live path, the one-liner to check which file is in use, and
that mounting straight at /config/coderai sidesteps it.

Also ships coderai-upgrade in Dockerfile.oci-venv. It was only in
Dockerfile.oci, so every image we actually publish (venv-built) failed
`coderai-docker --upgrade` with "stat /usr/local/bin/coderai-upgrade: no
such file or directory".
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>