#21485: feat(cron): add direct-text flag to deliver text message directly [AI-assisted]

## Summary - Problem: add direct-text flag to deliver text message directly - Why it matters: For text-only results, cron uses the subagent announce flow to deliver a user-facing update rather than raw output. This path intentionally asks the main agent to “convert the result into your normal assistant voice”, which tends to summarize. - What changed: add direct-text flag to deliver text message directly, skip subagent announce flow - What did NOT change (scope boundary): ## AI-assisted - Prompt: add a flag to delivers text payloads directly without the announce conversion path ## Change Type (select all) - [ ] Bug fix - [x ] Feature - [ ] Refactor - [ ] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [x ] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [ ] Memory / storage - [ ] Integrations - [ ] API / contracts - [ ] UI / DX - [ ] CI/CD / infra ## Security Impact (required) - New permissions/capabilities? (`No`) - Secrets/tokens handling changed? (`No`) - New/changed network calls? (`No`) - Command/tool execution surface changed? (`No`) - Data access scope changed? (`No`) - If any `Yes`, explain risk + mitigation: ## Human Verification (required) What you personally verified (not just CI), and how: - Verified scenarios: - Edge cases checked: - What you did **not** verify: ## Compatibility / Migration - Backward compatible? (`No`) - Config/env changes? (`Yes`) - Migration needed? (`No`) - If yes, exact upgrade steps: <!-- greptile_comment --> <h3>Greptile Summary</h3> Added `directText` flag to cron delivery configuration allowing text payloads to bypass the announce conversion path and be delivered directly to messaging channels. **Key changes:** - Added optional `directText` boolean field to `CronDelivery` type and schema - Implemented CLI flags `--direct-text` in both `cron add` and `cron edit` commands - Modified delivery routing logic in `run.ts` to check `directText` flag and route accordingly - Updated merge logic in `jobs.ts` to preserve `directText` field during job updates **How it works:** When `directText` is true and text content exists, the cron job delivers the raw text output directly via `deliverOutboundPayloads` instead of routing through the announce flow (which typically summarizes the output). Structured payloads (media, channel data) continue to use direct delivery regardless of this flag. <h3>Confidence Score: 4/5</h3> - Safe to merge with one minor style suggestion for consistency - Implementation follows existing patterns (similar to `bestEffort` flag), adds proper type definitions, schema validation, and CLI integration. One minor style inconsistency exists in type casting approach compared to similar functionality. No logical errors or security concerns identified. - No files require special attention - all changes are straightforward feature additions _{Last reviewed commit: 22c044f} <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->