Allow disabling wrapper timeout

[alex-mextner]

Summary

• Treat --timeout-sec 0 as disabling the claude-p wrapper timeout for long-running prompts
• Keep positive timeout behavior unchanged through a small timeout helper
• Document the behavior in English and Chinese README usage sections

Motivation

Some Claude Code tasks legitimately run longer than a fixed wrapper timeout. Users can already manage timeouts outside claude-p with their shell, CI runner, or SDK caller, so --timeout-sec 0 should let the wrapper wait indefinitely while Claude Code continues to run normally.

Example usage:

claude-p "Run a long local task and summarize the result" --timeout-sec 0

Validation

• uv run --with pytest pytest tests -q -> 12 passed
• uv build -> built dist/claude_p-0.1.4.tar.gz and dist/claude_p-0.1.4-py3-none-any.whl
• uvx twine check dist/* -> PASSED

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cf7dd2634b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Reject NaN timeout values before disabling timeout

argparse accepts --timeout-sec nan as a float, and with this helper that value never expires: timeout_sec <= 0 is false for NaN and current - start >= timeout_sec is also always false, so run_tui can wait indefinitely unless another exit path happens. This is a regression from the prior loop condition (which did not continue when timeout was NaN) and can surprise callers who accidentally pass invalid numeric input.

Useful? React with 👍 / 👎.