SDK drift: hosted signer class named `EthersSigner` in TypeScript but `EthAccountSigner` in Python

[realfishsam]

What

The concrete signer implementation has different names and different export visibility across SDKs.

SDK	File	Line	Class name	Exported from main entry?
TypeScript	sdks/typescript/pmxt/signers.ts	47	EthersSigner	accessible via sdks/typescript/pmxt/signers.ts
Python	sdks/python/pmxt/signers.py	38	EthAccountSigner	NOT exported from sdks/python/pmxt/__init__.py

After camelCase/snake_case normalization: EthersSigner does not map to EthAccountSigner. These are structurally different names referring to different underlying libraries (ethers.js vs eth-account).

Impact

Documentation and user code that references EthersSigner (TypeScript) has no directly corresponding symbol to use in Python. Python users who need to construct a signer explicitly must know to use EthAccountSigner from the non-public pmxt.signers submodule, since it is not re-exported from pmxt.__init__.