Greptile Summary

This PR fixes a silent engine-override gap where connection.ts read process.env.CODEGRAPH_ENGINE directly and pipeline.ts used ctx.opts.engine || 'auto', both bypassing any engine value set in .codegraphrc.json. All three call sites now use the unified priority chain opts.engine ?? config.build.engine ?? 'auto', which already incorporates the env-var path via applyEnvOverrides.

• connection.ts: openRepo() and openReadonlyWithNative() now call loadConfig().build.engine (cached, negligible overhead); openReadonlyWithNative gains an optional opts.engine escape hatch mirroring openRepo().
• pipeline.ts: loadConfig() is moved above the enginePref computation in setupPipeline() so config.build.engine is populated before the native-availability check and initializeEngine() reads it; || is replaced with ?? throughout the engine chain.
• fn-impact.ts: Parentheses lint fix only, no functional change.

Confidence Score: 5/5

Safe to merge — changes are narrowly scoped to wiring an existing config value into call sites that were previously ignoring it, with no new code paths or data mutations.

All three engine-selection sites now use the same priority chain; loadConfig() is cached so per-call overhead in connection.ts is negligible; moving loadConfig() earlier in setupPipeline() is safe because openDb/initSchema have no dependency on ctx.config; the ?? vs || change is type-safe given the TypeScript union type on engine.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[CLI / programmatic call] --> B{opts.engine set?}
    B -- yes --> E[use opts.engine]
    B -- no --> C[loadConfig / ctx.config]
    C --> D{config.build.engine set?}
    D -- yes --> E
    D -- no --> F[fallback: 'auto']
    E --> G{engine !== 'wasm'?}
    F --> G
    G -- yes --> H{isNativeAvailable?}
    H -- yes --> I[open NativeDatabase / rusqlite]
    H -- no --> J[open better-sqlite3]
    G -- no --> J

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[CLI / programmatic call] --> B{opts.engine set?}
    B -- yes --> E[use opts.engine]
    B -- no --> C[loadConfig / ctx.config]
    C --> D{config.build.engine set?}
    D -- yes --> E
    D -- no --> F[fallback: 'auto']
    E --> G{engine !== 'wasm'?}
    F --> G
    G -- yes --> H{isNativeAvailable?}
    H -- yes --> I[open NativeDatabase / rusqlite]
    H -- no --> J[open better-sqlite3]
    G -- no --> J

_{Reviews (4): Last reviewed commit: "fix: add engine override param to openRe..." | Re-trigger Greptile}

Codegraph Impact Analysis

4 functions changed → 42 callers affected across 32 files

• openRepo in src/db/connection.ts:370 (28 transitive callers)
• openReadonlyWithNative in src/db/connection.ts:427 (8 transitive callers)
• initializeEngine in src/domain/graph/builder/pipeline.ts:63 (4 transitive callers)
• setupPipeline in src/domain/graph/builder/pipeline.ts:173 (5 transitive callers)

Addressed Greptile P2 findings:

• Finding 1 (line 433, openReadonlyWithNative engine override): Fixed in f7606b6. Added opts: { engine?: 'native' | 'wasm' | 'auto' } parameter (default {}), matching openRepo()'s escape hatch. Priority chain is now opts.engine ?? loadConfig().build.engine ?? 'auto' — identical to openRepo(). Backward-compatible; no callers updated. TypeScript compiles cleanly.

• Finding 2 (line 387, loadConfig() uses process.cwd()): Pre-existing limitation, not a regression from this PR — the prior process.env.CODEGRAPH_ENGINE approach was equally process-wide. Tracked as connection: loadConfig() uses process.cwd() instead of DB root when customDbPath is set #1605 for follow-up when --db / multi-repo support is hardened.

@greptileai