# shellcheck shell=bash # # tests-extras.sh โ€” tests 09, 10, 12, 13. # Focus: reactions/replies, concurrent commits, offline catchup, KP rotation. test_09_reply_react_unreact() { banner "Test 09 โ€” reply / react / unreact" local id="09 reply/react" local gid mls_gid gid=$(load_state GROUP_02 || true) mls_gid=$(load_state GROUP_02_MLS || true) if [[ -z "${gid:-}" ]]; then record_result "$id" skip "no GROUP_02"; return fi # B anchors. Needs a member to be present โ€” if Test 11 already ran and A left, # skip cleanly so we don't double-fail. if ! wn_b --json groups members "$mls_gid" 2>/dev/null \ | jq -e --arg p "$A_HEX" '(.result // .) | .[]? | select((.pubkey // .public_key) == $p)' \ >/dev/null 2>&1; then record_result "$id" skip "A already left GROUP_02"; return fi wn_b messages send "$mls_gid" "anchor for reactions" >/dev/null 2>&1 || true sleep 3 local msg_id msg_id=$(wn_b --json messages list "$mls_gid" --limit 10 2>/dev/null \ | jq -r '[(.result // .) | .[]? | select((.content // .text // "") == "anchor for reactions")][0].id // empty') if [[ -z "$msg_id" || "$msg_id" == "null" ]]; then record_result "$id" fail "couldn't find anchor message id"; return fi wn_b messages react "$mls_gid" "$msg_id" "๐ŸŒฎ" >/dev/null 2>&1 || true sleep 3 # amy reply amy_json marmot message send "$gid" "replying via amy" >/dev/null || { record_result "$id" fail "amy send reply failed"; return } if wait_for_message B "$mls_gid" "replying via amy" 90; then record_result "$id" pass else record_result "$id" fail "B didn't receive reply" fi # NB: react/unreact round-trip verification requires a CLI verb we don't have # yet (amy marmot message react). Once we add it, expand this test. } test_10_concurrent_commits() { banner "Test 10 โ€” Concurrent commits race" local id="10 concurrent commits" local gid mls_gid gid=$(load_state GROUP_02 || true) mls_gid=$(load_state GROUP_02_MLS || true) if [[ -z "${gid:-}" ]]; then record_result "$id" skip "no GROUP_02"; return fi if ! wn_b --json groups members "$mls_gid" 2>/dev/null \ | jq -e --arg p "$A_HEX" '(.result // .) | .[]? | select((.pubkey // .public_key) == $p)' \ >/dev/null 2>&1; then record_result "$id" skip "A already left GROUP_02"; return fi # Fire both renames in parallel. One wins โ€” MLS single-commit-per-epoch # guarantees a deterministic outcome. ( amy_json marmot group rename "$gid" "race-from-amethyst" >/dev/null ) & local a_pid=$! ( wn_b groups rename "$mls_gid" "race-from-wn" >/dev/null 2>&1 ) & local b_pid=$! wait "$a_pid" "$b_pid" 2>/dev/null || true sleep 10 local b_name b_name=$(wn_b --json groups show "$mls_gid" 2>/dev/null | jq -r '(.result // .) | .name // empty') local a_name a_name=$(amy_field '.name' marmot group show "$gid" 2>/dev/null || echo "") if [[ -n "$a_name" && "$a_name" == "$b_name" ]]; then info "race converged: both sides see \"$a_name\"" # Verify encryption still works. wn_b messages send "$mls_gid" "post-race ping" >/dev/null 2>&1 || true if amy_json marmot await message "$gid" --match "post-race ping" --timeout 90 >/dev/null; then record_result "$id" pass else record_result "$id" fail "encryption broken after race" fi else record_result "$id" fail "diverged: A sees \"$a_name\", B sees \"$b_name\"" fi } test_12_offline_catchup() { banner "Test 12 โ€” Offline catch-up" local id="12 offline catchup" # wn-side keys groups by mls_group_id; amy-side by nostr_group_id. Learn # the amy side from `amy await group` so later amy calls target the right # group. local out mls_gid a_out a_gid out=$(wn_b --json groups create "Interop-12" "$A_NPUB" 2>>"$LOG_FILE") mls_gid=$(printf '%s' "$out" | jq_group_id) [[ -n "$mls_gid" ]] || { record_result "$id" fail "couldn't create Interop-12"; return; } save_state GROUP_12_MLS "$mls_gid" # A joins. a_out=$(amy_json marmot await group --name "Interop-12" --timeout 30) || { record_result "$id" fail "A never received Interop-12 invite"; return } a_gid=$(printf '%s' "$a_out" | jq -r '.group_id') save_state GROUP_12 "$a_gid" # "Go offline" == don't invoke amy. Meanwhile B sends 5 messages + adds C + sends 3 more + rename. for i in 1 2 3 4 5; do wn_b messages send "$mls_gid" "offline-msg-$i" >/dev/null 2>&1 || true sleep 1 done wn_b groups add-members "$mls_gid" "$C_NPUB" >/dev/null 2>&1 || true wait_for_invite C 30 >/dev/null && wn_c groups accept "$mls_gid" >/dev/null 2>&1 || true for i in 6 7 8; do wn_b messages send "$mls_gid" "offline-msg-$i" >/dev/null 2>&1 || true sleep 1 done wn_b groups rename "$mls_gid" "Interop-12-renamed" >/dev/null 2>&1 || true sleep 3 # A comes back online โ€” single sync pulls everything. local show show=$(amy_json marmot group show "$a_gid") || { record_result "$id" fail "amy group show failed"; return } local name; name=$(printf '%s' "$show" | jq -r '.name') if [[ "$name" != "Interop-12-renamed" ]]; then record_result "$id" fail "A replay missed rename (saw \"$name\")"; return fi # All 8 messages should be locally stored. local msgs; msgs=$(amy_json marmot message list "$a_gid" --limit 100) local missing=0 for i in 1 2 3 4 5 6 7 8; do if ! printf '%s' "$msgs" | jq -e --arg t "offline-msg-$i" \ '.messages[]? | select((.content // "") == $t)' >/dev/null; then missing=$((missing+1)) info "missing offline-msg-$i" fi done if [[ "$missing" -eq 0 ]]; then record_result "$id" pass else record_result "$id" fail "A missed $missing of 8 offline messages" fi } test_13_keypackage_rotation() { banner "Test 13 โ€” KeyPackage rotation" local id="13 keypackage rotation" local before before=$(wn_b --json keys check "$A_NPUB" 2>/dev/null | jq -r '.result.event_id // empty') if [[ -z "$before" ]]; then record_result "$id" fail "no prior KP for A"; return fi amy_json marmot key-package publish >/dev/null || { record_result "$id" fail "amy key-package publish failed"; return } local deadline=$(( $(date +%s) + 60 )) after="" while [[ $(date +%s) -lt $deadline ]]; do after=$(wn_b --json keys check "$A_NPUB" 2>/dev/null | jq -r '.result.event_id // empty') [[ -n "$after" && "$after" != "$before" ]] && break sleep 3 done if [[ -n "$after" && "$after" != "$before" ]]; then info "KP rotated: ${before:0:8}โ€ฆ โ†’ ${after:0:8}โ€ฆ" record_result "$id" pass else record_result "$id" fail "no new KP event_id observed" fi } # -- Inverted-role tests ---------------------------------------------------- # Tests 01โ€“13 mostly exercise amethyst as the committer and wn as the # receiver. The scenarios below are complementary: wn drives the state # change and amy is the receiver that must accept, verify and apply it. # This widens coverage for the post-fix inbound authenticity checks # (membership_tag, FramedContentTBS signature, LeafNode lifetime, # confirmation_tag) that now run on every commit amy processes. test_14_wn_removes_a() { banner "Test 14 โ€” wn (admin) removes A; amy processes Remove" local id="14 wn removes amy" # Known gap: wn (mdk-core/openmls) emits the filtered direct-path # form of UpdatePath on Remove commits per RFC 9420 ยง7.7 โ€” when the # copath of a direct-path node has an empty resolution (every leaf # under it is blank) the corresponding UpdatePathNode is omitted. # Quartz's RatchetTree.applyUpdatePath currently requires the # unfiltered node count (`pathNodes.size == directPath.size`) so # every wn->amy Remove triggers # "UpdatePath node count (N) doesn't match direct path length (N+k)". # That's a pre-existing quartz conformance bug, out of scope for # this branch; the harness carries the test so it starts passing # the moment the filtered-path path is wired up. record_result "$id" skip "pending filtered_direct_path support in applyUpdatePath" } test_15_wn_member_leaves() { banner "Test 15 โ€” wn_c leaves; amy + wn_b process SelfRemove" local id="15 wn_c leaves" # Same filtered_direct_path gap as test 14: when wn_c leaves a # 3-member group, wn_b folds the SelfRemove into a commit whose # UpdatePath uses RFC 9420 ยง7.7 filtering, and amy's strict # applyUpdatePath rejects it. Skip until quartz handles the # filtered form on inbound. record_result "$id" skip "pending filtered_direct_path support in applyUpdatePath" } test_16_wn_keypackage_rotation() { banner "Test 16 โ€” wn rotates KeyPackage; amy discovers new KP" local id="16 wn keypackage rotation" # amy's KeyPackageFetcher.fetchKeyPackage calls client.fetchFirst, # which returns the first matching event a relay sends โ€” nostr-rs-relay # typically serves kind:443 events in storage order, not created_at # order, so after a rotation amy may keep seeing the older event_id # depending on which arrives first. Making this test deterministic # requires a "fetch latest by created_at" KeyPackage fetcher; until # then the check flaps. The inverse direction (test 13, amy rotates # and wn sees via `wn keys check` which is an addressable index) is # the reliable one. record_result "$id" skip "pending createdAt-sorted KeyPackage fetch path" }