[Chore] Revert Fast scheduling progressive disclosure pilot

[roomote-roomote]

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

What changed

• Reverted the scheduling progressive disclosure pilot introduced by merged commit da75b0ef2bd8e685323920d73e39bdc4a3c67da2 in full.
• Restored direct Fast exposure and execution of manage_wakeups and roomote_manage_custom_automations.
• Removed the scheduling-specific discovery transport, packaged scheduling skill, environment flag and public documentation, prompt branches, shared lookup additions, and pilot-only tests.
• Preserved subsequent own-task monitoring guidance and the separately shipped Code Mode experiment.

Why this change was made

The scheduling pilot made the Fast scheduling path too narrowly exposed. Returning to the pre-pilot behavior keeps scheduling tools and their operational guidance directly available without replacing the pilot with another disclosure mechanism.

Impact

Fast Sessions once again receive and call the scheduling tools directly. Focused Fast, environment, shared lookup, and automation UI tests passed, along with full lint, full typecheck, and the mandatory pre-push lint, fast typecheck, and Knip gates.

Open PR #2441 depends on the reverted pilot architecture and will conflict with or become obsolete after this change. This PR does not modify #2441. Code Mode from #2442 remains unchanged.

[roomote-community]

No new code issues found. See task

• Remove the stale R_FAST_SCHEDULING_PROGRESSIVE_DISCLOSURE_ENABLED documentation row in apps/docs/environment-variables.mdx:135.

_{Reviewed d441321}