style: Automated JSON format and sort

[github-actions]

This is an automated PR containing formatting and sorting updates for JSON files.

---

Summary by cubic

Standardized JSON formatting and key ordering across the repo to enforce strict, valid JSON and reduce noisy diffs. No schema or data changes.

• Refactors
  • Consistent 4‑space indentation, key order, and final newlines across all JSON files.
  • Removed comments and trailing commas to keep JSON strict and parseable.
  • Normalized numeric literals (e.g., 0.10 → 0.1) without changing values.
  • Reordered objects/arrays only (e.g., moved “HK Missile” within weapons.json), with no content edits.

^{Written for commit f1a7a55. Summary will update on new commits.}

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (54 files)

• .github/pr-title-checker-config.json
• .goborc.json
• datafiles/data/armour.json
• datafiles/data/dialogue/sisters.json
• datafiles/data/gear.json
• datafiles/data/mobility.json
• datafiles/data/psychic_disciplines.json
• datafiles/data/psychic_powers.json
• datafiles/data/ruins_loot.json
• datafiles/data/ships.json
• datafiles/data/technologies.json
• datafiles/data/traits.json
• datafiles/data/unit_stats.json
• datafiles/data/vehicle_gear.json
• datafiles/data/vehicles.json
• datafiles/data/weapons.json
• datafiles/main/chapter_advantages.json
• datafiles/main/chapter_disadvantages.json
• datafiles/main/chapter_symbols/load_sets.json
• datafiles/main/chapters/33.json
• datafiles/main/chapters/34.json
• datafiles/main/chapters/35.json
• datafiles/main/chapters/36.json
• datafiles/main/chapters/37.json
• datafiles/main/name_loader.json
• datafiles/main/names/chaos.json
• datafiles/main/names/eldar.json
• datafiles/main/names/genestealercult.json
• datafiles/main/names/hulk.json
• datafiles/main/names/imperial.json
• datafiles/main/names/imperial_ship.json
• datafiles/main/names/knightly.json
• datafiles/main/names/mongol.json
• datafiles/main/names/ork.json
• datafiles/main/names/ork_ship.json
• datafiles/main/names/roman.json
• datafiles/main/names/roman.json
• datafiles/main/names/sector.json
• datafiles/main/names/space_marine.json
• datafiles/main/names/star.json
• datafiles/main/names/tau.json
• datafiles/main/role_markings/load_sets.json
• datafiles/main/squads/base_squads.json
• datafiles/main/squads/company_squad_builds.json
• datafiles/main/squads/equal_scouts.json
• datafiles/main/squads/equal_specialists.json
• datafiles/main/squads/equal_spescout.json
• datafiles/main/version.json
• datafiles/main/visual_sets/Company_marks_roman_right_knee/data.json
• datafiles/main/visual_sets/Company_marks_roman_right_shoulder/data.json
• datafiles/main/visual_sets/Test_set/data.json
• datafiles/main/visual_sets/mycrusaderbits/data.json
• datafiles/main/visual_sets/use_sets.json
• prefabs/io.gamemaker.sdfshaders-1.0.0/prefab.json
• stitch.config.json

---

_{Reviewed by step-3.7-flash · Input: 202.5K · Output: 13.3K · Cached: 1.4M}

[EttyKitty]

I like this a lot, but not sure how I feel about chapter files getting sorted as well, and generally depending on A-Z sorting.
Not sure if a JSON schema can be used for custom key order.