feat(dev-safety): Phase 1 of #185 — audit tool for ambiguous muse binaries
Adds scripts/dev/which_muse.py + which-muse.sh: classifies any muse-like executable as editable (live source) vs installed, via muse.__file__ inspection through the shim's own interpreter (handles both literal and `env`-indirect shebangs; fails clearly on non-Python dispatcher shims like pyenv's).
Audit found 5 distinct muse resolutions on this machine across 3 versions, confirming and exceeding the ambiguity #185 was filed to fix — including the interactive shell's `which muse` disagreeing with this very tool's own `shutil.which` result. Documented in docs/local-dev-safety.md along with a real cwd-shadowing bug the test suite caught in the classifier itself (subprocess inherited caller's cwd, whose own muse/ subpackage shadowed PYTHONPATH — fixed by pinning cwd to a neutral tempdir).
Observation-only: no PATH changes, no new binaries, no guard rails yet.
Semantic Changes
40 symbols
Files Changed
+1160
1160 in snapshot
0 comments
muse hub commit comment sha256:133f9bcf57a62ec7ebf0cd71138b54a200b15989aea2fb2a6912497e2926aa8a --body "your comment"
No comments yet. Be the first to start the discussion.