feat(studio): add scheduled runtime tasks

frontend/README.md

@@ -612,6 +612,37 @@ veadk studio deploy \
   --vefaas-app-name <app-name>
 ```
 
+## Scheduled tasks
+
+The `定时任务` workspace runs a fixed text prompt on a selected deployed Runtime
+Agent. Each occurrence creates an independent Agent session. Schedules support
+one-time, daily, weekly, and five-field Cron expressions with an IANA timezone.
+
+Definitions, locks, execution history, and results live in the private Studio
+TOS bucket under `veadk-studio/v1/users/{user_id}/cronjobs/{job_id}`. A derived
+minute index lives under `veadk-studio/v1/scheduler/cronjobs/due/{yyyyMMddHHmm}`
+so the scheduler never scans user namespaces.
+
+`veadk studio deploy` creates or updates two stateless VeFaaS functions. A
+scanner runs once per minute, copies the current due bucket into the durable
+`scheduler/cronjobs/ready/` queue, persists queued runs, and advances each
+schedule without waiting for Runtime execution. A separate asynchronous worker
+drains ready entries, invokes Runtime, and writes terminal results. The scanner,
+worker, and Studio BFF can therefore restart independently without losing work.
+
+Duplicate timer deliveries are deduplicated with immutable run IDs and TOS
+conditional writes; an ETag lock prevents concurrent executions of the same
+task across Studio replicas or worker instances. Ready entries are deleted only
+after a terminal result is persisted. The worker uses the function IAM role to
+read the Runtime's current endpoint and version. It does not store user tokens
+or AK/SK credentials.
+
+Manual runs are persisted with a `queued` status and placed in the next minute's
+due bucket, so they normally start within 60 seconds. This avoids losing a run
+when the current minute has already been scanned. When Studio is started with
+`veadk studio --vite`, the BFF starts independent local scan and execution
+loops; no separate local scheduler process is required.
+
 ## Agent usage statistics
 
 The `用量统计` tab on a deployed Agent records one invocation after a Studio

frontend/server/cronjobs/__init__.py

@@ -0,0 +1,59 @@
+# Copyright (c) 2025 Beijing Volcano Engine Technology Co., Ltd. and/or its affiliates.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+"""Durable Studio cronjob management domain."""
+
+from .repository import (
+    CronjobConflict,
+    CronjobNotFound,
+    Stored,
+    TosCronjobRepository,
+)
+from .routes import mount_routes
+from .schemas import (
+    CreateCronjobRequest,
+    Cronjob,
+    CronjobIdentity,
+    CronjobLock,
+    CronjobRun,
+    UpdateCronjobRequest,
+)
+from .service import (
+    CronjobAccessDenied,
+    CronjobAccessPolicy,
+    CronjobDuePublisher,
+    CronjobRunQueueUnavailable,
+    CronjobService,
+    OwnerOnlyAccessPolicy,
+)
+
+__all__ = [
+    "CreateCronjobRequest",
+    "Cronjob",
+    "CronjobAccessDenied",
+    "CronjobAccessPolicy",
+    "CronjobConflict",
+    "CronjobDuePublisher",
+    "CronjobIdentity",
+    "CronjobLock",
+    "CronjobNotFound",
+    "CronjobRun",
+    "CronjobRunQueueUnavailable",
+    "CronjobService",
+    "OwnerOnlyAccessPolicy",
+    "Stored",
+    "TosCronjobRepository",
+    "UpdateCronjobRequest",
+    "mount_routes",
+]