Root cause analysis: extraction can appear stuck at '正在提取xx-xx楼层' indefinitely
when the LLM API connection goes half-open (server stops sending data but keeps the
TCP connection alive). The SSE stream reader.read() would block forever with no
per-chunk idle timeout.
Changes:
1. llm/llm.js: Add LLM_STREAM_IDLE_TIMEOUT_MS (90s default) to
parseDedicatedStreamingResponse. When no SSE data is received for 90 seconds,
the read loop aborts with a clear timeout error instead of hanging forever.
The idle timeout is configurable per-request (defaults to 30% of config timeout,
minimum 30s).
2. index.js: Add EXTRACTION_VECTOR_SYNC_TIMEOUT_MS (120s) timeout wrapper around
syncVectorState in handleExtractionSuccess. Vector sync now uses a combined
AbortSignal (extraction signal + timeout) so that either user abort or 120s
timeout will break out. Vector sync timeout is treated as non-fatal (doesn't
abort the entire extraction batch).
- Fix#2: _executeStatements fallback now batches transactions (150/batch)
and reorders upsert-before-delete to prevent data loss on payload overflow
- Fix#3: Read/write migratedToAuthority marker in chat_metadata to prevent
re-overwriting from legacy sources after Authority migration
- Fix#1: Add OPFS → Authority migration channel (exportOpfsSnapshotForChat,
maybeImportLegacyOpfsSnapshotToLocalStore) inserted before IndexedDB in
migration chain
- Fix#4: Mark runtimeVectorIndexState dirty with triviumRebuildRequired
and trigger submitAuthorityVectorRebuildJob after all three migration paths
- Fix#5: Dual-save safety snapshots to Authority blob; rollback can now
recover from blob when local IndexedDB snapshot is unavailable
- Fix#6: Add isEmptyCheck detail and console.warn for near-empty stores
to help diagnose residual vs real data in store-not-empty skips
- Fix#7: Add overflow warning logs and sessionStorage persistence for
Authority offline queue max-items/max-bytes exceeded events
