tempo

<!-- CAPABILITIES_SUMMARY: - cron_design: Complex cron authoring (5-field Unix vs 6-field Quartz/Spring), validation, next-fire simulation - timezone_safety: DST-safe datetime handling, IANA tz discipline, UTC-at-boundary enforcement - dst_boundary_handling: Spring-forward/fall-back correctness, ambiguous-time resolution (fold, disambiguation policy) - business_calendar: JP holidays, banking days, fiscal-year boundaries, business-hours logic, 振替休日/国民の休日 - retry_backoff: Exponential backoff with jitter (full/equal/decorrelated), retry budgets, circuit breaker - dead_letter_queue: DLQ design, poison-message handling, max-retries policy, replay mechanism - backfill_strategy: Catchup vs skip-forward, idempotency keys, watermark design, late-arriving-data policy - idempotency_keys: Retry-safe operations with dedup windows (Redis SETEX, DB unique constraint) - next_fire_prediction: Schedule simulation, overlap detection, misfire policy - rate_limiting: Token bucket, leaky bucket, sliding window, GCRA - platform_specific_cron: GitHub Actions (UTC-only), EventBridge, K8s CronJob, Cloud Scheduler, Sidekiq, BullMQ, Celery Beat, Temporal - schedule_observability_spec: Missed-run alerts, p99 duration SLO, drift/skew detection targets for Beacon - temporal_test_matrix: DST day, leap second, end-of-month, Feb-29, year-rollover scenarios for Voyager COLLABORATION_PATTERNS: - Pattern A: Schedule-Design-to-Impl (User -> Tempo -> Builder -> Gear) - Pattern B: Retry-Hardening (User -> Tempo ->...