id phase-3: P3.7 real-network holepunch and n0 QAD tests on two networks are owner-blocked with no tracking issue #795

Activity

1. github-actions

   assigned

   dezren39

   on Oct 24, 2026
2. dezren39

   added

   kind/testTest coverage, test infrastructure, or test-only fixesTest coverage, test infrastructure, or test-only fixes

   status/blockedQueue or user escalation stateQueue or user escalation state

   priority/lowNice to have; do when convenientNice to have; do when convenient

   effort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-ins

   app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)

   user/reviewNeeds a user-look: Muse reviews first and handles what it canNeeds a user-look: Muse reviews first and handles what it can

   meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels added

   on Oct 26, 2026
3. dezren39 commented on Oct 26, 2026

   

   dezren39

   on Oct 26, 2026

   MemberAuthor

   More actions

   Intake review

   Related: #794 (P7.5 — the same owner-provided networks/accounts block the deployment half; the acceptance brief groups P7.5/P3.7 at line 75). Plan §8 Phase 3 step P3.7 and the Phase 3 record's P3.7 row are cited in the body.

   Still live (verified 2026-10-26): no merged PR references or resolves this issue, and nothing has unblocked it — the C2 matrix and N29 QAD behaviour remain validated only on loopback. Not solved; do not close.

   Notes / risks: This item is genuinely owner-blocked: it cannot be worked by any agent until Drew provides two networks. I have therefore labelled it status/blocked + user/review (intake for Muse / Drew) rather than status/needs-triage — the triage conclusion is that there is nothing to triage, only a blocker to clear. The code-side harness should stay ready so the matrix runs immediately when networks exist; the brief's instruction stands — leave the live matrix explicitly blocked, not falsely passed.

   Suggested approach: When two networks are available: run the C2 matrix + N29 checks, record NAT/QAD results here and in the Phase 3 record, then close — or close as superseded if later connectivity work changes the design first.

   🤖 Agent note · intake enrichment

   • Agent: fleet monitor (repo-fleet-monitor)
   • Session / ID: repo-fleet-monitor run, 2026-10-26 00:19 CDT (05:19 UTC)
   • Found via: monitor reconciliation
   • Task: Intake enrichment (§5 pass): acceptance criteria appended, labels normalized (blocked on owner-provided networks), still-live verified.
   • Expectation: effort/l once unblocked — a real-network test matrix; until then, blocked on the owner input named above.
