Cleanup stale claude-context bins from published SDK deps

[willgriffin]

Summary

Downstream installs are still emitting noisy ENOENT warnings from published SDK packages that advertise claude-context.js bins even though those files are no longer present.

This is not blocking the current Praeco/Anytown release, but it is leftover ecosystem cleanup and it makes fresh installs look broken.

Repro

In a downstream app consuming the current SMRT releases:

pnpm install

Observed warnings include:

WARN Failed to create bin .../@happyvertical/weather/dist/cli/claude-context.js
WARN Failed to create bin .../@happyvertical/encryption/dist/cli/claude-context.js

The warnings fan out through dependents as well, so a single install can print many copies.

What seems wrong

Published package metadata for these SDK packages still points bin entries at removed claude-context.js files.

From the downstream install logs, the affected published packages were:

• @happyvertical/weather@0.71.19
• @happyvertical/encryption@0.71.12

Expected

• installs should complete without stale bin warnings
• if the Claude-specific helper bins were intentionally removed, package metadata should stop advertising them
• if replacement bins are intended, they should point at real files in the published tarballs

Notes

This came up while verifying the Anytown Praeco release branch on smrt v0.21.37. The branch itself is healthy; this is follow-up cleanup so downstream installs stay quiet and trustworthy.