Decide whether GitHub Actions and kotlin.build should share one full-suite lease for url://netlab-hosted/. Cross-run evidence shows unbounded overlapping suites make manager-to-worker streams unwritable; approval is required before a separate implementation and measured manager cap.
Written 2026-07-30 ~07:05 UTC. RE-VERIFY banner: this handoff records a decision outcome; re-check the referenced handoffs and PRs live before acting.
This handoff was filed 2026-07-30 by a lane asking the owner to approve a single shared hosted-NetLab full-suite lease (across GitHub Actions and kotlin.build) plus a measured finite manager environment cap, as the prerequisite for reliable UrlResolver hosted CI runs.
The owner already ruled on exactly this question on 2026-07-30 (~03:45Z, recorded in PlanRepository session-2026-07-29-handoff-drive-state DECISIONS-NEEDED.md update, commit 263d924f): the lease/cap remediation is REJECTED as framed. The manager only coordinates worker droplets and should be nowhere near overloaded by ~45 environments; the required deliverable is the underlying defect fixed at the owning layer, not admission control.
The approved path (in flight): coordinated source upgrade of the NetLab manager and worker onto one current resolver/protocol set containing the already-merged retention fixes (https://github.com/CodexCoder21Organization/UrlResolver/pull/870, https://github.com/CodexCoder21Organization/UrlResolver/pull/887) and the response-delivery fix (https://github.com/CodexCoder21Organization/UrlProtocol/pull/430, enqueued 2026-07-30), plus retaining worker peer identity at provision time so the manager dials workers directly instead of announcing every short-lived worker into global discovery (the fanout amplifier). Then the pre-approved redeploy, then ONE hosted verification run.
If the stream-loss signature persists AFTER that upgrade+redeploy, the admission-side hypothesis returns to the owner with fresh instrumentation — but not before, and not as a lease "approval" that was already declined.
None here — this decision handoff is complete. The work continues under the 2026-07-29 handoff-drive session (url://handoff/handoffs/hf-2026-07-29-handoff-drive-session-2026-07-29-6-lane-per-handoff-campaign-11-prs-landed-resolver-netlab-cluster-gated-on-the-netlab-concurrency-decision-q8) and the SFS lane's own handoff, whose dependency on this decision clears with this completion.