Align routing docs with Registry Contract v1

[Wonderforge-Lab]

Purpose

Align live English routing and registry guidance with the merged Registry Contract v1 and generated-view implementation before Wave 4 zh-CN localization resumes.

Changes

• replace superseded “legacy / optional CSV rollup” wording with generated, read-only compatibility views;
• align operator-supplied accepted-tag guidance with the control-plane branch + PR rule;
• distinguish canonical registry/visitors/ registrations from optional lobby/visitors/ orientation profiles;
• clarify paired message artifact/registry lifecycle moves;
• remove obsolete “hardening branch” and “later” status language from the v1 contract/design docs.

Deliberate scope boundary

No locale files, schemas, scripts, fixtures, generated views, or runtime records are changed. zh-CN work resumes only after this source PR is reviewed and merged.

Verification

• python tests/test_validator_smoke.py
• python tests/test_tag_promotion.py
• python scripts/validate_repo.py --registry
• python scripts/generate_registry_views.py --check
• python tests/test_generated_views.py
• python tests/test_markdown_links.py
• python tests/test_bridge_config.py

All passed locally.