Manual test run Teamwork 1.2.0-alpha.20

Open a new issue and use the format of 'Manual test run' + app + version in the title.
Use the label of 'QA' for the new issue.
Update https://github.com/dxos/gravity/blob/main/docs/content/qa/index.md with a link to the new issue.
If any bugs are found, open new issues if they don't already exist. Add links into the test issue. Add a comment on the issue of the format "Feature: Name of feature : BROKEN"
Update https://github.com/dxos/gravity/blob/main/docs/content/qa/index.md with a list of broken features with links to the issues.
When a manual test is added to automation via playwright, remove it from the template.
Test using 2 machines with 2 different browsers (Brave / Chrome / Firefox are initial targets).
If that's not possible, use two different profiles of Chrome / Brave on a single machine.
Reset browser local storage between test runs.
Each daily run should be a comment in the testing tracking issue with the form below filled out.
Each person on the QA duty should attach at least one screen recording per week.

Not sure how I did it, but one user saw all messages and another one - only those posted by him. The same thing in other apps. I think this bug appeared after writing messages from invited device. Will try to reproduce it.

Feature: Inviting bot: BROKEN #485 (loading dialog appears for a while and then disappears) Tried with that configuration:

dxos-deprecated / teamwork