docs: remove token addresses from support pages

[acedatacloud-dev]

Why

Seventeen localized customer-support pages publish GEuu...pump as CA. Repository and runtime evidence identifies that address as the previous $ACE mint, while the platform, current coin documentation, whitepaper, and benefit logic use the post-2025-12-27 GnHp...pump mint.

More importantly, a customer-support contact page is the wrong place to assert any token contract. Placing CA between social and email contacts makes the address look like a prerequisite for receiving help and lets identity drift spread across translations. Replacing it with the new mint would preserve the same information-architecture problem.

What changed

• remove the stale CA line from 17 localized support pages;
• leave the Simplified Chinese support page unchanged because it already contains no token address;
• add a checker that rejects CA, Contract address, or Mint fields in every localized support page;
• explicitly guard both the current and previous known mint addresses;
• add three focused tests and a dedicated read-only CI workflow.

Validation

• python3.12 tests/test_support_identity.py — 3/3 passed
• python3.12 scripts/check_support_identity.py — 18 localized support pages passed
• python3.12 tests/test_sync_from_platformbackend.py — 30/30 safeguards passed
• python3.12 scripts/validate_nav.py — schema OK, 15 navigated languages validated
• diff audit — 17 support pages only remove the CA line and adjacent blank line
• git diff --check — clean

Scope boundaries

This PR does not choose or publish a token contract, alter token benefits, edit the whitepaper, contact CoinGecko, or change support channels. Current/previous mint identity and migration history belong on a dedicated token source-of-truth surface and are handled separately.

Rollback

Revert the commit to restore the lines and remove the guard. No runtime or database migration is involved beyond normal Docs publishing.

🤖 Generated with Claude Code