VSKI v0.8.0

vcli: the vski CLI ships as a release asset

The vski-cli repo (submodule of platform since this release) builds vcli and attaches it to every release from now on:

curl -fsSL https://vski.sh/x/platform/releases/download/latest/vcli -o vcli
chmod +x vcli

Two halves:

Model packs (info / verify / inspect / import, the pkg/pack + pkg/npy Go libraries) - unchanged tooling for the vski.model/2 opaque pack format.
VSKI LAB management (new): vcli lab init scaffolds a self-hosted lab - it downloads the lab compose from the app deploy (keeping the stack definition fresh independently of vcli releases), resolves the api/jupyter base images to exact registry digests, and renders the lab layout:
```
data/     the platform's own data (multi-tenant SQLite)
projects/ project data - the api's bind
docker/   api + jupyter image shims (FROM the registry images) -
          the place to add local dependencies (GPU/rocm userland, …)
.env      user-editable environment
```
Because the api/jupyter images BUILD from the local shims, a lab can grow its own dependencies without forking the stack; host-side additions (device passthrough) go in a docker-compose.override.yml.

Also: vcli lab update (refresh compose + pins, fill missing .env keys, never touching your edited shims), vcli lab up|down|status, and vcli lab migrate (split a pre-vcli cache/data lab into data/ + projects/, dry run by default).

The release pipeline (release.ts) initializes the submodule, stamps the version in (vcli version), and uploads the binary alongside vski and vski-standalone.

Compatibility

No engine, API or storage changes - v0.8.0 adds the vski-cli submodule and the release-asset pipeline. Existing standalone binaries and images are unaffected. The latest/vcli download URL goes live with this release; the lab compose itself is served by the app deploy (/docker-compose.lab.yml).