Create comprehensive Rust SDK implementation guidelines document

[Copilot]

Summary

Created detailed implementation guidelines for the Rust SDK for Solana AI Registries in docs/RUST_SDK_IMPLEMENTATION_GUIDELINES.md. This comprehensive document provides actionable requirements derived from the reference documentation to guide developers through the complete SDK implementation.

Changes Made

• Added docs/RUST_SDK_IMPLEMENTATION_GUIDELINES.md - 563-line comprehensive guide containing:
  • 12 atomic implementation tasks with detailed requirements
  • Feature gates and payment mode flags documentation
  • CI/CD publishing workflow requirements
  • Code style and review standards
  • Complete reference links to IDLs, constants, and artifacts

Document Structure

Atomic Implementation Tasks (12 tasks)

Each task includes requirements, acceptance criteria, implementation checklists, and references:

1. Core Library (lib.rs) - Exports, feature gates, compilation requirements
2. Agent Registry Module - CRUD operations, type builders, validation
3. MCP Server Registry Module - Server builders, tool/resource definitions
4. Payment Modules - Three payment flows (prepay, pyg, stream)
5. RPC Client Wrapper - Solana client abstraction, error handling
6. Error Handling - On-chain error mapping, comprehensive coverage
7. IDL Integration - Compile-time inclusion, hash verification
8. Agent Flow Tests - 26 test cases covering all operations
9. Payment Tests - Balance verification, compute unit budgets
10. Snapshot Testing - Ledger state validation
11. Feature Flag Implementation - Conditional compilation
12. Publishing Workflow - Security gates, MSRV compliance

Key Features

• 100+ actionable checklist items across all implementation tasks
• Feature flag documentation with usage examples for stream, pyg, prepay
• CI/CD workflow requirements including build matrix and publishing gates
• Code style standards following Rust API Guidelines
• 18 code examples demonstrating proper usage patterns
• Complete cross-references to existing codebase and external documentation

Example Implementation Guidance

/// Registers a new agent in the registry.
///
/// # Arguments
/// * `client` - The Solana RPC client
/// * `signer` - The account that will own the agent
/// * `agent` - Agent configuration built with AgentBuilder
///
/// # Returns
/// * `Ok(Signature)` - Transaction signature on success
/// * `Err(SdkError)` - Detailed error information
///
/// # Example
/// ```rust
/// let client = SolanaAiRegistriesClient::new("https://api.devnet.solana.com");
/// let agent = AgentBuilder::new("my-agent", "My AI Agent")
///     .description("An AI agent that helps users")
///     .build()?;
/// 
/// let signature = client.register_agent(&keypair, agent).await?;
/// ```
pub async fn register_agent(
    client: &SolanaAiRegistriesClient,
    signer: &dyn Signer,
    agent: AgentArgs,
) -> SdkResult<Signature> {
    // Implementation follows guidelines
}

The document serves as the definitive guide for implementing the Rust SDK according to the atomic execution plan specifications, ensuring consistency, quality, and maintainability across all components.

Fixes #38.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[sourcery-ai]

🧙 Sourcery is reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[netlify]

✅ Deploy Preview for aeamcp canceled.

Name	Link
🔨 Latest commit	902505d
🔍 Latest deploy log	https://app.netlify.com/projects/aeamcp/deploys/686babab02767800086641f9

[devloai]

PR Summary:

This is a Work-In-Progress (WIP) PR intended to create detailed implementation guidelines for the Rust SDK. Currently, the PR contains no file changes and serves as a placeholder for the deliverable described in issue #38.

Review Summary:

The PR is appropriately empty since it's explicitly marked as WIP and the author stated they're "starting to work on it." No code changes exist to review for bugs, security issues, or code quality concerns. I utilized repository knowledge about the existing Rust SDK structure and reference documentation to understand the intended scope. Please provide feedback on this review approach for future evaluations of WIP PRs.

Follow-up suggestions:

• @devloai help create the implementation guidelines document once the author adds content to review
• @devloai review the actual implementation guidelines when they're added to the PR