The committed lock still had bread-theme / bread-utils / bread-launcher
resolved as *path* dependencies — an artifact of the local-only
.cargo/config.toml [patch] that redirects them to ../bread-ecosystem
while iterating. When the theme-spotlight PR bumped Cargo.toml to
`tag = "v0.7.5"` and added bread-launcher, the lock was never
regenerated on an unpatched checkout, so it stayed inconsistent with
the manifest.
CI clones this repo alone with no sibling bread-ecosystem, so
`cargo build --release --locked` there hit "cannot update the lock file
because --locked was passed" and the dev-release build failed (run
1187) — which is why the shell-theme-capable breadbar never reached the
dev track and every downstream (the BOS ISO included) still ships the
pre-theme 297207a build.
Regenerated on a clean clone; `cargo build/clippy/test --locked` all
pass against the v0.7.5 tags. Transitive gtk-rs/etc. entries move to
latest-compatible patch versions as a side effect.
