Mnovich/temporal scheduler

[Kvadratni]

✅ What We Accomplished

1. Complete Rust Integration - Built a full TemporalScheduler that communicates with the Go Temporal service via HTTP
2. Standalone Job Executor - Created goose-scheduler-executor binary for executing individual recipes
3. Trait Abstraction - Implemented SchedulerTrait for seamless switching between schedulers
4. Factory Pattern - Added SchedulerFactory for environment-based scheduler selection
5. Comprehensive Testing - Created integration test suite that validates all components
6. Complete Documentation - Detailed architecture, usage, and implementation guides

🏗️ Architecture Implemented

┌─────────────────┐    ┌─────────────────┐    ┌─────────────────┐
│   Rust Code     │    │  Temporal Go    │    │  Temporal CLI   │
│                 │    │    Service      │    │    Server       │
│ SchedulerFactory│◄──►│                 │◄──►│                 │
│ TemporalSched   │    │ HTTP API        │    │ Dev Server      │
│                 │    │ Workflows       │    │ SQLite DB       │
│                 │    │ Activities      │    │ Web UI          │
└─────────────────┘    └─────────────────┘    └─────────────────┘
         │
         ▼
┌─────────────────┐
│ goose-scheduler │
│   -executor     │
│                 │
│ Standalone      │
│ Job Runner      │
└─────────────────┘

🚀 Usage

# Environment configuration
export GOOSE_SCHEDULER_TYPE=temporal  # Use Temporal scheduler
export GOOSE_SCHEDULER_TYPE=legacy    # Use legacy scheduler (default)

// Rust code integration
let scheduler = SchedulerFactory::create(storage_path).await?;
scheduler.add_scheduled_job(job).await?;
scheduler.list_scheduled_jobs().await?;
scheduler.run_now("job-id").await?;

📊 Key Benefits

• 🔒 Reliability: Jobs survive process restarts via Temporal persistence
• 📊 Observability: Rich monitoring via Temporal Web UI
• 📈 Scalability: Handle thousands of scheduled jobs
• 🔧 Maintainability: Clean separation of concerns
• 🔄 Drop-in Replacement: Same interface as legacy scheduler

🧪 Testing Status

All integration tests pass successfully:

• ✅ Prerequisites validation
• ✅ Library compilation
• ✅ Trait abstraction
• ✅ Executor functionality
• ✅ Full workspace build

[Kvadratni]

.bundle-windows

[spencrmartin]

For the agent space if we could prevent the secondary task of creating a schedule from recipe taking over the primary JTBD in this space that would be great>

If we could follow the cash modal/modal styling we've been using with segmented controller for source

Secondary button (pill) to avoid new CTA style (non rounded edges)

We may opt to just cut the "existing schedules" section for the empty state

Lets add some assistive helper secondary text on the main schedules page

Change to

Schedules
Create or manage scheduled tasks or actions

[spencrmartin]

Instead of all the icons in the card lets go popover via a 3 dot

[Kvadratni]

all comments addressed