You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Large TypeScript indexes avoid refreshing the reference graph twice** — CLI full scans, scoped updates, and MCP indexing now let a planned declaration-augmentation rebuild perform the single graph-finalization pass while keeping candidate-index staging active through that pass. Empty results still finalize deletions or an inherited graph pass, marker-only validation skips a whole-graph scan, late validation failures fall back before partial readiness, and `--memory-trace` attributes the graph sample after the augmentation work. Authoritative scans without TypeScript stamp the contract without rebuilding augmentation rows.
-**Large reference graphs no longer maintain the reverse candidate-symbol index row by row during candidate materialization** — Fresh, rebuilt, and high-churn full-graph indexing keeps this query-only index during raw reference persistence and drops it only when a graph refresh will actually repopulate candidates, including a TypeScript augmentation-owned pass. A filtered stat preflight skips reference and hotspot secondary-index staging when high-cardinality scoped targets are unchanged or only a sparse subset is expected to mutate indexed state; staging begins only when that estimate crosses the existing bulk threshold. Marker-only work also avoids rebuilding the candidate index. The candidate primary key remains available and success, cancellation, and recovery still converge on the identical final schema.
14
+
15
+
## 日本語
16
+
17
+
-**大規模 reference graph の candidate 構築中に candidate-symbol reverse index を行ごとに保守しなくなりました** — fresh、rebuild、および高 churn の full-graph indexing は、この query 専用 index を raw reference persistence 中は維持し、TypeScript augmentation が担当する pass を含め、graph refresh が candidate を実際に再構築するときだけ外します。filtered stat preflight は高 cardinality scoped target が全て unchanged、または indexed state を変更し得る target が疎な場合に reference / hotspot secondary-index staging を省き、その見積もり件数が既存 bulk threshold を超えた場合だけ staging を開始します。marker-only work も candidate index の再構築を避けます。candidate primary key を維持したまま、成功・cancellation・recovery の全経路で同一の最終 schema に収束します。
-**Parallel full scans start large tail files earlier** — extraction now skips metadata probes with a single worker or when all work fits in the first worker wave; otherwise it checks only a fixed-size suffix of at most 64 work items and starts known in-limit files largest-first, reducing the final worker-wave tail without adding a repository-wide metadata pass.
12
+
13
+
## 日本語
14
+
15
+
-**parallel full scanが末尾の大きなfileを早く開始します** — workerが1つ、または全workが最初のworker waveに収まる場合はmetadata probeを省き、それ以外では最大64件の固定長suffixだけを確認してsize取得済みで上限内のfileを大きい順に開始するため、repository全体のmetadata passを増やさず最終worker waveの長い尾を短縮します。
-**JavaScript and TypeScript symbol extraction reuses its sanitized snapshot** — module, supplemental-symbol, and private-scope analysis now share one column-preserving snapshot, avoiding a duplicate full-file lexical pass on scope-heavy files while retaining the flat-file pre-scan fast path.
-**Large indexing runs rebuild hotspot aggregate query indexes once instead of maintaining four trees row by row** — Full scans, rebuilds, high-churn scoped updates, and MCP bulk indexing now stage the cross-language hotspot indexes inside the existing aggregate refresh transaction when at least 64 dirty files account for most aggregate rows, including an empty pre-refresh aggregate during fresh/rebuild work. An exact probe bounded by dirty-row cardinality keeps the indexes for small or highly skewed updates, and success, cancellation, and failure preserve the same ready state and final schema.
-**Large FTS rebuilds avoid repeated automatic segment merges before their final optimize** — The standard and trigram indexes now disable routine automerge only around each transactional rebuild, restore their prior settings before commit, and retain crisis merging as a safety valve. Cancellation and failure roll back the configuration together with the rebuild.
0 commit comments