Add federated ecosystem control plane

[snapsynapse]

Summary

• define the federated Harnessie authority map and release trains in ECOSYSTEM.md
• add machine-readable topology in ecosystem.yaml
• add an offline, read-only status command with optional non-authoritative GitHub observations
• extend release propagation through the verify action and Homebrew while keeping engine wrappers independent
• record the adopted product contract in INTENT.md, NEXT.md, and CHANGELOG.md

Safety and sovereignty

• offline local state is the default and remains complete without GitHub
• GitHub observations require explicit --github
• manifest version-source paths fail closed on repository escape
• no submodules, monorepo coupling, dashboard, credential reads, or mutations
• public staged-diff scrub passed with zero private-name matches

Verification

• python3 -m pytest -q: 293 passed, 8 skipped
• python3 -m harness.cli eval: 44/44 passed
• python3 -m harness.cli verify-manifest: 9 files verified
• python3 scripts/ecosystem_status.py --validate: 4 components
• local status reports both downstream core pins matching 0.7.1
• git diff --check: clean