Expose lite worker launch in Factory SDK

[flujo-app]

Summary

• Expose Factory.startLiteWorker(...) and standalone startLiteWorker(...) from the installed SDK. Both return the native CLI ChildProcess.
• Route factory-lite through the same SDK launcher, with the existing Codex and Claude MCP isolation and full built-in tool access.
• Document SDK use and exercise the new method in source tests and packed-package smoke.

Local CI before GitHub

All four jobs ran from independent clean tracked-source archives of commit ee3579b, with clean dependency installs and no shared node_modules.

Platform	Node	npm	Result
Windows	22.17.0	11.19.0	Pass
Windows	24.19.0	11.19.0	Pass
Linux Docker	22.17.0	10.9.2	Pass
Linux Docker	24.19.0	11.17.0	Pass

Each job ran npm ci, npm audit --omit=dev --audit-level=high (0 vulnerabilities), and the workflow's focused node --test command over the 11 public SDK/fleet/presentation test files (69/69 passed). Each also ran npm pack --pack-destination <temp> --json, a fresh npm install --prefix <consumer> <tarball> --ignore-scripts --no-audit --no-fund, installed SDK swarm creation and lite-worker launch smoke, factory and factory-lite help, and installed MCP stdio smoke (node --test --test-name-pattern="public MCP stdio" test/public-sdk.test.mjs, 1/1 passed).