SecureBit.chat - P2P Encrypted Messenger Files

No changes to the protocol or to how messages are protected. This release tidies the documentation and fixes a version string.

Fixed

The version shown in the application header was written as a literal and had fallen behind, displaying v5.6.0 while running 5.7.1. It now comes from package.json, so it cannot drift again, and a test fails the build if anyone reintroduces a hard-coded one. The same test checks that meta.json, the README badge, the changelog and the documentation all agree before a release goes out.

Documentation

Everything technical now lives in doc/ with an index at doc/README.md. The repository root keeps only what belongs there by convention: README.md, SECURITY.md, CHANGELOG.md and LICENSE.

• SECURITY.md rewritten. It described a supported release line three major versions out of date and made claims the software does not make. It now states what is guaranteed, what is not, and how to report a problem.
• SECURITY_DISCLAIMER.md and RESPONSIBLE_USE.md merged into doc/USE-POLICY.md, which says plainly what the software cannot protect against instead of listing generic advice.
• doc/ARCHITECTURE.md (formerly SECURITY-ARCHITECTURE.md) rewritten around the session lifecycle, what verification gates, and how recovery works.
• doc/CRYPTOGRAPHY.md rewritten: key schedule, the Double Ratchet, frame format and memory handling, with every value taken from the source.
• doc/CONFIGURATION.md rewritten with the real file-type policy, ICE and TURN guidance, and the deployment caching rules that actually matter.
• Call tuning notes moved to doc/CALLS.md and rewritten. The obsolete docs/ directory has been removed.
• doc/CONTRIBUTING.md records what recent regressions taught us about writing tests that can actually fail.

Full changelog: https://github.com/SecureBitChat/securebit-chat/blob/main/CHANGELOG.md