fix(compat): 🔧 refresh the compat baseline

[binggg]

What

Regenerate config/source/editor-config/compat-baseline.json against the current generated set (1,654 files: 15 machine configs / 1,639 text surfaces).

Why

Two changes rewrote generated surfaces after the baseline was last regenerated, and neither regenerated it:

• The guideline entry projected into every IDE rule file (AGENTS.md, CLAUDE.md, .cursor/rules/…) moved with the frontend deploy guidance — 18 aggregated guide surfaces.
• The miniprogram-development skill gained its account/subject and environment preflight, which moved its three files across each of the eleven IDE targets — 33 surfaces.

Both groups carry hashMode: report, so the drift never failed a check. It only left 51 entries stale in every diff report, which is exactly the noise that hides the next real regression. Re-recording them now keeps the report meaningful.

Text surfaces are unchanged in count (1,639 expected / 1,639 generated), so this is a hash re-record only — no file was added or dropped.

How verified

• node scripts/diff-compat-config.mjs → No compatibility diffs found.
• node scripts/check-compat-baseline-sync.mjs --base origin/main → OK: no version declaration changed
• npx vitest run tests/compat-baseline.test.js → 3 passed
• node scripts/check-internal-refs.mjs --base origin/main → OK

[binggg]

Closing as superseded. The compat baseline on main has since been regenerated (current generatedAt 2026-09-28T08:53) and carries 22 more entries than this branch — the cloud-api-operations recipe files added afterwards. This branch has no entries that main lacks, and all 67 differing hashes are older, so merging it would revert the baseline. No further action needed here.