Lower a `left`/`right` assignment-expression node into an `Assign`. JS/TS and Rust grammars use the same field names for simple assignment; compound a

Detection options for the resolved query channels — shared by `analysis` and `divergence`.

Discover supported source files under all `roots`, then sort and deduplicate canonical path aliases. The returned path spelling is still the stable, u

Emit a statement into `out`, applying block flattening and loop / control desugaring that needs to insert sibling statements.

Evaluate the detector's candidate scores against a labeled golden.

Can this unit ever participate in the exact `semantic` channel's merge claim? The product asserts behavioral equality only for strict-exact-safe unit

The exact-claim gate when the caller already has the two relevant facts.

Exact self-field place proof for receiver-aware field-write fingerprints.

Extract all units of `il` passing the size gates, with features computed.

Byte ranges of every `<script>…</script>` block's *content*, plus whether any block declares TypeScript (`lang="ts"`/`tsx` or a TypeScript `type`). A

The structural shape of the fix IF this family is acted upon — a **decidable classification from unit kinds and channel, NOT a worth-it verdict (that

The directory a family lives in (the parent of its largest copy) — nose's spatial unit.

The existing helper a `call-existing-helper` family already contains: the lone named function/method whose body the other (inline) members recompute (

The aggregate value-class of a near family's varying spots, from the #315 graded witness: `leaf-only` (every hole is a clean value-leaf and the witnes

Find the first `Return` node with one computed (non-var/lit) child — a direct-return fragment root.

The body `Block` of the first `Func` — the multi-statement fragment body.

Fold a non-empty list of condition nodes with left-associative `Or`.

Go's bit-clear `a &^ b` ≡ `a & ^b` (AND-NOT) — it clears the bits of `a` that are set in `b`, which is NOT the same as `a & b`. Desugar to that two-no

Go static imports are lowered as namespace facts that can prove package aliases for selected stdlib-style recognizers.

Does `node` have a *direct* child token of the given `kind`? Used to read an operator token (`--`, `++`) off the node it belongs to without being fool

Divergent-edit **hazard**: how likely this family is to be edited inconsistently (one copy changed, the siblings missed) and cause a bug. A *severity*

The identity element of a reduction operator (`acc op identity = acc`), used to neutralize a filtered-out element in a guarded reduction.

Lower a `condition`/`consequence`/`alternative`-shaped CST node into a canonical [`If`]. Those three field names are *shared* across the C-family gram

Shared shape of static-import proof facts. The assignment remains in IL so import text participates in the syntax/near floor, but the `Seq` payload is

Whether `node` is a provider-owned literal value that can be snapshotted into an importing file without treating raw import coordinates or API spellin