The theme: v1.6 loosens where the stack can live. Everything to date assumes the appliance model — one dedicated host, Caddy owning :443, the default subnet. v1.6 makes the documented opt-outs real: co-hosting next to other services (#181), a remote Tari node like Monero's remote mode (#103), and proof the stack actually works off the default subnet (#201).
#181 co-hosting umbrella ── split into: disable-Caddy mode / alternative-ports
(Wave 0: split the issue; define the auth-when-Caddy-is-bypassed fail-closed rule)
#103 remote Tari base node ── Wave 0: feasibility SPIKE first
(remote --merge-mine over gRPC: templates/submission/latency/auth → go/no-go;
must define how the #314 socat Tor bridge behaves in remote mode)
#201 e2e: non-default network.subnet in the live matrix
(independent; extend to cover post-#346 proxy_net + the #344 onion vhost binding)
Wave 0 — Splits & spikes
[TODO: verify upstream]items are listed in the gap assessment.The work
network.subnetin the live matrix. Already executable as written; one-line scope addition per the gap comment.tari.mode: remote) — only if the spike says go.Release status — cycle not open
Gates when it opens: #181 split merged · #103 spike verdict recorded · gouda pass including one co-hosted-profile scenario · CHANGELOG · standard cut process.