v0.6.1

Demo mode isolation fix

v0.6.0 said --demo touched nothing. That was not true.

• It read your real favorites file, so actual pipeline names appeared in a mode meant for screenshots and screen sharing. Demo mode now seeds fictional favorites and never reads that file.
• It could write to your real config directory. Pressing f overwrote favorites.json with demo names, a dashboard refresh overwrote the cache, and completing the A or @ forms rewrote config.toml. All four writes are suppressed in demo mode.

A regression test asserts every demo favorite is one of the fixture pipelines, so a real name reappearing fails the build.

If you ran --demo on v0.6.0 and pressed f, check your favorites: cat ~/.config/lazygocd/favorites.json.

brew upgrade lazygocd
cargo install lazygocd

Full Changelog: v0.6.0...v0.6.1