feat: migrate test infrastructure to xnet

[neekolas]

Summary

Replace the docker-compose-managed XMTP node (node-go + validation + databases) with xnet-cli for test infrastructure. This simplifies the setup significantly and adds advanced integration test scenarios.

• xnet.toml configures the XMTP network (xmtpd, gateway, node-go, validation images)
• docker-compose.yml simplified to 3 services: db, notification_server, integration — all on the external xnet Docker network
• dev/up starts xnet with --paused, adds a migrator node, starts the notification DB
• dev/integration accepts v3-writes or v4-writes scenario, dynamically resolves CoreDNS IP for container DNS
• gatewayUrl support for V4-writes scenario (client publishes directly to V4 gateway)
• 3 new integration tests: selective unsubscribe, group message sender filtering, unregister stops notifications
• waitForNotification filters by installationId to prevent cross-test interference
• CI uses Nix + Cachix to install xnet-cli via a reusable setup-xnet composite action

Design: docs/plans/2026-04-04-xnet-integration-design.md

Test plan

• go test -p 1 ./... passes with xnet providing XMTP nodes
• ./dev/integration v3-writes — all 5 integration tests pass
• ./dev/integration v4-writes — all 5 integration tests pass (requires d14n activation)
• shellcheck dev/up dev/down dev/integration — no errors

🤖 Generated with Claude Code

Note

Migrate test infrastructure to xnet for integration testing

• Replaces the static docker-compose v3 node with an xnet-based environment, provisioned via new dev scripts (dev/up, dev/down, dev/xnet, dev/xnet-env) and a pinned xnet-cli installed via Nix (dev/install-xnet).
• Adds a CI matrix in test.yml to run integration tests against v3-direct and v4-with-migrator message sources using the new setup-xnet composite action.
• Adds a /readyz endpoint to ApiServer that returns 200/503 based on listener stream readiness; both v3 and v4 listeners now expose a Ready() method tied to active stream state.
• Integration tests are reworked to wait for per-installation notifications and cover new behaviors: selective unsubscribe, group message sender filtering, and unregister.
• Behavioral Change: docker-compose no longer includes a v3 node service; the notification server now depends on an external xnet Docker network and exposes /readyz for healthchecks.

^{Macroscope summarized 1620534.}

[neekolas]

• ci: add concurrency limits to all workflows #100
• feat: migrate test infrastructure to xnet #98 👈 (View in Graphite)
• feat: add V4 d14n listener with payload format support #96
• refactor: replace local upstream protos with xmtpd imports #97
• feat: migrate to V4 binary topic format #94
• refactor: centralize test utilities and standardize test patterns #99
• chore: upgrade Go from 1.25 to 1.26 #93
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[macroscopeapp]

Approvability

Verdict: Needs human review

1 blocking correctness issue found. While primarily test infrastructure changes, this PR introduces runtime modifications including a new /readyz endpoint and listener Ready() methods. An unresolved review comment identifies a potential data race in the readyCheck field that should be addressed before merging.

No code changes detected at 1620534. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}

Dismissing prior approval to re-evaluate d6d09c2

[neekolas]

Merge activity

• Apr 8, 5:03 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Apr 8, 5:10 PM UTC: Graphite rebased this pull request as part of a merge.
• Apr 8, 5:11 PM UTC: @neekolas merged this pull request with Graphite.