Bundle simplex-chat v7.0.0, adopt ExVer numbering (7.0.0:0)

[lundog]

Bumps the image to lundog/simplex-websocket-bridge:7.0.0 (simplex-chat v6.5.6 → v7.0.0), fixes the one thing the bump broke, and brings the version scheme and version graph in line with the packaging guide.

Relay switching fix

v7.0.0 added a roles field to every entry in the userServers structure. applyProtocol round-trips the structure it reads, so rows it mutates carried the new field through — but rows it constructs for a newly added custom server did not, and the SET failed to parse:

Bot refused server configuration: {"type":"chatCmdError","chatError":{"type":"error",
"errorType":{"type":"commandError","message":"Failed reading: empty"}}}

Constructed rows now include roles: {}, matching what every row the client returns carries; effective roles live on the operator (smpRoles/xftpRoles).

Versioning: 0.3.0:5 → 7.0.0:0

ExVer's upstream component is the upstream project's version, and the packaging guide's consistency checklist requires it to match the image tag. This package had been using 0.x as a wrapper-maturity number while the image said 6.5.x, so the two never agreed.

Renumbering makes the version state which client is bundled, and future wrapper-only changes roll the downstream revision (7.0.0:1, :2). The jump is monotonic, so existing installs still see it as an update, and openclaw-startos's >=0.3.0:0 dependency range is unaffected. The release notes explain the jump so it doesn't read as a different package.

Happy to revert this half if you'd rather keep wrapper-versioning — it's independent of the image bump.

Version graph: other: []

Dropped versions/v0_2_0.ts. Per the guide, a version earns a node only when it has its own migration to run in sequence; v0_2_0's up was empty, so it bought no behavior and cost a file that had to be kept compiling. Empty other also yields the widest canMigrateFrom.

Downgrades

down stays IMPOSSIBLE. simplex-chat migrates its database in place on first 7.0.0 start, and 6.5.6 will not start against a migrated database — verified, not inferred. simplex-chat leaves simplex_v1_*.db.bak snapshots beside the live files, but restoring them discards everything since the upgrade and relies on an upstream convention this package doesn't control, so it stays documented rather than automated. (The guide is also explicit that migrations aren't for data the upstream service migrates itself.)

Docs

• README: updates are one-way when simplex-chat migrates; back up first; what the .db.bak files are and what restoring them costs.
• README: a consumer keeps a stale mount after this package is uninstalled and reinstalled — the volume directory is replaced and the consumer's mount stays pinned to the old inode, so file exchange looks silently empty while the bridge writes normally. Restarting the consumer fixes it; a normal update is unaffected. Found while testing, after an uninstall/reinstall cycle left OpenClaw seeing an empty files dir.

Testing

On StartOS 0.4.0, against the 7.0.0 image:

• Create Invitation — connected a contact using the returned link
• View Address / Reset Address
• Configure Client — including a switch to a self-hosted SimpleX Server and back (the path this PR fixes)
• File exchange — send and receive through OpenClaw
• tsc --noEmit clean, prettier clean, ncc build succeeds