[WSLC] (2/4) Hold multiple sessions in the lifecycle daemon

docs/backends/wslc/wsl-container-getting-started.md

@@ -386,8 +386,10 @@ The separate `provision` operation takes the same list under
 
 The lifecycle daemon creates one container per sandbox, so a forward belongs
 to the sandbox that declared it. The session-wide `cpuCount` / `memoryMb` /
-`gpu` settings remain available only for create-and-run execution, because that daemon shares a
-single WSL session across every sandbox. `storagePath` is create-and-run-only
+`gpu` settings remain available only for create-and-run execution, because every
+lifecycle `provision` currently joins one shared session. The daemon itself holds
+several independently sized sessions; what no caller can yet do is ask for one.
+`storagePath` is create-and-run-only
 for a different reason: the daemon leases its store from a slot pool rather
 than taking a caller-named path, so warming its cache is a separate step. See
 [the lifecycle guide](wslc-state-aware.md#image-store).

docs/schema.md

@@ -576,8 +576,10 @@ posture is rejected at provision.
 
 Two entries claiming the same `windowsPort` are rejected on both surfaces. The
 session sizing knobs (`cpuCount` / `memoryMb` / `gpu` / `storagePath`) stay
-available only for create-and-run execution, because the lifecycle daemon shares one WSL session across
-every sandbox and cannot size them individually.
+available only for create-and-run execution, because every lifecycle `provision`
+currently joins one shared session and so cannot size sandboxes individually.
+The daemon itself holds several independently sized sessions; what no caller can
+yet do is ask for one.
 
 Full lifecycle API: [container lifecycle](container-lifecycle.md).
 

scripts/setup-wslc.ps1

@@ -47,7 +47,9 @@
     a slot that has never been leased holds no images. Defaults to 0, matching
     `wxc-exec.exe --wslc-daemon-slots`, so warming a create-and-run cache stays
     one pull per image. Pass 1 before running container lifecycle operations
-    against an isolated posture; each slot costs another pull and another
+    against an isolated posture, and one slot per session you expect to run at
+    once beyond that — a session that leases a cold slot cannot resolve an
+    uncached image under that posture. Each slot costs another pull and another
     multi-GiB store.
 
 .PARAMETER DebugLogs