fix: honor approvals.timeout across CLI and ACP

[tomgreeEn]

Summary

• make ACP approvals inherit approvals.timeout from config when no explicit timeout is provided
• allow non-positive ACP timeout values to wait indefinitely
• make the main terminal CLI approval UI also honor approvals.timeout instead of a hardcoded 60s limit
• add regression tests for both ACP and terminal CLI approval flows

Problem

Hermes had two separate 60-second approval timeouts:

• the ACP approval bridge defaulted to 60 seconds
• the main terminal CLI approval UI also hardcoded 60 seconds

This meant approvals.timeout in config.yaml was not fully honored, and users could still hit 1-minute expiry in regular terminal sessions even after fixing the ACP path.

Test Plan

• run ./venv/bin/python -m pytest tests/acp/test_permissions.py tests/cli/test_cli_approval_ui.py -q -o 'addopts='
• run ./venv/bin/python -m py_compile cli.py acp_adapter/permissions.py tests/cli/test_cli_approval_ui.py tests/acp/test_permissions.py
• manually verify that dangerous-command approval prompts no longer expire after 60 seconds when approvals.timeout is set higher

Fixes #3765.

[teknium1]

Thanks for tracing the configuration gap across CLI and ACP. The CLI portion is already present on current main in 8ae65d5c8 (cli.py:11695), but the ACP work is still useful after a focused port.

Problems

• The change covers only ACP command approvals. Current main also creates an ACP edit approval requester at acp_adapter/server.py:1425; that requester still defaults to 60 seconds in acp_adapter/edit_approval.py:290 and waits with it at :327.
• The proposed timeout <= 0 behavior blocks ACP command approvals indefinitely, while the CLI deadline expires immediately for that value (cli.py:11705, :11733). This also differs from the documented fail-closed timeout contract (website/docs/user-guide/security.md:141-147).
• Current ACP bridging now schedules through safe_schedule_threadsafe (acp_adapter/permissions.py:134-150), so the PR's direct scheduler call and scheduler patch in its tests need porting.

Suggested changes

• Salvage the ACP configuration resolution against the current helper, cover both command and edit approval bridges, and define one shared non-positive timeout policy.

Automated hermes-sweeper review.

[teknium1]

Please extend the configured timeout to the ACP edit approval requester as well. Current main constructs that independent bridge in acp_adapter/server.py:1425; it still defaults to 60 seconds in acp_adapter/edit_approval.py:290, so edits would retain the reported bug.

[teknium1]

An indefinite wait for timeout <= 0 conflicts with the current CLI, which immediately expires a non-positive deadline (cli.py:11705, :11733), and with the documented fail-closed timeout behavior. Define one shared policy before making ACP special-case this value.