# Textunnel physical acceptance summary

Reviewed: 2026-10-18
Maintainer-authored summary of repository acceptance modules 67 and 68.
Canonical explanation: https://textunnel.com/transfer-guide#tested-behavior

These are functional acceptance observations from the October 18, 2026 test record, not speed benchmarks or proof for every browser, VPN or router. Desktop reads were deliberately slowed for interruption tests. In-flight refresh recovery, iOS process eviction and physical Android/Windows coverage remain unverified.

Exact browser and OS versions were not recorded.

| Date | Devices | Route / conditions | Size | Outcome | Detail |
| --- | --- | --- | --- | --- | --- |
| 2026-10-18 | iPhone Safari ↔ Mac browser | Same Wi-Fi, native WebRTC; at least one VPN enabled | 1 MiB / 64 MiB | Passed | Saved and returned; SHA-256 matched. 64 MiB rejection reached sender. |
| 2026-10-18 | iPhone Safari ↔ Mac browser | WebRTC, lock screen / background | 64 MiB | Interrupted; recovery passed | Uninterrupted transfer failed. Return to Safari, reconnect and manual sender Retry resumed retained prefixes; return hashes matched. |
| 2026-10-18 | iPhone Safari ↔ Mac browser | WebRTC after ~20 seconds without Wi-Fi or cellular | 64 MiB | Recovery passed | After restoring network, reconnect and sender Retry resumed retained data; return hash matched. |
| 2026-10-18 | iPhone Safari ↔ Mac browser, both real cameras | Offline Offer/Answer QR; host ↔ host; desktop online signaling blocked | 1 MiB | Passed | Saved and returned with matching hash. Site was loaded first; not an uncached offline first visit. |

## iPhone Safari ↔ Mac on the same Wi-Fi, at least one VPN enabled

1 MiB and 64 MiB saved and returned over WebRTC; returned SHA-256 matched the source. A 64 MiB rejection also reached the sender correctly.

## iPhone lock screen and background

Uninterrupted transfer did not pass. Returning to Safari reconnected; manual sender Retry resumed verified prefixes, and complete 64 MiB return hashes matched.

## Physical network interruption

After Wi-Fi and cellular were disabled for about 20 seconds and restored, reconnection plus manual Retry resumed a retained prefix; the full 64 MiB return hash matched.

## Offline QR connection

Both real cameras exchanged Offer/Answer QR codes. With desktop WebSocket signaling blocked from context creation, a native host-to-host channel transferred a 1 MiB file with matching return hash. This does not prove an uncached offline first visit.

## Cloud Windows browser acceptance

Tested: 2026-10-22T08:13:59.427Z
Environment: Windows Server 2025 Datacenter, Chrome 155.0.8059.85 (x64).

GitHub-hosted Windows virtual machine, two isolated browser contexts on one host. Native WebRTC host-candidate route; ICE servers were cleared in the test harness. This verifies the recorded OS/browser workflow, not default STUN traversal, a physical Windows PC, Windows 11, iPhone-to-Windows, Android, or a same-Wi-Fi phone/PC session.

- Text delivered between isolated contexts: passed.
- os-1MiB.bin: passed; 1048576 bytes; SHA-256 c0978704744126c3999901381b5bbd1bb2a0ab5b20be30ed82816118643de894.
- os-return-1MiB.bin: passed; 1048576 bytes; SHA-256 c0978704744126c3999901381b5bbd1bb2a0ab5b20be30ed82816118643de894.
- 64 MiB rejection is not reported as success: passed.
- os-64MiB.bin: passed; 67108864 bytes; SHA-256 e3f94a7cf5e4223ed571fd220888bd5037140aa8298eecc51eee8adac4cbd58f.
- os-return-64MiB.bin: passed; 67108864 bytes; SHA-256 e3f94a7cf5e4223ed571fd220888bd5037140aa8298eecc51eee8adac4cbd58f.

Original workflow attachment SHA-256: 6c846f6de0f4f2dc825040779d3dc2abe5c97924b6e4e108e6dc8c1f2428d09f
HTML explanation: https://textunnel.com/transfer-guide#browser-tests
Machine-readable result: https://textunnel.com/windows-browser-acceptance.json