id phase-7: P7.5 deployments and real-network tests are owner-blocked with no tracking issue #794

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: #795 (P3.7 — same owner-provided networks/accounts blocker; the acceptance brief groups P7.5/P3.7 at line 75). Plan §12 Phase 7 step P7.5 and the Phase 7 record's P7.5 row are cited in the body. Relay kit: connectivity/relay/relay.kit.toml (tunnel and vps modes).

   Still live (verified 2026-10-26): no merged PR references or resolves this issue; the relay kit has unit-level tests but has never been exercised on a real host. Not solved; do not close.

   Notes / risks: Genuinely owner-blocked (networks + accounts), so this is labelled status/blocked + user/review instead of status/needs-triage. The brief's instruction stands: keep the code-side harness ready and leave the live matrix explicitly blocked, not falsely passed. Nothing here is agent-actionable until the owner inputs exist.

   Suggested approach: When the inputs exist: deploy the relay kit on a real host (tunnel and/or vps), check /ping, /generate_204, and KillSignal behaviour, run the C2/N29 matrix, record results here and in the Phase 7 record, then close.

   🤖 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/accounts), still-live verified.
   • Expectation: effort/l once unblocked — real-host deployment + real-network matrix; until then, blocked on the owner inputs named above.
4. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/blockedQueue or user escalation stateQueue or user escalation state

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

   

   dezren39

   on Oct 28, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), Lane A shift
   • Session / ID: queue task 2224 · repo-queue-worker-shift 2026-10-28 14:00 CDT
   • Found via: queue claim (issue carries user/review — reviewed by the worker first, per protocol)
   • Task: Triage issue id phase-7: P7.5 deployments and real-network tests are owner-blocked with no tracking issue #794 — verify the P7.5 owner-blocked state at current HEAD and route it.
   • Expectation: s — done = facts verified, the exact owner inputs named, escalation recorded with the read attached
6. dezren39 commented on Oct 28, 2026

   

   dezren39

   on Oct 28, 2026

   MemberAuthor

   More actions

   🤖 Agent note · escalated

   • Agent: queue worker (repo-worker-code), Lane A shift
   • Session / ID: queue task 2224 · repo-queue-worker-shift 2026-10-28 14:00 CDT
   • Found via: queue claim; issue carried user/review, reviewed here first
   • Task: Triage of id phase-7: P7.5 deployments and real-network tests are owner-blocked with no tracking issue #794 complete; the blocker is owner-provided infrastructure, escalated with specifics below
   • Expectation: Drew provides (or declines) the inputs listed; on provision, the live matrix run is a straightforward worker task

   Triage read — facts verified at HEAD (2026-10-28)

   • The relay kit is present and current: relay.kit.toml exists at HEAD both in the design tree (doc/2026-10-11T03-44-33Z_design_groups_events_delegation/connectivity/relay/, alongside tunnel.toml, vps.toml, and iroh-relay.service) and as a test fixture (pkgs/id/tests/fixtures/relay/relay.kit.toml). Nothing about the kit is stale — it has simply never run on a real host, exactly as the issue says.
   • The blocker is genuinely external: every cited record (plan §12 P7.5, the Phase 7 connectivity note of 2026-10-12, acceptance brief line 75) says the same thing — the live matrix "cannot be truthfully verified without the required networks/accounts". No worker-side action substitutes for that; running it on one network or a sandbox would be the false pass the brief warns against.
   • Not superseded: no later connectivity work has run this matrix. (Phase 13's F13.3, id: Phase 13 F13.3 SSH-over-iroh reachability (and iroh-over-SSH fallback) #785 SSH-over-iroh, is a different item and still open.) The close-as-superseded exit in the criteria is not available on current evidence.
   • Shared blocker: sibling id phase-3: P3.7 real-network holepunch and n0 QAD tests on two networks are owner-blocked with no tracking issue #795 (P3.7, real-network holepunch/QAD tests) is blocked on the same owner inputs and is still open with the same status — one provision unblocks both issues.

   What Drew needs to provide (the whole ask)

   1. Two separate networks the test hosts can sit on (e.g. home LAN + a VPS's network, or two VPS in different providers/regions).
   2. Account access for at least one relay mode: a Cloudflare account/zone for Tunnel mode, and/or a VPS for vps mode.

   With those, the run is mechanical: deploy the kit in tunnel and/or vps mode on a real host, check /ping, /generate_204, and the systemd KillSignal behaviour, run the C2 matrix + N29 checks, record results here and on #795. If Drew would rather not spend the accounts/time, the honest alternative is an explicit descope decision recorded here — the kit and fixtures stay in-tree either way.
7. dezren39

   added

   user/escalatedQueue or user escalation stateQueue or user escalation state

   queue/blockedQueue or user escalation stateQueue or user escalation state

   status/blockedQueue or user escalation stateQueue or user escalation state

   and removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

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

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

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

   

   dezren39

   on Oct 28, 2026

   MemberAuthor

   More actions

   Owner constraints recorded (Drew, 2026-10-28, from the #795 ruling)

   • No second home network exists or will be provided; no VPC / paid networking — realistic server targets are plain hosts only.
   • The two-network portion of this issue follows the new id phase-3: P3.7 real-network holepunch and n0 QAD tests on two networks are owner-blocked with no tracking issue #795 plan (P3.7 test access: browser/Wasm peer page for phone runs + laptop VM NAT emulation #1826: phone/Wasm real-network cell + laptop VM NAT emulation).
   • What remains genuinely open here after that: the relay kit exercised on a real host. Tunnel mode via the existing Cloudflare account is the realistic path (no new paid infrastructure); vps mode only if a plain VPS enters the picture for other reasons. Recorded so this issue's blocker reflects the owner's actual inputs rather than the original framing. The lane A escalation (task 2224) is answered for the network half by this comment.
9. 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