fix(agents-mcp): include bin/ in published npm package

[rock2089]

Problem

The @inkeep/agents-mcp package declares bin entries pointing to bin/mcp-server.js but the published tarball omits this file.

Root Cause

packages/agents-mcp/.gitignore excludes /bin. The package.json lacks a files field, so npm uses .gitignore during publish.

Fix

Added files field ["esm/", "bin/"] to explicitly include these directories.

Closes charles-openclaw/charles-microbounties#585

[changeset-bot]

⚠️ No Changeset found

Latest commit: eb7f580

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Thanks for the contribution! Your PR has been mirrored into Inkeep's internal monorepo, where review and merge happen. Your commit attribution is preserved as @rock2089.

What happens next:

• An Inkeep maintainer will review the internal mirror PR.
• Reviewer comments are not automatically mirrored back to this thread. If you don't hear from us within a few business days, please comment here to nudge — that's the right thing to do.
• Once merged internally, the change will sync back to this repository and this PR will close automatically (don't be alarmed when it closes — that's how it lands).

For Inkeep maintainers (link goes to a private repo and is not accessible to external contributors): https://github.com/inkeep/agents-private/pull/1700

See the repository's CONTRIBUTING.md for more context on how public PRs flow. This comment will be updated as the bridge state changes.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity.
It will be closed in 7 days if no further activity occurs.

If this PR is still relevant:

• Rebase it on the latest main branch
• Add a comment explaining its current status
• Request a review if it's ready

Thank you for your contributions!