What problem does it solve? Solana developers face uncertainty when deciding between @solana/web3.js (v1) and @solana/kit, and migrating existing codebases involves breaking API changes, async keypair handling, BigInt conversions, and Anchor incompatibility risks. ## Core Features & Use Cases - Migration Analysis: Scans a codebase with shell and Node scripts to count v1 patterns (Connection, Keypair, PublicKey, Transaction) and classify migration complexity as low, medium, or high. - API Mapping Reference: Provides side-by-side v1-to-Kit conversions for RPC calls, keypairs, transactions, subscriptions, and program instructions. - Edge Case Handling: Documents gotchas like BigInt JSON serialization, missing .send() calls, async keypair generation, and hybrid Anchor setups using @solana/compat. - Use Case: A developer with an existing Solana dApp runs the analyzer, discovers 120 migration points and an Anchor dependency, and receives a recommendation to use a hybrid approach with @solana/compat instead of a full rewrite. ## Quick Start Analyze my Solana project and tell me whether I should migrate from @solana/web3.js to @solana/kit.