docs: fix Bash timeout unit and document background cap

[wucm667]

Related Issue

No issue — this is a documentation-only fix, which CONTRIBUTING.md allows to be opened directly.

Problem

The Built-in Tools reference describes the Bash timeout parameter as milliseconds, but the implementation uses seconds (bash.ts: DEFAULT_TIMEOUT_S = 60, MAX_TIMEOUT_S = 5 * 60; the param description and bash.md both say "in seconds"). The docs also omit the background timeout maximum of 24h (MAX_BACKGROUND_TIMEOUT_S = 24 * 60 * 60 = 86400s).

This affects both docs/en/reference/tools.md and docs/zh/reference/tools.md.

What changed

• Fixed the timeout unit from "milliseconds" → "seconds" (en) / "毫秒" → "秒" (zh).
• Documented the background timeout maximum of 24 hours (matches MAX_BACKGROUND_TIMEOUT_S).

No code/behavior change.

Local verification:

$ pnpm --filter kimi-code-docs build
(!) Some chunks are larger than 500 kB after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
✓ building client + server bundles...
- rendering pages...
✓ rendering pages...
build complete in 7.42s.

Checklist

• I have read the CONTRIBUTING document.
• No related issue — documentation-only change (allowed to open directly).
• Tests — N/A, documentation-only change.
• No changeset needed (docs-only).
• Docs updated directly in this PR.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6cb0125

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR