chore: regenerate CLI schema

[margaretjgu]

Fixes the remaining schema drift on main. Running npm run build:schema produces a small diff (8 insertions, 29 deletions) that was not committed when the larger schema update landed.

[github-actions]

🔍 Preview links for changed docs

⏳ Building and deploying preview... View progress

This comment will be updated with preview links when the build is complete.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ COPYPASTE	jscpd	yes		no	no	0.97s
✅ REPOSITORY	gitleaks	yes		no	no	62.98s
✅ REPOSITORY	git_diff	yes		no	no	0.51s
✅ REPOSITORY	secretlint	yes		no	no	32.75s
✅ REPOSITORY	trivy	yes		no	no	18.79s

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository

[JoshMock]

LGTM.

schema.json seems to be a possible source of merge conflicts, so we may need to look into ways we can prevent that from being a regular source of pain. cc @Mpdreamz