bearing-api-routeslisted

# API Routes <!-- 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 kit auto-detects the router style at install and writes `.bearing/gitnexus-api-profile.json`. Run `npm run bearing:detect-api` to refresh it after major server changes. Route the work by profile. | Profile | What it means | Use | | --- | --- | --- | | `framework` | Indexed `Route` nodes exist | `api_impact` → `route_map` → `shape_check` | | `framework-likely` | Framework imports seen, no Route nodes yet | Try `api_impact`; if empty after refresh, treat as custom | | `custom` | Hand-rolled dispatcher, zero Route nodes | Graph tools on dispatcher symbols (below) | | `none` | No HTTP layer detected | Skip API tooling | ## Framework routers (Express / Fastify / Hono / Next route handlers) ``` 1. gitnexus_api_impact({ route: "/api/<path>", repo: "__GITNEXUS_REPO__" }) # consumers + shape + risk 2. gitnexus_route_map({ route: "/api/<path>" }) # handler + middleware chain 3. gitnexus_shape_check({ route: "/api/<path>" }) # response keys vs cons