Gateway test framework verification needed for UPDATE fire-and-forget semantics

[sanity]

Problem

UPDATE operations recently changed to fire-and-forget semantics (PR #2038), but haven't been tested end-to-end with River, which heavily uses UPDATE operations.

Unit tests (operations.rs, connectivity.rs) verify basic functionality, but don't catch real-world issues like:

• Multi-hop UPDATE propagation through actual network
• River room updates with multiple subscribers
• UPDATE behavior under network delays/failures
• Extended stability with continuous UPDATE load

Requested Testing

Run the gateway test framework with:

cd ~/code/freenet/freenet-testing-tools/gateway-testing
python gateway_test_framework.py --local --extended-stability --multi-room 50

This exercises:

• Real WebSocket connections
• Actual River room updates
• Multiple concurrent UPDATE operations
• Extended stability monitoring
• Full stack integration (gateway + peers + contracts)

Why This Matters

The fire-and-forget UPDATE semantics are a significant architectural change. Real-world testing would verify:

• River rooms stay synchronized
• UPDATE propagation doesn't stall
• No regressions in multi-room scenarios
• Performance under load

Related

PR #2038 - Refine fire-and-forget UPDATE semantics

[github-actions]

🤖 Auto-labeled

Applied labels:

• T-enhancement (95% confidence)
• E-medium (80% confidence)
• A-networking (90% confidence)
• A-developer-xp (90% confidence)

Reasoning: The report requests end-to-end verification and expanded testing of recently changed UPDATE fire-and-forget semantics rather than reporting a concrete runtime bug or requesting new functionality; this fits an enhancement (testing/validation) task. Running the gateway test framework with multi-room, extended-stability and real network conditions is moderately complex (requires environment setup and extended runs), so E-medium is appropriate. The work clearly involves networking concerns (multi-hop propagation, WebSocket connections, network delays) and developer/testing workflow (gateway test framework, integration tests), so A-networking and A-developer-xp are relevant.

Previous labels: T-enhancement

If these labels are incorrect, please update them. This helps improve the auto-labeling system.

[iduartgomez]

The tests for this are the ones in freenet-ping.