Blocker: deployed StartOS and Umbrel transfer UAT needs real installed nodes

[dskvr]

MeshDrop has local/package smokes for Start9/StartOS and Umbrel artifacts, but final deployed-node acceptance remains unproven until real installed services run the deployed UAT harnesses.

Current evidence in GSD:

• Start9/StartOS package builds and package smokes exist.
• Umbrel package render/smoke exists.
• Deployed target harnesses require installed service URLs, but real node UAT is still open.

Required unblocker:

• Provide reachable installed StartOS and Umbrel MeshDrop service URLs from real nodes.
• Run npm run test:start9-deployed and npm run test:umbrel-deployed with those URLs.
• Capture route proof for local and Pollen/Nostr paths expected on each target.

Acceptance:

• npm run test:start9-deployed -- <startos-url> passes against a real installed service.
• npm run test:umbrel-deployed -- <umbrel-url> passes against a real installed service.
• Proof output includes target runtime, route type, bytes sent/received, hash match, fallback status, and config target identity.
• Any environment-specific unsupported route stays fail-closed and documented.

[dskvr]

Fresh check 2026-07-08T00:18:24+02:00 from /home/sandwich/Develop/meshdrop-fips-byte-route-proof-20260708:

npm run status:external-uat -- v0.1.5 still reports deployed-target blockers:

• Start9: missing MESHDROP_START9_UAT_URL; next proof is npm run test:start9-deployed with installed service URL.
• Umbrel: missing MESHDROP_UMBREL_UAT_URL; next proof is npm run test:umbrel-deployed with installed service URL.

Status: still blocked on real deployed service URLs.

[dskvr]

Fresh evidence from 2026-07-08 on origin/master (5a4fed99b48aa42711d266a0a7f836ab6362e603):

$ npm run status:external-uat -- v0.1.5 --json

Start9 deployed-device UAT: blocked
Reason: Missing MESHDROP_START9_UAT_URL. Set MESHDROP_START9_UAT_URL=<installed StartOS service URL> and run npm run test:start9-deployed.

Umbrel deployed-node UAT: blocked
Reason: Missing MESHDROP_UMBREL_UAT_URL. Set MESHDROP_UMBREL_UAT_URL=<installed Umbrel service URL> and run npm run test:umbrel-deployed.

Local package/build smokes are covered by CI and npm test; this issue remains the real installed-node acceptance surface.