fix(cli): drop the dead yaml runtime dependency

`yaml` was added to cli's `dependencies` by the capability-ledger commit, when a
requirement was a YAML side file the CLI parsed itself. That design was replaced
two commits later: requirements became registered metamodel vocabulary, and
`src/lib/capability-ledger.ts` -- the only file that imported `yaml` -- was
deleted with it. The dependency was not.

Nothing in the package imports the module today (exhaustive grep over src and
test; the remaining hits are filenames like `pnpm-lock.yaml` and `meta.*.yaml`).
YAML parsing for metadata belongs to `@metaobjectsdev/metadata`, which declares
its own `yaml` and is where the loader's position-walker lives.

Caught pre-publish: the only surviving reference was an ORPHANED
`dist/src/lib/capability-ledger.js` left behind by `tsc` after the source was
deleted -- the stale-`dist` trap docs/RELEASING.md warns about, which a clean
rebuild clears. Left in place, 0.22.0 would have shipped an unused package to
every `npm i @metaobjectsdev/cli`.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: dmealing

server/typescript/packages/cli/package.json

@@ -59,8 +59,7 @@
     "@metaobjectsdev/runtime-ts": "workspace:*",
     "@metaobjectsdev/sdk": "workspace:*",
     "@toon-format/toon": "^2.3.0",
-    "jiti": "^2.4.0",
-    "yaml": "^2.9.0"
+    "jiti": "^2.4.0"
   },
   "peerDependencies": {
     "kysely": ">=0.27.0 <0.30.0",