> Part of the **Plugin & Package System** epic #20. Phase 4 (MVP — pairs with #D). Relates to #15 (CLI: more commands). ## Goal Add a `package` subcommand to `turian-cli` for managing project packages: `install`, `remove`, `update`, `list`, `info`, and (stub/forward-looking) `search`. Installation orchestrates `zig fetch --save` for source/native packages and manifest/vendor writes for asset-only packages, then updates the project so the next build picks the package up automatically. ## Context / integration points - `editor/Cli.zig` (862 lines) dispatches subcommands by string match (`new-project`, `info`, `import`, `build`, `play-build`, `debug`, `mcp`, `docs`). The `debug`/`mcp`/`docs` commands show the nested-subcommand pattern to mirror. - Project deps live in `build.zig.zon` after #B. Source/native packages are added via `zig fetch --save <url>` (Zig computes the hash/lockfile). Asset-only packages (no `build.zig.zon`) install into the project's vendored packages location decided in #C. - `editor/PackageManager.zig` (#C) provides discovery/list/info data; this issue is the CLI surface over it plus the install/remove *mutations*. ## Design `turian-cli package <sub> [args]`: - `install <source>` — `<source>` = a git URL, a registry name (future #J), or a local path. For code packages: run `zig fetch --save[=name] <url>` then record the package in the project manifest/index; for asset-only: fetch/copy into the vendored packages dir + register. Validate the fetched package has a `turian-package.json` (via #C) and is `engine_compat`. - `remove <name>` — remove from `build.zig.zon` `.dependencies` (and/or vendored dir) + project index. - `update [<name>]` — re-fetch to the latest allowed version (delegates to `zig fetch`); `--all` updates every package. - `list` — installed packages (name, version, type) from #C discovery. - `info <name>` — full manifest metadata + dependency edges. - `search <query>` — **stub** returning "registry not yet available" pointing at #J; wire real behavior when the registry lands. Use the existing `GameBuild.spawnAndWaitIn` helper to invoke `zig fetch`. Emit clear, parseable output (consistent with the existing CLI style). Honor a `--project <path>` arg like other commands. ## Tasks - [ ] `cmdPackage` dispatcher in `editor/Cli.zig` mirroring `cmdDebug`/`cmdDocs` nesting - [ ] `install` — orchestrate `zig fetch --save` (code) / vendored copy (assets) + validate via #C + record in project - [ ] `remove` — undo install (manifest + vendored dir + index) - [ ] `update [name] [--all]` — delegate to `zig fetch` - [ ] `list` / `info` over #C discovery data - [ ] `search` stub → forward-reference #J - [ ] Update `printUsage()` help text - [ ] Tests / a scripted end-to-end: install the #A example package into `examples/basic-project`, `list`, `build`, confirm package assets in `game.oap` (closes the loop with #D) - [ ] `zig fmt`; docs (CLI reference) per the standing docs-site rule ## Acceptance criteria - `turian-cli package install <local-or-git>` adds a package so that the next `turian-cli build` includes it with no manual file copying. - `remove`, `list`, `info`, `update` work and round-trip cleanly (install → list → remove → list). - `search` returns a clear "not yet available" pointing to the registry work (#J). - An end-to-end script installs an asset package and builds a project that uses it. ## Dependencies Depends on #C (discovery) and #B (project `build.zig.zon`). Pairs with #D for the headline MVP loop. ## Out of scope Publishing packages and a real registry/search backend (#J). Editor UI (#H).