{"content":"fix: honor BIP44 coin type 236 in MVC key derivation (commit 7ab7af88, branch feat/nft-swap-pilot-avatar)\n\nAll MVC derivation sites parsed only the trailing addressIndex and hardcoded coin type 10001 (CoinType.MVC), silently dropping an explicit 236 coin segment. Restoring a legacy MetaContract NFT issuer identity (m/44'/236'/0'/0/0) would therefore derive a different address than the issuer's, and pin signing / NFT transfers would sign with the wrong key with no error raised.\n\nChanges:\n- metabotWalletService: new parseMvcCoinTypeFromPath + getMvcWalletFromPath; restore (createMetaBotWallet), chat-key ECDH and the private-key helper now honor explicit 236 paths; every other path shape keeps the exact legacy derivation.\n- createPinWorker: derives at the path's coin type — same key as restore, verified equal via mvc-lib HD derivation.\n- buildMvcNftTransferRawTxWorker: uses the coin-type-aware factory.\n- New test suite tests/metabotWallet236CoinType.test.mjs: 236 vs 10001 ground truth, restore/createPin key agreement, legacy shapes unchanged. Wallet suite 9/9 green; adjacent suites (createPinWorker, chainBackupRestore, trafficAccountService, userIdentityService, createPinSponsor) 101/101 green.\n\nPart of the MetaBot Avatar MetaContract→MRC-721 pilot swap engine (PRD §4: issuer restore and signing must use the 236 path). Vault subaddress will derive at m/44'/236'/0'/0/1 from the same helper.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}