Address PR review comments: type safety, error sanitization, and testing

[Copilot]

Addresses all review comments from PR #71 on the WASM bridge implementation.

Type Safety

• Fix UpdateRecord → UpdateMultipleRecord in update_multiple signature
• Fix u32 → u64 for max_records parameter to match bridge type definitions
• Update default API version from 62.0 to 65.0 across codebase

Security & Memory

• Use Arc<str> instead of String for access_token and instance_url fields to reduce credential duplication in memory
• Sanitize error codes before returning to WASM guests—map internal error types to stable codes (AUTH_ERROR, HTTP_500, RATE_LIMITED) instead of exposing Debug format

// Before: leaked internal type structure
Err(e) => BridgeResult::err(format!("{:?}", e.kind), e.to_string())

// After: stable error codes
Err(e) => {
    let (code, message) = sanitize_rest_error(&e);
    BridgeResult::err(code, message)
}

Documentation & Testing

• Add integration tests for sf-bridge (module loading, WASM validation)
• Document testing strategy for sf-guest-sdk at module level—unit tests require Extism runtime, tested via integration and examples
• Clarify SOQL injection prevention is guest responsibility; host validates structured inputs (IDs, field names)

---

💡 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.