docs: update incremental benchmarks (3.7.0)

[github-actions]

Automated incremental benchmark update for 3.7.0 from workflow run #546.

[greptile-apps]

Greptile Summary

This is an automated documentation-only PR that appends incremental benchmark results for version 3.7.0 to generated/benchmarks/INCREMENTAL-BENCHMARKS.md. The benchmark data was produced by a CI workflow run and inserted via github-actions[bot].

Key observations:

• All numeric values are internally consistent: percentages in the summary table match the raw millisecond values in the embedded JSON block (full build ↑5%, no-op ↑46%, 1-file ↑2%, JS resolve ↑31%).
• The speedup ratio (3.8x) correctly reflects jsFallbackMs (15.3) / nativeBatchMs (4).
• The \"native\": null field (absent native engine) mirrors the same condition seen in 3.6.0, but the explanatory note about the WAL race condition that was present in the 3.6.0 "Latest results" section was not carried forward to 3.7.0.
• The no-op rebuild time jumped 46% (13ms → 19ms) — notable in the trend but accurately recorded.

Confidence Score: 5/5

Safe to merge — documentation-only update with internally consistent benchmark data.

All values (percentages, raw ms, speedup ratio, file counts) cross-check correctly between the markdown summary table and the embedded JSON block. The single P2 comment about a missing native-engine absence note is a minor documentation improvement that does not block the merge.

No files require special attention.

Important Files Changed

Filename	Overview
generated/benchmarks/INCREMENTAL-BENCHMARKS.md	Automated benchmark update adding 3.7.0 WASM-only results (532 files, 6.4s full build, 19ms no-op, 558ms 1-file); data is internally consistent but the explanatory note for the absent native engine was not carried forward from 3.6.0.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[CI Workflow Run #546\nRelease 3.7.0] --> B[Run Benchmarks\non own codebase]
    B --> C{Engine}
    C -->|WASM| D[WASM Build Tiers]
    C -->|Native| E[native: null\nEngine absent]
    D --> F[Full Build: 6.4s ↑5%]
    D --> G[No-op Rebuild: 19ms ↑46%]
    D --> H[1-File Rebuild: 558ms ↑2%]
    B --> I[Import Resolution]
    I --> J[Native Batch: 4ms ↑3%]
    I --> K[JS Fallback: 15ms ↑31%]
    I --> L[Speedup Ratio: 3.8x]
    F & G & H & J & K & L --> M[Append to\nINCREMENTAL-BENCHMARKS.md]
    M --> N[Update Summary Table\n+ Latest Results section\n+ Embedded JSON block]

Loading

_{Reviews (1): Last reviewed commit: "docs: update incremental benchmarks (3.7..." | Re-trigger Greptile}

[greptile-apps]

Missing explanation for absent native engine

The 3.6.0 "Latest results" section included an explanatory note detailing that the native engine was absent due to a SQLITE_CORRUPT crash (WAL race condition between native and JS connections). In 3.7.0, "native": null in the JSON data but the analogous explanatory note has been dropped from the "Latest results" section.

If the same known WAL race condition still applies in 3.7.0, it would be helpful to carry forward the note (even in updated form) so readers aren't left wondering why there's no native build section. If the issue has been resolved and native was simply not run for a different reason, a brief note clarifying that would be equally useful.

Suggested change

	**Version:** 3.7.0 | **Files:** 532 | **Date:** 2026-04-01
	**Version:** 3.7.0 | **Files:** 532 | **Date:** 2026-04-01
	> **Note:** Native engine results are absent for 3.7.0. The known WAL race condition
	> between native and JS connections (first tracked in 3.6.0) may still apply.
	> WASM results are unaffected.