Add kind field ("api" | "page" | "action" | "websocket") to EndpointInfo

[jorgeraad]

EndpointInfo today exposes the wire shape of a route (method, path, handler, file, params, auth) but not its categorical role. Consumers like apex currently derive that with hand-written file-path regex, which puts framework-specific knowledge in the wrong repo.

Changes

Add a required kind field to EndpointInfo in src/types.ts, plus an optional kind? parameter to the endpoint() factory in src/utils.ts (defaulting to "api" for migration ergonomics). Existing extractors get the default — only server-actions and FastAPI websocket routes set explicit values.

Four values

Kind	Meaning	Set by
"api"	REST / GraphQL / RPC / generic JSON HTTP routes	Default for all extractors
"page"	Server-rendered or client-routed page returning HTML/RSC	Future: Next.js pages, Rails views, etc.
"action"	RPC-style call invoked from UI (Next.js Server Actions)	server-actions.ts extractor
"websocket"	Persistent bidirectional channel	fastapi.ts extractor (for @app.websocket)

Files changed

• src/types.ts — Added EndpointKind type union; added required kind field to EndpointInfo
• src/utils.ts — Added optional kind? parameter to endpoint() factory, defaulting to "api"
• src/extractors/server-actions.ts — Set kind: "action" for server action endpoints
• src/extractors/fastapi.ts — Set kind: "websocket" for FastAPI websocket routes
• src/format.ts — Include kind in JSON and NDJSON output
• src/format-impact.ts — Include kind in impact JSON and NDJSON output
• src/index.ts — Export EndpointKind type from public API

Design

The factoring is deliberate: method carries the HTTP verb (or wire-shape distinction for WS / ACTION), kind carries the protocol/role category. Two fields, orthogonal concepts.

Foundation for the Next.js page extraction work and future page detection in Rails / Django / FastAPI / Spring view-rendering routes.