feat(cli): add mops toolchain info --versions

[Kamirus]

Scripts can list every stable GitHub release for toolchain tools (moc, lintoko, wasmtime, pocket-ic) — the missing counterpart to mops info <package> --versions.

Before:

$ mops toolchain info moc --versions
error: unknown command 'info'

After:

$ mops toolchain info lintoko
lintoko
latest: 0.11.0
pinned          0.7.0
repository      https://github.com/caffeinelabs/lintoko
versions        0.11.0, 0.10.0, 0.9.0, 0.8.0, 0.7.0, 0.6.0, 0.5.1, 0.5.0, 0.4.3, 0.4.2 (+7 more)

$ mops toolchain info moc --versions | tail -5
1.8.2
1.9.0
1.10.0
1.10.1
1.11.0

--versions excludes drafts and prereleases. Stable versions match what mops toolchain update and mops toolchain use <tool> latest resolve to. Interactive mops toolchain use without a version may still show prereleases in its picker.

Works without a mops.toml. For aggressive cache warming against GitHub rate limits, set GITHUB_TOKEN.

What is unchanged

• mops toolchain use, update, and bin behavior is unchanged aside from paginated latest resolution (stops at the first stable release instead of scanning only the first 10).

[github-actions]

Cursor AI review

👍 APPROVE — looks safe to merge

Category	Assessment	Details
Summary	✅	Adds mops toolchain info <tool> with --versions, plus paginated GitHub release fetching and a fix so getLatestReleaseTag finds the newest stable release beyond the first page of results.
Code Quality	✅	Reuses the package info UX pattern (label, --versions, recent-history display); release filtering/sorting is extracted into release-tags.ts and shared via toolchain-utils.ts.
Consistency	✅	Commander wiring, docs page, changelog, skill, and overview link are all updated; command works without mops.toml like the PR describes.
Security	✅	Read-only GitHub API calls only; optional GITHUB_TOKEN for rate limits is documented, no new secret handling.
Tests	✅	Unit tests cover semver sorting and stable-tag filtering; matches existing toolchain test style (no network snapshots).
Maintainability	✅	Small, focused diff; paginated getLatestReleaseTag fixes a real edge case where 10+ consecutive prereleases/drafts blocked use latest / update.

Verdict

Decision: APPROVE
Risk: Low
Reason: This is a well-scoped CLI addition with docs/changelog/skills in sync and a contained correctness fix to latest-release resolution. I found no probable bugs or changes that warrant blocking or human escalation.

---

Generated for commit 02c96e1