[GaganSD]

Summary

• Replace whole-history rollback cloning with per-file transactions and durable, resumable indexing.
• Keep the dashboard responsive with committed-cache reads, live progress, and one managed worker for large archives.
• Protect worker ownership, rebuild generations, interrupted scans, and cache/store consistency; add Node 22.15/22/24 CI coverage.
• Fixes herdr-insights: first scan never finishes on large session histories because Herdr stops it at 30 seconds #109.

Validation

• 217 tests pass on Node 22.15.0, 22.23.4, and 24.22.1; 29 tooling tests, package checks, and changed-file lint pass.
• Final-head synthetic 10,008-file benchmark: 3.16 s cold, 0.62 s warm; zero warm transcript reads or store rewrites. Cached status responds in 56 ms median.
• Verified concurrent launchers, kill/restart recovery, rebuild fencing, and a throttled worker lasting over 30 seconds.
• Native loaded/settings/menu checks pass with 10,000 rows; an existing-app synthetic scan completes without mod errors.
• Installed locally through the standard installer; staged native check passes, existing data and layout preserved.
• Regression coverage includes concatenated/skippable/empty zstd frames and archive replacement on supported Node versions.

Compatibility

• No new dependencies or raw-transcript persistence; Node 22.15+ remains required.
• An interrupted compressed file is replayed from its beginning; committed checkpoints survive.
• Legacy ownerless locks remain fail-closed and require verified manual recovery.

[greptile-apps]

Confidence Score: 2/5

[Medium impact] The changes affect the local Insights scan and dashboard workflow.

Fix the generation mismatch, foreign-host signal target, and plain-file stall before merging.

Findings

1.  Unchanged settings block refreshes ▶
2.  Wrong local process gets stopped ▶
3.  Long transcript lines stall indexing ▶
4.  Worker exits during startup ▶
5.  Empty frames bypass scan limits ▶

Summary

Replaces whole-history rollback copies with per-file transactions and adds resumable scans, a detached worker, committed presentation caches, and live progress.

• File scans limit rollback work to the records they change.
• Large history scans continue in one worker while the dashboard stays responsive.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Dashboard refresh] --> B{Writer lock available?}
  B -->|No| C[Read committed cache or store]
  B -->|Yes| D[Run bounded scan]
  D --> E[Commit accepted file changes]
  E --> F{Unfinished archive or database?}
  F -->|Yes| G[Claim and start worker]
  F -->|No| C
  G --> H[Worker holds writer lock]
  H --> I[Commit completed files]
  I --> C
  C --> J[Show committed dashboard]
  J --> K{Work remains?}
  K -->|Yes| A

Loading

_{Reviews (1) · Last reviewed commit: "fix(insights): reset archive parser cont..." · Reviewed by Greptile}