#6596: Fix pre-existing formatting issues causing CI failures

## Fix pre-existing formatting issues causing CI failures Ran `pnpm format:fix` to address formatting violations that were causing CI failures on other PRs. ### Files Fixed - docker-compose.yml - docs/channels/telegram.md - docs/concepts/model-providers.md - docs/docs.json - docs/providers/moonshot.md - docs/start/onboarding.md - docs/web/control-ui.md - skills/canvas/SKILL.md ### Context These appear to be pre-existing formatting issues that were caught when CI runs `oxfmt --check`. Not my submission to correct, but this should make CI complain less if merged. Only whitespace/formatting changes - no functional modifications. <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR applies automated formatting fixes across YAML/JSON/docs to satisfy `oxfmt --check` in CI. Most changes are whitespace-only, but the Moonshot docs formatting altered the sync markers used by `scripts/sync-moonshot-docs.ts`, which is part of the repo’s docs maintenance workflow; those markers should remain as the exact strings the script searches for. <h3>Confidence Score: 2/5</h3> - Not safe to merge as-is due to a docs-sync marker regression. - While the intent is formatting-only, the Moonshot docs markers were changed in a way that will break `scripts/sync-moonshot-docs.ts` (string match for HTML comment markers), causing the sync script to error and potentially blocking future updates. - docs/providers/moonshot.md, docs/concepts/model-providers.md, scripts/sync-moonshot-docs.ts <!-- greptile_other_comments_section --> <!-- /greptile_comment -->