ReSatoshi Wallet production release requirements

Current status: development-signed Android preview, not a store-ready release.
Source publication and production service/app publication are separate decisions.

Before a public wallet backend or production app release:
- Validate real incoming payments, two-phone QR signing, change recovery,
  encrypted backup restore, upgrades, background locking and device credentials.
- Establish an operator identity, private security contact and privacy contact.
- Decide actual Electrum/TLS/proxy/VPS logging, retention, deletion and hosting
  arrangements. Update PRIVACY.txt and resatoshi/privacy.json to match reality.
- Assess FIU reporting applicability using the actual service and revenue model;
  software licensing is not an exemption from financial regulation.
- Review distribution-country requirements and Google Play declarations/account.
- Audit final npm, Android Maven/NDK, font/image and other distribution licenses.
- Generate a dedicated production/upload key offline. Keep signing secrets out
  of Git, Gradle files, screenshots and issue reports. Never use the debug key
  for production. Decide test-to-production app identity and migration first;
  a different signing certificate can prevent an in-place preview upgrade.
- Prepare a signed AAB, Play App Signing and store assets. Do not upload the
  development-signed preview as a production artifact.
- Preserve copyright, license and modification notices. Separately check naming
  and trademark conflicts; an MIT license is not a trademark permission.
- Keep risk disclosures accurate; never promise finality, guaranteed safety,
  anonymity, returns or legal immunity.

The review does not authorize or assess coin fundraising, sales, exchange,
custody, investment advice, return guarantees or operation in every jurisdiction.
