You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Directly added, verified group members discover the room after sync without requesting a `wire-group:` join code.
6
+
7
+
## Change
8
+
9
+
-`wire group list` now runs the existing verified-invite intake when identity state exists.
10
+
- Intake accepts a direct invite only when the event targets and the signed roster includes the local identity.
11
+
- The group integration test proves pull → list materializes the direct invite before any send or tail call.
12
+
13
+
## Scope and assumptions
14
+
15
+
- Reused the existing creator-signed roster validation, trust pinning, and group persistence paths.
16
+
- Kept join codes as the admission path for unpaired/link recipients.
17
+
- Did not change daemon behavior, group credentials, trust tiers, or invite consent semantics.
18
+
19
+
## Evidence
20
+
21
+
- Regression reproduced: `cargo test --test e2e_group group_bidirectional_room_with_introduce_pin -- --nocapture` failed before the code fix because the recipient listed zero groups after pull.
22
+
- Focused verification passed: `cargo fmt --check`, `cargo test --test e2e_group -- --nocapture`, and `cargo test --test cli group_list_empty_reports_no_groups -- --nocapture`.
23
+
- Full verification passed: `cargo test -q`.
24
+
- GitNexus impact: `cmd_group_list` had one direct caller / LOW risk; shared `ingest_group_invites` was HIGH risk due to `send` and `tail` callers, so its validation logic was unchanged.
25
+
- Independent review found that automatic listing would otherwise persist a valid roster for an excluded recipient; added recipient and roster-membership gates plus e2e wrong-recipient and excluded-recipient regressions.
A verified peer added directly to a group sees that group after sync without requesting a `wire-group:` code.
6
+
7
+
## Scope
8
+
9
+
- Run existing verified-invite intake before `wire group list`.
10
+
- Materialize only an invite addressed to, and whose signed roster includes, the local identity.
11
+
- Cover the creator-adds-member, recipient-pulls, recipient-lists path in the group integration test.
12
+
- Preserve code-based joins for link-style, unpaired admission.
13
+
14
+
## Non-goals
15
+
16
+
- No change to group signatures, trust tiers, relay credentials, or daemon behavior.
17
+
- No new consent or pending-invite model.
18
+
19
+
## Verification
20
+
21
+
The integration test must prove that a recipient can list a directly added group after pulling its signed invite, before sending or tailing a group message.
0 commit comments