digz-comms-tailscale

name	digz-comms-tailscale
description	Use when agents are "not getting messages", bridge queue is stuck, Claude is confused about sandbox/access, or you need exact Windows Tailscale/Claude paths. Recover and operate inter-agent comms lanes with exact runbooks and launch prompts.
type	encoded-preference

DIGZ Comms + Tailscale (Encoded Preference)

This skill encodes a strict Encoded Preference (SOP) for restoring lane capabilities quickly and giving agents exact, executable instructions when fixing bridge communication failures.

🎯 The Objective

Deterministic, step-by-step restoration of the OpenDigz factory-comms-lane architecture when Triad agents (Claude, Gemini31, Antigravity) lose connection or get stuck in sandboxes.

🛠️ Execution Protocol

Step 1: Locked Paths And Hosts

You MUST strictly adhere to these paths:

• Linux lane controller: /home/jb/Digz-Opendigs-co-repo/.claude/plugins/digz-agent/scripts/factory_comms_lane.py
• Linux bridge worker wrappers:
  • /home/jb/Digz-Opendigs-co-repo/.claude/plugins/digz-agent/scripts/claude_windows_bridge_worker.sh
  • /home/jb/Digz-Opendigs-co-repo/.claude/plugins/digz-agent/scripts/antig_bridge_worker.sh
• Linux lane state root: /home/jb/.digz/factory-comms-lane
• Windows host: jbald@100.100.11.39
• Windows verified binaries:
  • C:\Users\jbald\AppData\Roaming\npm\claude.cmd
  • C:\Program Files\Tailscale\tailscale.exe

Step 2: Lane Health Snapshot

1. Read the environment: source /home/jb/.digz/factory-comms-lane/env && echo "$DIGZ_ENABLE_INTERBOX_COMMS" (Expected: 1)
2. Check JSON status: python3 /home/jb/Digz-Opendigs-co-repo/.claude/plugins/digz-agent/scripts/factory_comms_lane.py status --json

Step 3: Rescue Operations

If the bridge is unhealthy/stale, ALWAYS run:

1. python3 /home/jb/Digz-Opendigs-co-repo/.claude/plugins/digz-agent/scripts/factory_comms_lane.py start
2. python3 /home/jb/Digz-Opendigs-co-repo/.claude/plugins/digz-agent/scripts/factory_comms_lane.py rescue --min-age-sec 30

Step 4: Dispatch Targets (Copy-Paste Tasks)

When relaunching lanes, use --dispatch bridge.

Claude Lane: python3 /home/jb/Digz-Opendigs-co-repo/.claude/plugins/digz-agent/scripts/factory_comms_lane.py launch --lane claude --dispatch bridge --task "claude: You are on Windows host jbspc via SSH target jbald@100.100.11.39. You are NOT sandbox-only. Verify comms by replying exactly: CLAUDE_COMMS_OK, then read queued work and execute."

Antigravity Lane: python3 /home/jb/Digz-Opendigs-co-repo/.claude/plugins/digz-agent/scripts/factory_comms_lane.py launch --lane antig --dispatch local --task "antig: full auto enabled. Reply ANTIG_COMMS_OK, consume queued work, and continue until blocked."

🚨 Trigger Tuning & Evlas

• Evaluation Criteria: If Claude reports "sandbox/no access", force the Windows verification via SSH (ssh jbald@100.100.11.39 'powershell -NoProfile -Command "(Get-Command claude).Source"') and explicitly relaunch the Claude task with the absolute host path.
• Pass Rate Check: >99%. Never guess file paths. Always use the stated routes.
• Trigger: Do not trigger during normal OpenDigz Next.js development unless the user explicitly mentions the bridge, lanes, or tailscale is broken.