chore: release 0.9.1

[TheCrazyAnt]

Patch release carrying the Python adapter fix from #61.

What ships

A route now reads the decorator call above its own declaration instead of the first matching call in the file, so a module with several same-method routes stops labeling all of them with the first one's path. documentedCapabilityLabel therefore matches on real paths again.

Version sites

All seven declarations the publish plan checks move together — the plan refuses a mismatch:

Site	0.9.0 → 0.9.1
package.json (root)	✅
packages/cli/package.json	✅
packages/react/package.json	✅
packages/mcp/package.json	✅
packages/cli/src/cli.ts VERSION	✅
packages/mcp/src/server.ts VERSION	✅
action.yml default cli-version	✅

package-lock.json regenerated with --package-lock-only.

Gate

npm run release:check passes locally: typecheck, 24 files / 213 tests, build, npm audit --audit-level=high, and the package checks —

Package check passed: agent-runtime-map-0.9.1.tgz, 652496 bytes, 33 files.
MCP package check passed: agent-runtime-map-mcp-0.9.1.tgz, 43519 bytes, 4 files.
Component package check passed: agent-runtime-map-react-0.9.1.tgz, 25915 bytes, 10 files.
Repository identity check passed: no retired slug in tracked files.
Version check passed: every declaration says 0.9.1.

Verified end to end by building a map with the bumped CLI: the emitted status.json carries "toolVersion": "0.9.1", so the constant reaches the artifacts and not just the manifest.

After merge

Per docs/RELEASING.md: tag v0.9.1 on the merge commit to trigger the OIDC publish, attach the three npm pack tarballs to the GitHub Release, then move v1 to the same commit (backward-compatible).

🤖 Generated with Claude Code