[HalRiveria-Bot]

What was wrong

Two gaps were left after the kit became an in-memory module in #27:

• Callbacks inside a worker runspace. There the kit's functions are plain copies, not a module. A closure-less -OnComplete given to Invoke-PkProcessBatch in a worker could still add to the batch's own $results, write to its $state, and read its $TimeoutSeconds, with silently wrong results. Dispatcher callbacks had the same problem, for example reading the kit's $running.
• A drive made with New-PSDrive inside a function. It can only be seen from that function, so the module couldn't resolve a WorkingDirectory or FilePath on it.

Generated lookup script (added in #27) also quoted names and paths by doubling ASCII single quotes only. PowerShell also treats curly quotes as string delimiters, so a curly quote could end the literal early. A new check showed a path running as code in the caller's scope.

What changed

• pk-prefixed variables in Invoke-PkProcessBatch, Invoke-PkProcessDispatch, Invoke-PkProcessDispatchCore and the group-building helper. Locals are renamed, and parameters are copied to pk names and removed. Public parameter names don't change. The diff is large, but the rename itself was done mechanically from the syntax tree.
• The drive lookup falls back to the caller's session. When the module's own lookup fails, the path is resolved again from where the kit was called. Start-PkProcess is now a thin wrapper over an internal function that takes the caller's session, and Invoke-PkProcessWithTimeout, the dispatcher's default starter and the batch pass theirs. Paths the module can already resolve take the same route as before.
• Quoting uses CodeGeneration.EscapeSingleQuotedStringContent, in the function lookup and the path lookup.
• README: plain callbacks no longer need .GetNewClosure() inside a worker, and the -Scope Script advice for drives is gone.

Still true: a closure-less callback in a worker can see a kit function's automatic variables, such as $PSBoundParameters, and a variable of the worker's own named with the pk prefix could collide.

Testing

• New harness section AA, 7 checks:
  • in a worker, plain callbacks reach the worker's $results, $state, $TimeoutSeconds and $running;
  • a guard lists every variable visible from plain batch and dispatcher callbacks in a worker, and fails on any kit variable without the prefix;
  • a WorkingDirectory on a function-local drive works from Invoke-PkProcessWithTimeout, Start-PkProcess, the batch, the batch under Invoke-PkRun and the dispatcher;
  • a FilePath on that drive works;
  • a drive that doesn't exist still gives a clear start error;
  • a path with a curly quote stays a path.
• Against main's kit (5.1), the worker and drive checks fail (5 FAILED, 1 passed, run before the curly-quote check existed). The nonexistent-drive check passes on both, as a guard. The curly-quote check failed before its fix on this branch.
• With the change: ALL PASSED (288 assertions) on Windows PowerShell 5.1 and PowerShell 7.

🤖 Generated with Claude Code