reproduce-skill-envlisted

# Reproduce a skill environment with qvr qvr separates *intent* from *bytes*: `qvr.lock` pins each skill to a `commit` and a `subtreeHash`, so the exact content can be restored even if upstream refs move. On top of that, `qvr export` emits a small, human-readable manifest that a teammate (or a CI job) can `qvr import` to rebuild the same set from scratch — without any pre-existing registry configuration. This skill covers sharing a set, pinning it hard, and asserting reproducibility in CI. ## When to use this - The user wants to share their skill set with a teammate or another machine. - They want byte-for-byte reproducibility (pin to exact commits, not floating refs). - They want CI to **fail** if the checked-out skills don't match the lockfile. For first-time discovery/install of individual skills, use `onboard-skills` instead. ## Key concepts - **Manifest (export)** — a 3-column text file: repo URL, skill name, version. Portable and reviewable. By default it records the ref; `--frozen` records the exact pinned commit. - **Lockfile (`qvr.lock`)** — the authoritative TOML v5 record with commit + subtreeHash. Commit it to version control. - **`mode: edit` / `mode: link` skills** live in the project filesystem and are not portable across projects; they're skipped from exports by default. ## Workflow ### 1. Export the current set ``` qvr export > skills.txt # ref-only (floating) qvr export --frozen > skills.lock.txt # pin t