feat: implement bounty CRUD, batch operations, and MCP server for Claude Code ( Issue #844)

[Tusharkhadde]

Feature: Bounty Management CLI & Claude Code Skill (MCP)

This PR expands the SolFoundry CLI with full bounty lifecycle management (CRUD), batch operations, and a native Claude Code skill via the Model Context Protocol (MCP). It also resolves critical environment issues and property-mapping bugs found in the existing CLI codebase. #844

🛠️ Key Improvements & Bug Fixes

• Dependency Resolution: Fixed missing tsx and correctly linked the local @solfoundry/sdk to resolve "module not found" errors during development.
• Fixed Property Mapping: Corrected bugs in profile and status commands where incorrect SDK properties (e.g., total_earnings instead of total_earned) were being accessed.
• Type Safety: Fixed TypeScript compilation errors related to private constructors and type casting that prevented the CLI from building.

🚀 New CLI Commands

• Bounty CRUD: Added full support for create, update, and delete commands directly from the terminal.
• Batch Creation: Implemented a batch create <file.json> command for bulk bounty deployment.
• Example Config: Included batch-example.json as a template for batch operations.

🤖 Claude Code Skill (MCP)

• MCP Server Integration: Implemented a JSON-RPC 2.0 server using @modelcontextprotocol/sdk.
• Exposed Tools: list_bounties, get_bounty, create_bounty, and update_bounty are now available natively to Claude Code and other AI agents.

✅ Verification Results

• All 51 unit tests in sdk/cli are passing.
• Verified CLI help menus and command registration.
• Successfully built both sdk and cli packages.

Wallet - JDkFAXAaysAradjqQkCtpu2seJZR43F9qrfHZvgPYfvL

[nagiexplorer88]

The CLI package is now only installable from inside this monorepo. sdk/cli/package.json changes @solfoundry/sdk from the published peer dependency to:

"@solfoundry/sdk": "file:.."

That works for local development, but a user installing @solfoundry/cli from npm or via npx will not have the parent .. SDK package available in their install context. The resulting CLI package depends on a local filesystem path instead of a resolvable published dependency, which breaks the "Claude Code skill / CLI for developers" part of #844 outside the repo.

This should either keep @solfoundry/sdk as a peer/normal published dependency or package the CLI through the workspace publish flow without a file:.. dependency in the published manifest.

[Tusharkhadde]

Fixed @solfoundry/cli packaging so npm/npx installs work outside the monorepo.

Replaced local/workspace-style SDK linkage with published dependency in sdk/cli/package.json: @solfoundry/sdk: ^0.1.0
Updated sdk/cli/package-lock.json to match the manifest
This removes reliance on repo-local .. SDK resolution for external consumers
Commit: 1208475

[nagiexplorer88]

Confirmed for the packaging issue I reported. The current sdk/cli/package.json now declares "@solfoundry/sdk": "^0.1.0" under regular dependencies and no longer relies on the repo-local "file:.." / peer-only setup, so an external npm/npx install should be able to resolve the SDK package instead of requiring the parent monorepo checkout.

[Tusharkhadde]

Thank you for confirming the fix and validating the packaging behavior.
Could you please proceed with the bounty payout amount for this issue?
Also, do you pay only in FNDRY token, or can I share a USDC wallet address for payout?

[nagiexplorer88]

Thanks. I reviewed the code path only, so I can't confirm payout amount, timing, currency, or wallet/payment details.

Please coordinate the bounty payout with the SolFoundry maintainers or the official bounty/payment flow.

[Tusharkhadde]

Thanks. Who should I contact regarding the payout workflow and reward details?

[nagiexplorer88]

I don't have a private payout contact or payout authority here.

The original bounty issue #844 was opened by @mtarcure, who appears as a SolFoundry repository collaborator on that issue. Please ask @mtarcure or another SolFoundry maintainer in the official PR/issue thread for the payout workflow and reward details, and use the official SolFoundry bounty/payment flow before sharing any wallet or payment details.

[Tusharkhadde]

Thank you for the clarification. I'll follow up with @mtarcure and the SolFoundry maintainers in the official thread regarding the payout workflow and reward details.

Could you also confirm whether, after the PR is merged, I will be eligible to receive the bounty reward for this issue, and whether the issue has been accepted/validated for bounty consideration?

[nagiexplorer88]

To avoid confusion: I can only confirm the specific packaging issue I reviewed was addressed. I cannot confirm bounty eligibility, acceptance, reward amount, merge outcome, payout timing, or payout method. Please rely on @mtarcure / SolFoundry maintainers and the official SolFoundry bounty/payment flow for those decisions.