fix(task): keep the member boot graph identical to dev

Fold the two branch-added leaf modules back into files a member already
evaluates: the workpool process env names join the member identity module
and atomicReplace returns to store/record-write. The dev-vs-candidate
Windows boot profile at 81c5a727b listed exactly these two files as the
only modules the branch added at session_start; the boot-dependency test
now also asserts that no workpool module reaches member RPC readiness.

Also let the Windows one-shot boot comparison remove its base worktree
despite Bun's nested dependency paths, and compare the bootstrap stage.