feat(lattice): adapt Gateway topology fragments

[mgazza]

Summary

• add a pure, explicitly enabled Gateway retained-topology Lattice fragment publisher
• persist immutable generation/fingerprint-bound snapshots and expose the common structural adapter API
• invalidate the shared compiler on topology, liveness, and removal changes
• publish REFERENCE-only aliases plus stable node-ID and serial identities without granting materialization authority
• keep durable removal irreversible through ordinary retained replay and filter node tombstones from aliases and diagnostics
• validate provider ownership, document-version monotonicity, and inspection-only binding coordinates

Safety

• default off and not registered in the production component graph
• no PredBat configuration mutation, materializer callback, MQTT publication, or control write
• no PRIMARY/CONTROL roles or config projections
• Gateway retained topology remains explicitly limited to v0.2/v0.3 in this tranche; v0.4 schedule transport is independent
• a removed integration requires a future explicit re-enrol operation; ambient retained messages cannot resurrect it

Validation

• 105 focused and adjacent tests pass on Python 3.9
• 86 focused and adjacent tests also pass on Python 3.14
• Black, Ruff, cspell, pre-commit, and diff checks pass
• GitNexus: LOW risk, 50 changed symbols, zero affected execution flows

Stack

• base: feat(lattice): add auto-config shadow telemetry #4330
• programme: Predictive-Cloud-Ltd/predbat-saas-infra#466
• fragment compiler/materializer tracker: Predictive-Cloud-Ltd/predbat-saas-infra#561