compiler: restore ability to compile from IR (#48)

* compiler: restore ability to compile from IR

This feature was lost in a rebase of 5b1569e

* compiler: properly handle direct model relative paths

* compiler: reject invalid IR as compile input

* cli: reject scenario ir missing version

Author: nhynes

Cargo.lock

@@ -163,7 +163,8 @@ amber compile path/to/root.json5 --output /tmp/scenario.json
 ```
 
 You can also use an existing Scenario IR as input for `amber compile` to produce other outputs
-(for example, Docker Compose or Kubernetes manifests).
+(for example, Docker Compose, Kubernetes, or direct/native runtime artifacts). Scenario IR input
+is graph-only, so `--bundle` still requires a manifest or bundle input with manifest source bytes.
 
 ### Check-only (linting + diagnostics)
 

README.md

@@ -14,6 +14,7 @@ amber-manifest = { workspace = true }
 amber-mesh = { workspace = true }
 amber-resolver = { workspace = true }
 amber-router = { workspace = true }
+amber-scenario = { workspace = true }
 amber-template = { workspace = true }
 base64 = { workspace = true }
 clap = { version = "4.5.46", features = ["derive"] }

cli/Cargo.toml

@@ -8,7 +8,9 @@ Command-line front-end for the compiler. It resolves a root manifest, runs compi
 - Keep `amber --help` and nested `--help` pages useful enough that users can discover the CLI
   surface without reading the source.
 - Write compile outputs only when requested; `amber compile` requires at least one output flag (`--output`, `--dot`, `--docker-compose`/`--compose`, `--metadata`, `--kubernetes`, `--direct`, or `--bundle`).
-- Detect bundle and Scenario IR inputs and emit bundle directories via `--bundle`.
+- Detect bundle and Scenario IR inputs for `amber compile`.
+- Emit bundle directories via `--bundle` when the input is a manifest or bundle; Scenario IR
+  inputs do not carry manifest source bytes, so `--bundle` is not available there.
 - Run compiled direct artifacts via `amber run <output-dir>` (delegates to the direct init runtime).
   - Direct mode requires a local sandbox backend: `bwrap` plus `slirp4netns` on Linux, or `/usr/bin/sandbox-exec` on macOS.
   - Direct mode only supports explicit `program.path` executables; it does not resolve bare program names through `PATH`.