Clear three advisories, take sdk 2.7.3, release 0.4.9

[vvillait88]

Summary

Three advisories were reachable in the lockfile, each with a fixed version already published: brace-expansion (two High, one per locked copy) and postcss. None had been taken because bun does not re-resolve a locked version that still satisfies its range, so a routine refresh could never reach them. A clean re-lock takes all three.

The brace-expansion allowlist entry is deleted rather than waived. It said the 1.x line had no fixed release, which was true when written; upstream has since backported to 1.1.17 and then 1.1.18, so minimatch@3's own ^1.1.7 range reaches the fix with no override and none of the API breakage that made forcing 5.x impossible. osv-scanner now reports it as an unused ignore.

Nothing coupled moved. incur is already at its latest release (0.4.26), so the exact pin and patches/incur@0.4.26.patch stay together and the patch cannot silently detach. viem 2.55.10, mppx 0.8.15, @solana/mpp 0.7.0 and @solana/kit 7 are all unchanged, so there is no coupled-set bump here and no live all-rails settle obligation. @agent-score/sdk picks up 2.7.3, which the bunfig exempts from the release-age soak so a first-party publish reaches its consumer immediately.

Type of change

• Bug fix (no breaking change)
• New feature (no breaking change)
• Breaking change (existing callers must update)
• Docs, tests, or internal maintenance only

Public API

None. No command, flag, output envelope or MCP tool surface changed. The MCP handshake still advertises the same four progressive-discovery tools (search_tools, get_tool_details, call_read_tool, call_write_tool).

Test plan

Run from a clean install (rm -rf node_modules bun.lock && bun install):

• bun run lint, bun run typecheck, bun run knip all exit 0
• bun run test: 570 passed, 2 skipped
• osv-scanner v2.4.0 over bun.lock: no issues found

Because the compiled binary is what the incur patch exists to fix, and the node dist can pass while the binary cannot resolve the transport, the smokes were run against the binary, and rebuilt after the version bump so the evidence matches what ships:

• --version reports 0.4.9, not 0.0.0-dev, so the build-binary.mjs version injection is intact
• whoami --format yaml renders, so incur's createRequire-based lazy yaml load resolves inside the binary
• MCP initialize + tools/list handshake returns serverInfo 0.4.9 and all four tools, so the stdio transport resolves through the patch's literal specifiers

The patch was also confirmed applied to the installed tree by reading the rewritten dist/Mcp.js, rather than trusting that the patchedDependencies entry was still wired.

Checklist

• Tests cover the new behavior, and the suite passes locally
• Lint, format, and type checks pass
• Docs and README examples updated if the public surface changed
• No secrets, credentials, or personal data in the diff or the tests