feat: move triggers/schedules to agent.ts (defineAgent)
Mechanical migration to the new persona-vs-agent split — triggers and cron schedules move from the persona into agent.ts via defineAgent({ triggers, schedules, handler }); personas keep integration connection config only.
Tracks/stacks on AgentWorkforce/workforce#175 (which ships defineAgent in @agentworkforce/{persona-kit,runtime,deploy}).
Draft because it is stacked on that unpublished release — import { defineAgent } will not resolve / typecheck here until the workforce packages publish. Each migrated agent.ts parses cleanly (esbuild transform verified).
🤖 Generated with Claude Code
Summary by cubic
Moved triggers and cron schedules from personas into agent.ts with defineAgent({ triggers, schedules, handler }) so agents own their automation. Updated docs and bumped @agentworkforce/{persona-kit,runtime} to ^3.0.39.
-
Refactors
- Migrated all agents (granola, linear, review, repo-hygiene, hn-monitor, spotify-releases, vendor-monitor) to
defineAgent; personas now only declare integration connections. - Declared agent-owned schedules/triggers (Linear issue/comment; GitHub PR lifecycle; Granola storage write; HN/Spotify/Vendor cron), removed a dead cron guard in granola, added the deploy bundle under
review/.workforce/build/pr-reviewer, and updated the README to clarifydefineAgentcovers triggers/schedules (dropped "watch").
- Migrated all agents (granola, linear, review, repo-hygiene, hn-monitor, spotify-releases, vendor-monitor) to
-
Dependencies
- Bumped
@agentworkforce/{persona-kit,runtime}to^3.0.39and refreshed the lockfile.
- Bumped