v0.5.0

From outside feedback: helper functions were taking Agent slots, and most node types never appeared.

Install

npm install --save-dev https://github.com/tangyishun9846/agent-runtime-map/releases/download/v0.5.0/agent-runtime-map-0.5.0.tgz
npx agent-runtime-map .

A folder no longer promotes the plumbing inside it

Every function under agents/ became an Agent at 72%, so isRecord, optionalText, and parseJsonBlock held four slots on a compressed map — and because an Agent outranks almost everything, they pushed real steps off it.

A predicate, a converter, or a function returning a bare primitive is plumbing wherever it sits. A name that says …Tool is still evidence about the function itself, so searchTool in tools/ is still a tool.

The map shows data and outbound calls again

Data access required the receiver to be literally db, prisma, supabase, drizzle, or knex; an outbound call required a literal https:// URL. An ordinary project showed neither.

prisma.order.findMany   → order data          0.88   named client
pool.query              → pool data           0.70   receiver convention
fetch("https://vendor") → vendor.example.com  0.92   host known
got.post(endpoint)      → got request         0.68   host computed

Confidence carries the difference rather than the two being reported as equally certain.

<LogicMap positions={…} />

For a host that already computes its layout: pass coordinates by node id and the layout engine is never imported. Verified — a map rendered from supplied positions makes no request for elkjs at all.