Inline jsdoc

[nkaradzhov]

Description

Currently, JSDocs are not visible to end-users. This PR moves JSDocs to the export location so users can actually see them. It also adds a new mandatory step in CI -> all commands must have JSDocs defined.

• Move command JSDoc to command registry exports (packages/*/lib/commands/**/index.ts) and remove parseCommand JSDoc from command implementation files.
• Remove internal @param parser docs from user-facing registry JSDoc.
• Introduce a lightweight check script: npm run check:command-jsdoc.
• Add a required PR CI workflow (JSDoc Check) that runs the new check.
• Remove JSON_JSDOC_SYNC_PLAN.md.

BEFORE

AFTER

---

Checklist

• Does npm test pass with this change (including linting)?
• Is the new or changed code fully tested?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

---

Note

Low Risk
Mostly documentation-only refactors plus a new CI gate; runtime behavior should be unchanged, but PRs may start failing if any command registry export lacks an attached JSDoc block.

Overview
Moves user-facing JSDoc from individual command implementation files (e.g., parseCommand blocks) onto the exported command registry entries (notably the Bloom subcommand index.ts registries and many packages/client commands), so docs show up where consumers import/inspect commands.

Adds a lightweight scripts/check-command-jsdoc.ts and npm run check:command-jsdoc, plus a new PR GitHub Actions workflow (.github/workflows/jsdoc-check.yml) that runs the check to require JSDoc for each registry export entry.

^{Reviewed by Cursor Bugbot for commit a61efe1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Reviewed by Cursor Bugbot for commit 9087a9b. Configure here.}