---
description: Build + pack + deploy a federated module to the bonded fiddle (npm run ship under the hood)
argument-hint: [<name> ...] [--kind jar|ext]
---

Invoke the `ship-workflow` skill (at `admin-kit/.claude/skills/ship-workflow/SKILL.md`) and follow its behavior contract.

Parse arguments after `/ship`:
- If one or more `<name>` positionals given → ship those specific projects in topo order: `npx ws-modules --build --pack --deploy <name> [<name> ...]`
- If none given → ask the user which project(s) to ship before running (mass-ship is rare and usually wasteful).
- Pass through `--kind jar` or `--kind ext` if given.

Pre-check:
- Workspace is bonded: `wsconfig.json` exists with a `wpmRoot`. If not, abort and suggest `/wire-host <fiddle>`.
- cwd is workspace root (`angular.json` present).

After the bin completes, surface deploy paths from its summary so the user can verify the artifacts landed where expected.

If the lib build fails with `Cannot find module '<dep>'`, suggest `npx ws-sync-paths` then retry — covered in `federation-error-catalogue` entry #2.