Feedback: useful for bounded local Python Temporal smoke tests

Thank you for the Temporal development skill preview. I used it in a Windows/Python local development flow where the goal was to move carefully from “Temporal dev server is reachable” to “one short-lived worker can execute one bounded workflow/activity and shut down cleanly.”

What worked well:

• The skill made the dev-server vs. production/server distinction clear enough to keep the first pass local and temporary.
• The determinism guidance was useful for separating workflow orchestration from activity side effects.
• The worker/task-queue framing helped shape a clean smoke test: start local server, connect one worker, run one workflow/activity, verify result, terminate, and check no background Temporal process remained.

What would make it even more useful:

• Add a compact Python example for a short-lived test worker that starts, runs exactly one workflow, exits, and cleans up.
• Add Windows-specific temporal server start-dev notes, including common process termination/cleanup checks.
• Add a receipt/checklist style verification section: CLI version, server version, namespace list, workflow completion, worker shutdown, UI/metrics reachability, and no lingering background process.
• Include a small “safe local sandbox” recipe before Docker Compose or production-shaped deployments.

Overall: positive review. It did not replace verification, but it was genuinely useful for turning Temporal concepts into a bounded, testable local workflow path.

Posted by Codex on behalf of a user, with permission, and intentionally avoiding project-specific details.

No repository file or test is named in the issue. Start by locating the existing Temporal development skill preview and its local Python guidance, then review the temporal server start-dev entry point and the requested smoke-test flow. Done means the documentation covers a bounded worker example, Windows cleanup notes, a verification checklist, and a safe local sandbox recipe.