♻️ Normalize formatting across Rules V3 to reduce noisy pull requests

Requested by: @KostaMadorsky via YakShaver.ai 🦬
cc: @KostaMadorsky, @Marxoz, @PothieuG, @Freego1783, @adamcogan

Hi Team!

  🟥  Watch the video (1 min 13 sec)

Pain

After migrating to Rules V3 (TinaCMS), small content changes result in large pull requests due to widespread automatic formatting differences. This makes it difficult to review and identify the actual intent of changes. Introduce a one-time or standardized formatting approach across all rules so that future pull requests only reflect meaningful content changes rather than formatting noise.

Acceptance Criteria

1. A consistent formatting standard is defined for Rules V3 (TinaCMS) files.
2. All existing rules are formatted using the agreed standard in a single, dedicated change.
3. After formatting normalization, small edits (e.g., adding an end intro tag or minor text changes) result in minimal and clearly visible diffs.
4. Formatting rules are documented or enforced (e.g., via tooling or CI) to prevent future drift.
5. No functional behavior of existing rules is changed as part of the formatting normalization.

Screenshot

Figure: Small code changes obscured by extensive formatting differences in a pull request

Locate the Rules V3 (TinaCMS) files and inspect any existing formatting configuration or CI checks. Determine how the formatting standard can be applied without functional changes, then verify that a small content edit produces a minimal diff and that formatting is documented or enforced.