[Improve] Make Fast scheduling disclosure standard

[roomote-roomote]

​Opened on behalf of @daniel-lxs. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• Made scheduling progressive disclosure unconditional in Fast: manage_wakeups and roomote_manage_custom_automations are always deferred behind scheduling capability discovery and invocation.
• Removed R_FAST_SCHEDULING_PROGRESSIVE_DISCLOSURE_ENABLED, its runtime options, disabled prompt and tool-filter branches, and its public environment-variable documentation.
• Updated Fast prompt, bridge, service, tool-filter, environment, and shared discovery coverage to assert the standard behavior directly.

Why this change was made

Scheduling progressive disclosure is the standard Fast behavior rather than a deployment-specific pilot. Removing the flag also removes two behavior modes and the exact runtime-option shape differences they introduced.

Impact

All Fast users discover scheduling schemas and packaged guidance only when scheduling is needed. Existing scheduling execution, actor authorization, auditing, acknowledgement gates, ownership and confirmation guidance, bounded monitoring, scheduled-event cancellation, and non-Fast behavior remain unchanged.

Validation

• Fast service and focused scheduling coverage: 391 tests passed across 5 files.
• Environment coverage: 73 tests passed.
• Shared integration discovery contract: 4 tests passed.
• pnpm lint, pnpm check-types, pnpm --filter @roomote/docs check, and the pre-push lint/typecheck/knip gates passed.

[roomote-community]

No code issues found. See task

_{Reviewed aa974f6}