[kkroo]

Bumps @blockcast/mabr-route-proxy 0.2.0 -> 0.2.1 to release #30 (route cache hit and miss telemetry, BLO-49953) and #29 (resolve DS URLs against the DS root, scope the cache to the manifest). After merge, tag mabr-route-proxy-v0.2.1 on the merge commit so publish-npm.yml job publish-mabr publishes.

Local: npm run build ok, npm test 53/53 pass, npm pack --dry-run -> blockcast-mabr-route-proxy-0.2.1.tgz (8 files).

Paperclip: BLO-49945

[kkroo]

@ally please review at head c9dc35a: version bump only, @blockcast/mabr-route-proxy 0.2.0 -> 0.2.1, to release #29 and #30.

[allyblockcast]

🔗 Paperclip issue: BLO-49945
🔗 Paperclip issue: BLO-49953

[allyblockcast]

Ally — Consolidated PR Review

Lenses: pr-review-toolkit (code, tests, comments, errors, types) + gstack/review + native-codex (nested CLIs unavailable in the k8s pod; applied directly to the diff).
Reviewed head: c9dc35a

Looks good. One-line version bump of @blockcast/mabr-route-proxy 0.2.0 → 0.2.1 in packages/mabr-route-proxy/package.json:3; branch is 1 ahead / 0 behind main, so it releases exactly #29 and #30 as described.

Critical Issues (0)

Important Issues (0)

Suggestions (0)

Strengths

• No lockfile or in-source version constant under packages/mabr-route-proxy to drift out of sync with the bump.
• publish-npm.yml job publish-mabr asserts the packed tarball version equals the mabr-route-proxy-v* tag before publishing, so a mistyped post-merge tag fails closed rather than publishing the wrong version.

Recommended Action

1. No blocking changes requested.
2. Merge once the remaining required CI checks finish green.