Make MultiAgentV2 wait minimum configurable

[jif-oai]

Why

MultiAgentV2 wait_agent currently clamps short waits to a fixed 10 second minimum. That default is still useful for preventing tight polling loops, but it is too rigid for environments that need faster mailbox wake-up checks or a larger minimum to discourage frequent polling.

This PR makes the minimum wait timeout configurable from the existing MultiAgentV2 feature config section, so operators can tune the behavior without changing the legacy multi-agent tool surface.

What Changed

• Added features.multi_agent_v2.min_wait_timeout_ms.
• Defaulted the new setting to the existing 10 second floor.
• Validated the configured value as 1..=3600000, matching the existing one hour maximum wait bound.
• Applied the configured minimum to MultiAgentV2 wait_agent runtime clamping.
• Plumbed the configured minimum into the wait_agent tool schema, including the effective default when the minimum is above the normal 30 second default.
• Regenerated core/config.schema.json.

Verification

• cargo test -p codex-features
• cargo test -p codex-tools
• cargo test -p codex-core --lib multi_agent_v2
• just fix -p codex-core

[jif-oai]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Keep it up!

ℹ️ 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".