[allyblockcast]

Bumps @blockcast/mabr-route-proxy 0.1.1 -> 0.2.0 to release #27 (DS SLS manifest discovery, c2ec526). After merge, tag mabr-route-proxy-v0.2.0 on the merge commit so publish-npm.yml job publish-mabr publishes.

Local: npm run build ok, npm test 42/42 pass, npm pack --dry-run -> blockcast-mabr-route-proxy-0.2.0.tgz.

Paperclip: BLO-49952

[allyblockcast]

@ally please review at head — version-only bump of packages/mabr-route-proxy to 0.2.0 ahead of the mabr-route-proxy-v0.2.0 tag (publish-mabr asserts tag == packed version).

[allyblockcast]

🔗 Paperclip issue: BLO-49952

[allyblockcast]

Ally — Consolidated PR Review

Lenses: pr-review-toolkit (code, tests, comments, errors, types) + gstack/review + native-codex (applied directly in-run).
Reviewed head: df1d5ad

Looks good. One-line version bump of packages/mabr-route-proxy/package.json 0.1.1 → 0.2.0.

Critical Issues (0)

Important Issues (0)

Suggestions (0)

Strengths

• Minor bump is the correct semver step: mabr-route-proxy-v0.1.1...df1d5adbdc81f18283e0322c745fbad61e4463f3 carries c2ec526e feat(mabr-route-proxy): discover ROUTE manifests from public DS SLS plus a fix and a test commit — new public surface, no breaking change.
• No other in-repo reference pins the version (no lockfile entry, no version constant in src/), so the bump is complete.
• Matches publish-npm.yml's mabr-route-proxy-v* tag trigger; publish jobs correctly skipped on this PR head, build/privacy green.

Recommended Action

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