chore: remove xinda ingestion modules

docs/module-data-flow.html

@@ -265,7 +265,7 @@
     <div class="summary-grid">
       <div class="summary-card">
         <strong>接入方式</strong>
-        <span>Netty TCP、MQTT、后续可扩展更多 Inbound Adapter；Xinda Push 不在默认生产面。</span>
+        <span>Netty TCP、MQTT、后续可扩展更多 Inbound Adapter；信达 Push 源码已删除。</span>
       </div>
       <div class="summary-card">
         <strong>统一模型</strong>

docs/superpowers/plans/2026-06-23-gb32960-service-split.md

@@ -13,7 +13,9 @@
 ## Current-State Notes
 
 - Existing all-in-one entrypoint: `modules/apps/bootstrap-all/src/main/java/com/lingniu/ingest/bootstrap/IngestApplication.java`.
-- Existing all-in-one module: `modules/apps/bootstrap-all/pom.xml` imports protocols, sinks, history, state, stat, command gateway, MQTT, Xinda, and JT modules.
+- Existing all-in-one module at the time of this plan imported protocols,
+  sinks, history, state, stat, command gateway, MQTT, and JT modules. Xinda was
+  later removed from source and build configuration.
 - Existing GB32960 handler: `modules/protocols/protocol-gb32960/src/main/java/com/lingniu/ingest/protocol/gb32960/inbound/Gb32960ChannelHandler.java`.
 - Existing handler currently writes report ACK before `dispatcher.dispatch(rf)`.
 - Existing `DisruptorEventBus` publishes to sinks asynchronously and does not wait for sink completion.

docs/superpowers/specs/2026-06-23-gb32960-production-readiness-design.md

@@ -2,7 +2,7 @@
 > Use `docs/target-architecture.md` and
 > `docs/superpowers/specs/2026-06-29-vehicle-ingest-redesign.md` for the
 > current production architecture: TDengine is the default hot history store,
-> `event-file-store` is optional compatibility only, and Xinda Push is legacy.
+> `event-file-store` and Xinda Push have been removed from the production codebase.
 
 # GB32960 Production Readiness Design
 

docs/target-architecture.md

@@ -17,9 +17,8 @@ Active production protocols:
 | JT/T 808 | `jt808-ingest-app` | `vehicle.event.jt808.v1` | `vehicle.raw.jt808.v1` |
 | Yutong MQTT | `yutong-mqtt-app` | `vehicle.event.mqtt-yutong.v1` | `vehicle.raw.mqtt-yutong.v1` |
 
-Xinda Push is legacy and is not part of the default production surface.
-It may remain in source for reference, but new optimization work should target
-the active protocols above.
+Xinda Push source, Maven profile, deployment bindings, and history consumers
+are removed. New optimization work should target the active protocols above.
 
 JSATL12 attachment upload is also outside the default production reactor. Keep
 it available through the `optional-attachments` profile until an attachment app
@@ -187,7 +186,7 @@ production deployment.
 
 - Active production deployment contains GB32960, JT808, Yutong MQTT,
   vehicle-history, and vehicle-analytics apps.
-- Xinda Push is absent from default deployment and history consumer bindings.
+- Xinda Push source and deployment bindings are removed.
 - JSATL12 is absent from the default Maven reactor and available through
   `optional-attachments`.
 - vehicle-state-service is absent from the default Maven reactor and available