docs: align comments with tdengine history path

modules/core/ingest-api/src/main/java/com/lingniu/ingest/api/event/RawArchiveKeys.java

@@ -11,8 +11,8 @@ import java.util.Map;
  * Shared raw-archive key conventions used by Dispatcher, archive sink, and query services.
  *
  * <p>32960 生产链路里，RAW .bin 文件本体按 {@code 日期/协议/VIN/eventId.bin} 落在 archive 根目录，
- * DuckDB 只保存 {@code archive://...} 引用和查询索引。这个类集中维护 key 规则，避免接收端、落盘端、
- * snapshot 查询端对目录分区的理解不一致。</p>
+ * TDengine raw_frames 或兼容索引只保存 {@code archive://...} 引用。这个类集中维护 key 规则，
+ * 避免接收端、落盘端、snapshot 查询端对目录分区的理解不一致。</p>
  */
 public final class RawArchiveKeys {
 

modules/core/ingest-api/src/main/java/com/lingniu/ingest/api/event/TelemetryFieldValue.java

@@ -3,11 +3,11 @@ package com.lingniu.ingest.api.event;
 /**
  * One normalized telemetry field value.
  *
- * <p>Protocol mappers use stable internal field keys so Kafka, Parquet, Redis,
+ * <p>Protocol mappers use stable internal field keys so Kafka, TDengine, Redis,
  * and statistics do not depend on protocol-specific names.
  *
  * <p>{@code value} 统一用字符串承载，真实类型由 {@code valueType} 表达。这样 Kafka
- * protobuf、CSV 导出、DuckDB JSON 字段和前端展示可以共用同一份字段结构；数值精度/格式化
+ * protobuf、CSV 导出、JSON 字段和前端展示可以共用同一份字段结构；数值精度/格式化
  * 由查询层或前端按 {@code valueType + unit} 决定。
  */
 public record TelemetryFieldValue(

modules/core/ingest-api/src/main/java/com/lingniu/ingest/api/event/TelemetrySnapshot.java

@@ -12,9 +12,9 @@ import java.util.Optional;
 /**
  * Normalized full-field telemetry snapshot for one parsed vehicle event.
  *
- * <p>This is the shared contract for Kafka, Parquet history, Redis hot state,
+ * <p>This is the shared contract for Kafka, TDengine history, Redis hot state,
  * and statistics. It intentionally lives in {@code ingest-api} and has no
- * Spring, Kafka, Redis, or DuckDB dependency.
+ * Spring, Kafka, Redis, or TDengine dependency.
  */
 public record TelemetrySnapshot(
         String eventId,