4. dezren39 commented on Oct 28, 2026

   

   dezren39

   on Oct 28, 2026

   MemberAuthor

   More actions

   🤖 Agent note · escalated

   • Agent: queue worker (repo-worker-code), lane D
   • Session / ID: queue task 2226
   • Found via: queue claim (issue carried user/review; reviewed first per protocol)
   • Task: Triage verdict for id phase-3: P3.7 real-network holepunch and n0 QAD tests on two networks are owner-blocked with no tracking issue #795 — confirmed, and the blocker is genuinely Drew's
   • Expectation: blocked until Drew provides two real networks; then the C2/N29 runs can be scheduled
   • Links: plan-phases.md P3.7 row; acceptance brief P7.5/P3.7 item

   Triage verdict: CONFIRMED and owner-blocked — escalated to Drew

   Verified at main HEAD 35726e8e9d93698e9922e85ba5d072d557edb36d (2026-10-28T18:50:35Z):

   • doc/2026-10-11T11-08-42Z_design_remaining_work/plan-phases.md:131 — P3.7 "Real-network holepunch and n0 QAD tests on two networks (N29)", blocked-by: "owner provides networks", test column: "the C2 matrix on real networks (owner-blocked)". The same doc's status header (line 4) repeats: "P7.5/P3.7 require external networks/accounts."
   • doc/2026-10-14T_platform_completion/acceptance-brief.md — the P7.5/P3.7 item is still unchecked: "real two-network and account-backed deployment matrix cannot be truthfully verified without the required networks/accounts. Keep the code-side test harness ready and leave the live matrix explicitly blocked, not falsely passed."
   • No superseding work found: searches for later real-network holepunch/QAD issues or PRs come up empty (only the original design docs PRs docs(id): design plan, research, and n0 relay default #152/id phases 0-10 review: file gaps, fix easy ones inline #804), so the "close as superseded" acceptance branch does not apply yet.

   My read: nothing here is agent-actionable. The code-side harness is ready; the C2 NAT/holepunch matrix and N29 QAD checks can only run when two real, distinct networks exist, and only Drew can provide those (e.g. home network + a second NAT/ISP or hotspot path, with a host on each). This is a genuine owner decision/provision, so I'm escalating rather than parking it silently: label swapped user/review → user/escalated, task 2226 blocked with reason class escalated-to-user.

   What Drew can unblock with: two reachable networks and a machine (or this laptop + one remote host) on each; a worker can then run the C2 matrix and record the numbers on this issue and in the Phase 3 record.
5. dezren39

   added

   user/escalatedQueue or user escalation stateQueue or user escalation state

   queue/blockedQueue or user escalation stateQueue or user escalation state

   and removed

   user/reviewNeeds a user-look: Muse reviews first and handles what it canNeeds a user-look: Muse reviews first and handles what it can

   on Oct 28, 2026
6. dezren39 commented on Oct 28, 2026

   

   dezren39

   on Oct 28, 2026

   MemberAuthor

   More actions

   Owner ruling (Drew, 2026-10-28): the blocker as framed is withdrawn — new plan

   Drew's answer to 'provide two networks':

   • He does not have a second computer on a second home network, and will not be setting one up. No VPC or paid networking either — any server we run would be a plain host, not a VPC.
   • He WILL run the test himself from his phone: a website he can open on the phone (Wasm is fine), or a mobile app.
   • VMs on the laptop with an emulated NAT configuration are acceptable for cells a phone cannot cover.
   • His phone's carrier network is not a second home network — correct, and it doesn't need to be: carrier CGNAT vs home NAT is a legitimate, hard, realistic cell (it is the pairing actual mobile users present), and it is the cell the phone run measures honestly.

   New plan: filed as #1826 — (1) a browser/Wasm peer page Drew runs on his phone against the laptop peer at home; (2) a reproducible laptop VM NAT-emulation config for the remaining C2 cells, with emulated results labeled as emulated, never as real-network measurements. This issue's first acceptance criterion ('two owner-provided networks') is superseded by this ruling; the run-and-record criteria stand, under the new plan. The lane D escalation (task 2226) is answered by this comment.
7. dezren39 commented on Oct 28, 2026

   

   dezren39

   on Oct 28, 2026

   MemberAuthor

   More actions

   Added per owner direction (Drew, 2026-10-28)

   Companion issue filed: #1831 — proof-of-concept Android app + extending the accepted input interfaces (multi-touch, mice, hover on web and TUI; enter/leave/click/right-click where the platform allows; press/long-press on Android) so phone input can be relayed into a live app over a deliberately limited interface (click minimally; drag/scroll as proven). The Android app doubles as a native phone peer for this issue's test line, alongside the Wasm page in #1826.
8. dezren39

   added

   mode/hybridOnline work plus a physical step (power, cabling, KVM access to a real device)Online work plus a physical step (power, cabling, KVM access to a real device)

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 1, 2026
9. dezren39 commented on Nov 3, 2026

   

   dezren39

   on Nov 3, 2026

   MemberAuthor

   More actions

   Status note: the withdrawn blocker now has two tracked execution legs

   Follow-up to the 2026-10-28 owner ruling. Triage of #1826 at d3476bce7 (2026-11-03, queue task 7751) confirms both legs are still unexecuted and splits them:

   • Proof-of-concept Android app + input interface extension (touch, mouse, hover) for relaying into live apps #1831 — Android phone peer. This is the viable phone leg: a browser cannot be an iroh peer (no UDP; iroh compiles QAD probes out under wasm_browser), so the carrier-CGNAT × home-NAT cell must be measured by a native phone app, which Drew's ruling already allows ("Wasm is fine, or a mobile app").
   • id: make the C2 NAT-emulation lab reproducible from the repo (de-hardcode paths, add a runnable entry point) #4984 — reproducible C2 NAT-emulation lab. The emulation itself already exists (spikes/c2-holepunch/lab, netfilter cone/restricted/symmetric, full and mixed matrix in RESULTS.md:96-123); it is unusable from a clean checkout because of hardcoded absolute paths.

   This issue stays status/blocked: its run-and-record criteria are unchanged, and emulated results will arrive labelled emulated, never as real-network measurements.

   🤖 Agent note · blocked (dependency tracking)

   • Agent: queue worker (repo-worker-code), lane ec118cad-0fd3-4652-91c4-27432f2f2efd
   • Session / ID: queue task 7751 (P3.7 test access: browser/Wasm peer page for phone runs + laptop VM NAT emulation #1826 triage)
   • Found via: triage of the plan issue filed against this one
   • Task: Recorded the split (Proof-of-concept Android app + input interface extension (touch, mouse, hover) for relaying into live apps #1831 phone peer, id: make the C2 NAT-emulation lab reproducible from the repo (de-hardcode paths, add a runnable entry point) #4984 reproducible emulated lab); no label change here, the escalated/blocked state is unchanged.
   • Expectation: results posted here when both legs land.
10. dezren39 commented on Nov 4, 2026

    

    dezren39

    on Nov 4, 2026

    MemberAuthor

    More actions

    Emulated C2 matrix results (2026-11-04)

    These are Linux netfilter emulation results only, not real NAT devices, carrier CGNAT, or real-network measurements. The reproducible entry point and implementation are in PR #5665. Command from the repository root:

    C2_WINDOW=8 nix --extra-experimental-features "nix-command flakes" run ./doc/2026-10-11T03-44-33Z_design_groups_events_delegation/spikes/c2-holepunch#c2-lab

    All three NAT-behaviour probes completed and all nine ordered pairs completed with dial exit 0:

    Host A	Host B	Final selected path
    cone	cone	direct
    cone	restricted	direct
    cone	symmetric	direct
    restricted	cone	direct
    restricted	restricted	direct
    restricted	symmetric	relay
    symmetric	cone	direct
    symmetric	restricted	relay
    symmetric	symmetric	relay

    The local timestamped report was 20261104T222140Z-emulated-c2-matrix.md; the repository ignores generated results* artifacts. These results satisfy the emulation leg only; #795 remains blocked for the separate phone/carrier-network leg (#1831).}