feat(mcp): run scheduled tasks immediately

[juliusmarminge]

Problem

Scheduled tasks can be managed through MCP, but agents could not trigger one immediately without bypassing scheduler bookkeeping or risking duplicate work on retry.

Change

• Add run_scheduled_task_now with a required stable request key.
• Route manual runs through ScheduledTaskService, ThreadLaunchService, and V2 command receipts.
• Serialize command identity, task mutation, and caller/target policy checks with the existing thread executor.
• Resume a partial unbound launch once without rewriting task bookkeeping already owned by another logical run.

Behavior

Fresh calls re-read the task and bound target under admission, enforce current project and runtime/interaction ceilings, and return durable thread, message, run, and receipt identities. Accepted retries return the original effect after task changes or deletion. Conflicting key reuse fails without mutating the losing task. A successful partial-launch resume does not rewrite runCount, nextRunAt, or the latest run summary.

Validation

• 19 focused scheduler service, MCP/V2 integration, and contract tests.
• Scoped @t3tools/contracts and t3 typechecks.
• Formatting and type-aware lint for all changed files.

Base

Standalone PR on t3code/codex-turn-mapping at 415ed0f73b97f1655b6282492f81d0b2bba3a9cc.

Implemented by GPT-5.6-Sol via Codex in T3 Code.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a0316b7f-ee1f-45ef-af05-dbf67f1938cb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the changed Effect service code (ScheduledTaskService, Orchestrator, ThreadLaunchService, ThreadManagementService, MCP toolkit/handlers, contracts) against the service conventions. Two convention violations found, both in apps/server/src/scheduledTasks/. The new policyCeiling plumbing, getCommandReceipt exposure, and makeKeyedSerialExecutor usage all follow existing module/layer conventions.

^{Posted via Macroscope — Effect Service Conventions}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for c5a6c97.

This comment will update automatically after the next completed run.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new MCP workflow that can durably create threads, dispatch agent runs, update scheduler state, and replay commands across multiple orchestration layers. It also changes shared policy enforcement and dispatch locking, making the runtime and authorization impact broad enough to require human review.

No code changes detected at c5a6c97. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One convention finding on the new scheduled-task manual-run errors; everything else (namespace imports, layer/service shape, dependency acquisition, test seams) looks consistent with the repo conventions.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One convention finding in the Effect service changes: new code in Orchestrator.ts references the standalone CommandReceiptStoreV2Shape type instead of the inferred Foo["Service"] interface. Everything else (tagged manual-run errors with derived messages, namespace imports, keyed serial executor as a pure helper, test-only service seams) looks consistent with the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit e8823bd. Configure here.}

[juliusmarminge]

Superseded as the active MCP proposal by #10562 in the rebuilt MCP stack, following the maintainer request to review thin service wrappers separately from service hardening.

This is not a full feature-parity replacement. Requires a full-access/default caller. Each call is a new manual run, not an idempotent retry. Returned bookkeeping is not provider turn completion; durable keyed retries and scheduler hardening are separate.

Closing this mixed proposal without merging. The remote branch agents/mcp-scheduled-tasks/run-now and exact head c5a6c9755adea95bd684df1efd84ec13dfe0e69b are retained so the service changes can be extracted for separate review later.