v0.9.1

Patch release: the Python adapter names each route after its own decorator.

Fixed

• routeFromDecorators resolved a route's path with a file-wide lookup by the decorator's dotted name, so every same-method route in a module took the first one's path. A route now reads the decorator call that sits above its own declaration. file:line, symbol, and edges were always correct — the damage was to name and metadata.path, which is what documentedCapabilityLabel matches on, so a single-module app's feature list collapsed. (#61, closes #60)

One route per file hid this: the file-wide lookup and the per-declaration lookup return the same call. The TypeScript adapter reads the path off the call expression it is iterating and never had this bug.

Install

npm install --save-dev agent-runtime-map

No registry access? The three CI-validated tarballs below install directly.

Upgrading

Nothing to change. v1 points at this release, so repositories using the GitHub Action pick it up on their next run.

Full diff: v0.9.0...v0.9.1