End-to-end test: clone -> commit -> push -> pull against two local nodes

[sanity]

Problem

We need an end-to-end test that exercises the full demo path against real (local) Freenet nodes.

What needs to happen

Following the same pattern as freenet-core's ping app integration tests:

1. Spin up two local nodes on unique loopback IPs.
2. On node A: init-identity, create a repo, push an initial commit through git-remote-freenet.
3. On node B: git clone freenet: against node B's WS endpoint; verify the working tree matches.
4. On node A: make a second commit, push.
5. On node B: git pull, verify the new commit is fetched.

Dependencies

• WS API publish (Wire up WS API publish in freenet-git create #1).
• git-remote-freenet helper (Implement git-remote-freenet helper binary #2).

Note for implementer

The 6-peer simulation tools and ping app integration test in freenet-core/crates/core/tests/ are the reference. Use the same test harness rather than rolling our own node-spawning code.

[AI-assisted - Claude]

[sanity]

Status check 2026-05-01: still relevant. Dependencies (#1, #2) are done as of 0.1.0/0.1.1.

Live demo against the production gateway has worked end-to-end (freenet-stdlib full history at freenet::2pyvKxrozxgT/freenet-stdlib, freenet-core HEAD source at freenet::AaRxPZVdWrPh/freenet-core), so we have evidence the protocol works on real hardware. A self-contained two-local-node test is still valuable for CI — production-gateway tests are flaky under load and not deterministic.

[AI-assisted - Claude]