create --type change
`spt shell cmd <instance> <unknown-op>` names the cmd capability set as THE shell's vocabulary, hiding every send-payload verb
Measured 2026-09-08 (flynn, confirmed by doyle walking into it the same morning): `spt shell cmd alchemy-1 create` answers `unknown op create — the shell's vocabulary is [bags, bind-repo, …]`. That sentence is true of the `[shell.capabilities]` cmd set and false of the shell: alchemy's `create` and `comment` are SEND-payload verbs (line-1 verb over `spt shell send`, CONTEXT.md Agent surface), deliberately outside `[shell.capabilities]` because they carry free text and an optional --file. An agent reading the refusal concludes the verb does not exist and routes around the shell (doyle filed releases#287 via bare `gh issue create` + a `type` fill for exactly this reason).

Ask: the unknown-op refusal should say what it enumerates ("the cmd capability set is [...]") and point at the shell's other surfaces ("send-payload verbs and drive types are not listed here; see `spt shell cmd <instance> help` / the adapter's manifest"), or list the manifest's send verbs when the adapter declares them. Small wording change, discoverability only; no behaviour change.

Origin: spt-progress-tool v0.25.0 fixes its own hint half (names create's send form); this is the core half.