67a458c491
- Move service.py -> application/service.py (SchedulerService class name unchanged; build_object_store / build_storage_http_client move along) - main.py imports schedule.application.service - Rewrite worker.py's lazy `from schedule.service import build_object_store` and test_worker.py's mock patch string targets — same class of bug as the test_janitor patch strings (silent no-op until the old file is deleted) - Delete flat service.py (orphaned; only docstring refs remain in orchestrator, cleaned up in stage 6) - Zero behavior change; schedule/pyproject.toml untouched Co-Authored-By: Claude <noreply@anthropic.com>
Schedule Executor
独立调度执行服务，内置 APScheduler。
- Cron 任务持久化到 MySQL 的
apscheduler_jobs表； - FastAPI Backend 创建运行记录和 Outbox 事件后，通过 HTTP 尝试立即推送；
- HTTP 推送失败时，Executor 继续轮询 MySQL
outbox_events，保证任务不会丢失； - Executor 负责 DAG 节点派发、稳定版本执行、重试、状态推进和结果回写；
- 不依赖 Redis，MySQL 是调度状态与幂等状态的唯一权威。