refactor: remove legacy event file store

docs/target-architecture.md

@@ -41,7 +41,7 @@ is explicitly deployed.
 - Ingest apps do not write business tables.
 - Ingest apps do not serve history query APIs.
 - Redis is not the long-term historical store.
-- `event-file-store` Parquet/DuckDB is not the default history store.
+- File-based event indexes are not part of the current build surface.
 - `telemetry_fields` parsing is not handled by this project when a separate
   field parsing service owns that job; the `telemetry_fields` query API is
   also disabled by default unless `TDENGINE_TELEMETRY_FIELDS_ENABLED=true`.
@@ -111,9 +111,8 @@ Production default:
 - `EVENT_FILE_STORE_ENABLED=false`.
 - `TDENGINE_TELEMETRY_FIELDS_ENABLED=false`.
 
-`event-file-store` remains an optional compatibility path for old low-level
-record APIs or local investigations. It should not be treated as the primary
-history backend.
+File-based event indexes have been removed; this app should keep history
+queries on TDengine and raw replay on `archive://...` references.
 
 ### Analytics App
 
@@ -192,10 +191,7 @@ flowchart LR
   through `optional-latest-state`.
 - raw-archive-store is absent from the default Maven reactor and available
   through `optional-raw-archive-store`.
-- event-file-store is absent from the default Maven reactor and available
-  through `optional-event-file-store`.
-- History APIs read from TDengine by default; Parquet/DuckDB is optional
-  compatibility only.
+- History APIs read from TDengine; file-based event indexes are not maintained.
 - Raw frame queries can return complete parsed JSON through `payloadJson.parsed`.
 - Location queries page over compact rows and reference raw records instead of
   duplicating full raw JSON.