Update nebula to master 7cfa47d

[jasikpark]

Moves the nebula pin from v1.11.0 to master 7cfa47d (2026-09-22). This is the commit every Defined Networking client is converging on. It supersedes #404, which stops at v1.11.2.

Master has everything v1.11.2 backported, plus work that never went to the release line. The indirect bumps are nebula master's own dependency versions.

On iOS, master's Network Extension idles about 7 MiB lower than 1.11, because it no longer links gopacket (DefinedNet/nebula-apple#8). This app links the same nebula package graph.

Verified in nebula/: go build ./..., go vet ./... (host and GOOS=android GOARCH=arm64), go test ./..., and an iOS arm64 cgo cross-compile.

lookihere: iOS Network Extension memory, 1.11 vs master

Measured on an iPhone 13 Pro, same site. A 10-second timer in the extension logs the process footprint from task_info(TASK_VM_INFO), plus os_proc_available_memory() and Go runtime.MemStats. The jetsam limit is footprint + available.

Native app (nebula-apple), Debug build. A is release-1.11 2a3aa08, B is master e20569c, the parent of 7cfa47d. About 5 minutes idle each.

MiB	A: 1.11	B: master
footprint before start	12.39	5.50
footprint at steady idle	~16.9	~10.2
peak	17.42	10.35
Go Sys	16.65	12.57
Go HeapInuse	~2.8	~3.4
jetsam limit	50.00	50.00

Flutter app (mobile_nebula), Profile build. A is v1.11.2, B is master 7cfa47d. About 5 minutes idle each.

MiB	A: 1.11	B: master
footprint before start	—	5.10
footprint at steady idle (median)	16.49	9.19
peak	16.77	9.52
Go Sys	16.90	12.31
Go HeapInuse (median)	2.74	3.49
jetsam limit	50.00	50.00

A's before-start sample fell outside the log window.

Both apps come out within about 0.5 MiB of each other, so the difference comes from nebula, not from the app wrapper. Master no longer links gopacket (slackhq/nebula#1864), which is where most of the drop comes from.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MurGUoeWWCURHtoWFB7R56