Redacted excerpt; full evidence withheld.

$ cd <guest-path> && pwd && ls -la && id -u && (git status 2>&1 | head -3) && cat README.md 2>/dev/null | head -200
exit: 0
et the song, add or remove a video, find where each fits (`align`) or place one by hand (`set_offset`), score, cut (`propose_edit`), keep and change named edits cut by cut (`save_edit`, `set_cut`, `split_cut`, `merge_cut`, `replace_edit`), trim an edit to part of the song (`set_span`), render — is a plain function in `muvid.footage.service`, listed once in its `FOOTAGE_OP_SPECS` and registered with nw as `nw.GenreOp`s, so a host serves them without importing muvid's internals. `muvid.mcp.footage_tools` and `muvid.mcp.scoring_tools` expose the same operations as MCP tools (`set_song`, `add_footage`, `align_footage`, `propose_edit`, `assemble_music_video`, `footage_set_cut`, `footage_render`, …) over a stateful per-user workspace under `~/.local/share/muvid` (`MUVID_DATA_HOME` to relocate). A host that serves the project itself (the reelee studio) creates it where it wants with `projects_dir` — a `muvid.Project`, an `nw.Project` whose media is registered in the host's artifact catalog — and `python -m muvid.importing MANIFEST PROJECTS_DIR` brings a finished prod
[excerpt truncated]