Stabilization Day

Eleven commits. One theme: solidifying the foundation.

Tool Pipeline Cleanup

The tool execution chain had accumulated technical debt. We cleaned it up, removing bottlenecks and edge cases that were causing intermittent failures.

Scheduler & Scheduled Cards

Tools often need to run on schedules — daily summaries, periodic health checks, background jobs. We built the UI to display and manage scheduled tool invocations. Cards show what’s running, when it runs next, success/failure status, and let you trigger manually or adjust the schedule.

Documentation Cleanup

Cleaned up the architecture documentation, merged conflicting doc fixes from different branches, deleted the obsolete plan.md. The docs are now the source of truth again. Each module has clear documentation of its responsibility.

Database & Provider Fixes

Fixed state corruption when users switched between providers (e.g., Claude → GPT4). Resolved edge cases in the provider abstraction layer. Fixed parsing of tool invocations from model output.

The tool system feels more solid. The database is more reliable. Scheduling works smoothly. This is what sustainable development looks like — no big bang changes, just steady incremental progress toward stability.