Print the engine commit in --version #266

Closed
opened 2026-07-13 18:06:14 +02:00 by claude · 0 comments
Collaborator

aura --version prints aura 0.1.0 only, while run manifests stamp the engine commit. A stale binary is therefore invisible until after a run. Observed failure mode: a 9-day-old release binary at a pre-data-only-support commit failed aura run inside a data-only project with a raw cargo metadata failed: could not find Cargo.toml error, while HEAD had long supported data-only projects — nothing at the CLI surface distinguished the stale binary from an engine bug.

Research docs pin engine commits (Engine: aura @ <sha>); aura --version printing aura 0.1.0 (<commit>) gives those docs, and any agent, a pre-run freshness probe. The raw cargo error text in that failure mode is a small adjacent UX gap.

`aura --version` prints `aura 0.1.0` only, while run manifests stamp the engine commit. A stale binary is therefore invisible until after a run. Observed failure mode: a 9-day-old release binary at a pre-data-only-support commit failed `aura run` inside a data-only project with a raw `cargo metadata failed: could not find Cargo.toml` error, while HEAD had long supported data-only projects — nothing at the CLI surface distinguished the stale binary from an engine bug. Research docs pin engine commits (`Engine: aura @ <sha>`); `aura --version` printing `aura 0.1.0 (<commit>)` gives those docs, and any agent, a pre-run freshness probe. The raw cargo error text in that failure mode is a small adjacent UX gap.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#266