[Docs] Explain tool policy changes for running tasks

[roomote-community]

​Opened on behalf of @mrubens. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

• clarify that a per-tool policy change applies to an already-running task at its next tool call
• explain that the task does not need to restart before following the new policy

Why this change was made

The public-documentation audit reviewed all eight first-parent commits merged to develop from 2026-10-02T03:00:45.895Z through 2026-10-03T03:00:45.895Z. Shipped proxy enforcement now catches policy changes for tasks that started before a tool was gated, while the Integrations guide still said choices only applied from the next session turn.

Impact

Operators and session owners can now tell when a tightened integration-tool policy takes effect for work that is already running. This is a documentation-only correction.

Screenshots

Representative DOM-rendered fallback only: the local Mintlify preview was missing generated Next.js manifest files after hot reload. The image proves the complete wording is readable, not genuine Mintlify rendering or runtime policy enforcement.

[roomote-community]

No code issues found. See task

_{Reviewed 3dcc087}