Skip to content

Native resolution reads

Jerry Holland edited this page Nov 14, 2026 · 5 revisions

Native resolution reads

The bounded increment in #83 added five in-process reads through Rust and gitoxide. Git stays the default engine and performs every mutation. Unsupported profiles, inputs the backend refuses, and native errors use complete-operation Git fallback.

The implementation landed in PR #85 as an optional N-API binding beside the JavaScript CLI. Since v0.24.0 (#243) it is part of the Rust cst itself: there is no binding, prebuild, or separate build step, and --engine native selects it for one invocation. The issue retains the three Windows latency checks and full platform qualification.

For the supported profile, the operations, refusals, and how equality is checked, use the maintained native-engine guide.

From a checkout, build cst and check the native backend:

npm run build:native
native/target/release/cst doctor --engine native
native/target/release/cst resolve list --json --engine native

The doctor must report the native engine available with the five supported operations. nativeReads metrics count executed operations; a selected native engine alone does not prove native execution.

Latency qualification remains Windows-only on lab-windows-a; the performance checkpoint measures each read under both engines. Functional Windows/Ubuntu and Node 24 floor qualification remains mandatory. Evidence belongs on #83 or CI artifacts, not in a second benchmark baseline.

This increment does not open native mutations, a canonical store, or Gate B. The resolved owner decision remains recorded in Human action 18.

Clone this wiki locally