bearing-exploringlisted

# Exploring Codebases with GitNexus <!-- BEGIN GENERATED: graph-uncertainty — bearing regenerates this block; edits here are replaced on update --> ## The graph can be wrong A zero is not absence; a near-0.5 `r.confidence` edge is a lead, not proof (~92% of `USES`); a count can be a floor — `impact` says which in `epistemic`. Before a conclusion that matters, confirm with a scoped `Grep` (allowed here, not a gate violation) and say which check you ran. <!-- END GENERATED: graph-uncertainty --> ## The type layer is indexed too On a typed codebase most of the graph is not the call graph: | Question | Query | | --- | --- | | Who uses this interface / type? | `USES` → `Interface` / `TypeAlias` | | What fields does this type own? | `HAS_PROPERTY` → `Property` | | Where is this property actually read or written? | `HAS_PROPERTY` then `ACCESSES` (carries `reason: read`/`write`) | | Circular imports between files | `check({ cycles: true })` | Measured on one real repo: 23,018 `Property` nodes and 7,280 `USES` edges against 27,611 `CALLS`. **Raw cypher line numbers are 0-BASED; every other tool hands them to you 1-BASED.** A function reported at `startLine: 149` begins on line 150 — 149 is the last line of its docblock. Jumping straight from a cypher result into `Read`/`sed` lands one line early, every time, silently. Add 1 to values that came from cypher; use `context`/`query`/`impact` numbers as given. **Check `r.confidence` before you conclude.** `CALLS` and resolved `ACCE