chore: Run pnpm format:fix.

docs/experiments/plans/cron-add-hardening.md

@@ -8,9 +8,11 @@ last_updated: "2026-01-05"
 # Cron Add Hardening & Schema Alignment
 
 ## Context
+
 Recent gateway logs show repeated `cron.add` failures with invalid parameters (missing `sessionTarget`, `wakeMode`, `payload`, and malformed `schedule`). This indicates that at least one client (likely the agent tool call path) is sending wrapped or partially specified job payloads. Separately, there is drift between cron provider enums in TypeScript, gateway schema, CLI flags, and UI form types, plus a UI mismatch for `cron.status` (expects `jobCount` while gateway returns `jobs`).
 
 ## Goals
+
 - Stop `cron.add` INVALID_REQUEST spam by normalizing common wrapper payloads and inferring missing `kind` fields.
 - Align cron provider lists across gateway schema, cron types, CLI docs, and UI forms.
 - Make agent cron tool schema explicit so the LLM produces correct job payloads.
@@ -18,11 +20,13 @@ Recent gateway logs show repeated `cron.add` failures with invalid parameters (m
 - Add tests to cover normalization and tool behavior.
 
 ## Non-goals
+
 - Change cron scheduling semantics or job execution behavior.
 - Add new schedule kinds or cron expression parsing.
 - Overhaul the UI/UX for cron beyond the necessary field fixes.
 
 ## Findings (current gaps)
+
 - `CronPayloadSchema` in gateway excludes `signal` + `imessage`, while TS types include them.
 - Control UI CronStatus expects `jobCount`, but gateway returns `jobs`.
 - Agent cron tool schema allows arbitrary `job` objects, enabling malformed inputs.
@@ -53,5 +57,6 @@ See [Cron jobs](/automation/cron-jobs) for the normalized shape and examples.
 - Manual Control UI smoke: add a cron job per provider + verify status job count.
 
 ## Open Questions
+
 - Should `cron.add` accept explicit `state` from clients (currently disallowed by schema)?
 - Should we allow `webchat` as an explicit delivery provider (currently filtered in delivery resolution)?

docs/experiments/plans/group-policy-hardening.md

@@ -3,6 +3,7 @@ summary: "Telegram allowlist hardening: prefix + whitespace normalization"
 read_when:
   - Reviewing historical Telegram allowlist changes
 ---
+
 # Telegram Allowlist Hardening
 
 **Date**: 2026-01-05  
@@ -25,7 +26,7 @@ All of these are accepted for the same ID:
 
 - `telegram:123456`
 - `TG:123456`
-- ` tg:123456 `
+- `tg:123456`
 
 ## Why it matters