Nightly 2 — branch/merge fixes, mist read path fix, log --branch flag

Muse v0.2.0-nightly.2

Second nightly build. Three real fixes landed in muse, and musehub is version-synced alongside it — both now at v0.2.0-nightly.2.

What changed

• muse branch --merged/--no-merged now accept a sha256:-prefixed commit ID, not just a branch name — previously crashed with a confusing "forbidden characters" error.
• muse mist read owner/ID now hits the correct API path. It was silently misrouting to a nonexistent endpoint and reporting a bogus "invalid JSON" error instead of the real 404.
• muse log --branch/-b is now a real flag, not just an implicit positional argument — composable with --oneline, --max-count, --json, etc., with zero working-tree or HEAD side effects.

How the version number got picked

Every commit above carries a sem_ver_bump computed automatically from a structural diff of the changed public symbols — not a changelog someone typed by hand. muse release suggest walked the commit graph since the last nightly, found three patch-level structural changes, and cited the exact commits and symbols responsible. The version number came with a citation, not a vibe.

Install

curl -fsSL https://staging.musehub.ai/install.sh | sh
muse --version
# → muse 0.2.0.dev2

Muse is domain-agnostic version control — the same commit DAG, merge engine, and object store versioning code today extend to music, 3D scenes, datasets, biological pathways, and knowledge graphs without changing the core.