code-index: a one-file edit re-verifies the whole sealed generation (~5 min, 2.3 GB peak) #4507

Observed

Measured by the daemon-memory investigation (PR #4503 lane) on a release build of origin/master 9b8789c, isolated profile, fresh clone of this repository (6.1k files):

• A one-file edit triggers an incremental pass whose physical footprint peaks at 2.3 GB and that takes about 5 minutes; footprint returns to 0.38 GB afterwards.
• The pass re-reads every sealed segment of the active generation instead of only what the changed file touches.

On the live daemon the same checkout logged refresh passes of 870 s and 1,489 s that ended outcome="noop".

Expected

An incremental pass costs in proportion to the changed files (re-extract the file, re-link its edges, reuse unchanged sealed segments), not a full-generation re-verify.

Why it matters

Every edit in an active checkout pays minutes of multi-core CPU and GBs of transient memory, which is a large share of the sustained daemon CPU users see while agents edit code.