Summary
- remove the
build.binaryfield fromcaution.hclparsing so new configs reject it instead of driving binary-only EIF builds - stop translating legacy
binary:Procfile entries intocaution.hcland update templates/fixtures to rely on Containerfile/Dockerfile packaging - remove the remote builder
binary_pathrequest surface so hosted builds always emit full-image manifests without abinaryentry
Closes #330
Test plan
cargo test -p caution-configcargo test -p cli migrate_procfilecargo test -p api buildercargo check -p caution-config -p api -p cligit diff --check
Notes:
- The legacy
EnclaveManifest.binaryreader/build-helper path is intentionally left in place for previously produced manifests, but no currentcaution.hcl, Procfile migration, CLI local build path, or API remote build request can setbuild.binary/binary_pathfor new deployments.
## Summary
- remove the `build.binary` field from `caution.hcl` parsing so new configs reject it instead of driving binary-only EIF builds
- stop translating legacy `binary:` Procfile entries into `caution.hcl` and update templates/fixtures to rely on Containerfile/Dockerfile packaging
- remove the remote builder `binary_path` request surface so hosted builds always emit full-image manifests without a `binary` entry
Closes #330
## Test plan
- `cargo test -p caution-config`
- `cargo test -p cli migrate_procfile`
- `cargo test -p api builder`
- `cargo check -p caution-config -p api -p cli`
- `git diff --check`
Notes:
- The legacy `EnclaveManifest.binary` reader/build-helper path is intentionally left in place for previously produced manifests, but no current `caution.hcl`, Procfile migration, CLI local build path, or API remote build request can set `build.binary`/`binary_path` for new deployments.