[xss3cut10n3r]

Why

Group chats were built behind a build switch that was off by default. This turns them on and sets the version for the release that carries them.

What changed

• Group chats are on by default. --dart-define=FIREPLACE_GROUPS=false still builds the app without them.
• Version 0.4.0 (0.4.0+000400).
• The encryption core is the published fireplace-crypto 0.2.0, pinned exactly, instead of a commit of its repository.
• Decision 0050 records how the owner settled each condition it listed for release:
  • Shipping on OpenMLS 0.9.2, which still uses provisional cipher-suite identifiers. Groups made now may need to be made again when a release with the final identifiers is adopted; that will be a visible step.
  • The dependency is approved, including the MPL-2.0 licence of hpke-rs.
  • Not waiting for an independent review at the present number of users.

No screen changes, so no previews.

What people will notice

• Someone on an older version cannot be invited to a group until they update and open the app once. The contact picker says so.
• On iPhone, a group notification shows a generic alert.

How it was checked

• scripts/check.sh passes on this branch, built against the published 0.2.0 crate.
• CLA.
• Not done: an iOS build. The group code has not been compiled for iPhone, and its size and memory use are not measured. The iOS workflow is run by the owner.
• Not done: a test on real devices with two accounts (create, invite, accept, send both ways, leave).

AI assistance

Claude Code made this change, directed by the owner, who made the release decisions recorded in decision 0050.

Privacy and safety

• No new data leaves the device or is stored on the server beyond what decision 0050 describes for group chats.
• No secrets, keys or real user data in the diff.

🤖 Generated with Claude Code