Plan the 0.4.0 work: consent, cancel, status, NAT proof, Windows - #65
Merged
Merged
Conversation
The user set priorities on 2026-09-14: the receiver sees what is coming and accepts before anything is written, either side can cancel, the sender sees the receiver's state throughout, NAT traversal is proven rather than assumed, and drop works on Windows, macOS and Linux with transfers between them. Two new plans. Receiver consent and status supersedes the 2026-08-19 confirmation plan, which was written against cleartext metadata. Cross-platform records that Windows has no build and macOS has never had a test run. The browser removal and browser-on-iroh plans from 2026-09-11 are committed, with the removal's four open questions answered as the plan leaned. A re-run of netlab found that hole punching has never been exercised there: QUIC address discovery fails TLS against the lab helper's self-signed certificate, so no peer learns its public address. The helper's comment and the rendezvous plan both claimed iroh skips that check; it does not. Recorded in the netlab plan, with the fix proposed as self-hosted rendezvous phase 3 and left for a decision because it changes what the CLI trusts. Also corrected: meta_ok confirmation was to land before the direct path shipped, and the direct path shipped in v0.2.0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01G7Fy45hUvna94cd79WKG8S
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This was referenced Sep 14, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs only. No code, workflow, or wire changes.
What's in it
docs/plans/receiver-consent-and-status-plan-2026-09-14.md). The receiver sees name, type, size and destination and accepts before anything is written. Either side can cancel and the other is told in words. The sender sees each step the receiver goes through. It replaces the 2026-08-19 confirmation plan, now marked abandoned.docs/plans/cross-platform-plan-2026-09-14.md). Today Windows has no build, macOS has never had a test run, and CI is Ubuntu only. Phase 0 puts tests on all three.UnknownIssuer), so no peer learns its public address. That, not iroh, is why the full-cone test fails. The fix is proposed as self-hosted rendezvous phase 3 and left for a decision, because it changes which certificates the CLI trusts.meta_okconfirmation was meant to land before the direct path shipped, but the direct path shipped in v0.2.0. Self-hosted rendezvous phase 1 was done but still unchecked.Checks
scripts/check-secrets.shpassesgit diff --checkis cleandocs/resolves🤖 Generated with Claude Code
https://claude.ai/code/session_01G7Fy45hUvna94cd79WKG8S