chore: release v0.35.1

.claude/rules/runner-development.md

@@ -34,6 +34,10 @@ factory.completed_ok(answer=..., resume=token, usage=...)
 
 Do NOT construct `StartedEvent`, `ActionEvent`, `CompletedEvent` dataclasses directly.
 
+## RunContext trigger_source (#271)
+
+`RunContext` has a `trigger_source: str | None` field. Dispatchers set it to `"cron:<id>"` or `"webhook:<id>"`; `runner_bridge.handle_message` seeds `progress_tracker.meta["trigger"] = "<icon> <source>"`. Engine `StartedEvent.meta` merges over (not replaces) the trigger key via `ProgressTracker.note_event`. Runners themselves should NOT set `meta["trigger"]`; that's reserved for dispatchers.
+
 ## Session locking
 
 - `SessionLockMixin` provides `lock_for(token) -> anyio.Semaphore`

.claude/rules/telegram-transport.md

@@ -59,6 +59,22 @@ Agents write files to `.untether-outbox/` during a run. On completion, `outbox_d
 
 `progress_persistence.py` tracks active progress messages in `active_progress.json`. On startup, orphan messages from a prior instance are edited to "⚠️ interrupted by restart" with keyboard removed.
 
+## Telegram update_id persistence (#287)
+
+`offset_persistence.py` persists the last confirmed Telegram `update_id` to `last_update_id.json` (sibling to config). On startup, `poll_updates` loads the saved offset and passes `offset=saved+1` to `getUpdates` so restarts don't drop or re-process updates within Telegram's 24h retention window. Writes are debounced (5s interval, 100-update cap) via `DebouncedOffsetWriter` — see its docstring for the crash/replay tradeoff. Flush happens automatically in the `poll_updates` finally block.
+
+## TelegramBridgeConfig hot-reload (#286)
+
+`TelegramBridgeConfig` is unfrozen (slots preserved) as of rc4. `update_from(settings)` applies a reloaded `TelegramTransportSettings` to the live config; `handle_reload()` in `loop.py` calls it and refreshes the two cached copies in `TelegramLoopState`. `route_update()` reads `cfg.allowed_user_ids` live so allowlist changes take effect on the next message. Restart-only keys (`bot_token`, `chat_id`, `session_mode`, `topics`, `message_overflow`) still warn with `restart_required=true`.
+
+## sd_notify (#287)
+
+`untether.sdnotify.notify(message)` sends `READY=1`/`STOPPING=1` to systemd's notify socket (stdlib only — no dependency). `NOTIFY_SOCKET` absent → no-op False. `poll_updates` sends `READY=1` after `_send_startup` succeeds; `_drain_and_exit` sends `STOPPING=1` at drain start. Requires `Type=notify` + `NotifyAccess=main` in the systemd unit (see `contrib/untether.service`).
+
+## /at command (#288)
+
+`telegram/at_scheduler.py` is a module-level holder for the task group + `run_job` closure; `install()` is called from `run_main_loop` once both are available. `AtCommand.handle` calls `schedule_delayed_run(chat_id, thread_id, delay_s, prompt)` which starts an anyio task that sleeps then dispatches. Pending delays tracked in `_PENDING`; `/cancel` drops them via `cancel_pending_for_chat(chat_id)`. Drain integration via `at_scheduler.active_count()`. No persistence — restart cancels all pending delays (documented in issue body).
+
 ## Plan outline rendering
 
 Plan outlines render as formatted Telegram text via `render_markdown()` + `split_markdown_body()`. Approval buttons (✅/❌/📋) appear on the last outline message. Outline and notification messages are cleaned up on approve/deny via `_OUTLINE_REGISTRY`.

.claude/rules/testing-conventions.md

@@ -60,14 +60,14 @@ Integration tests are automated via Telegram MCP tools by Claude Code during the
 
 ### Test chats
 
-| Chat | Chat ID |
-|------|---------|
-| `ut-dev-hf: claude` | 5171122044 |
-| `ut-dev-hf: codex` | 5116709786 |
-| `ut-dev-hf: opencode` | 5020138767 |
-| `ut-dev-hf: pi` | 5276373372 |
-| `ut-dev-hf: gemini` | 5152406011 |
-| `ut-dev-hf: amp` | 5064468679 |
+| Chat | Chat ID | Bot API chat_id |
+|------|---------|-----------------|
+| Claude Code | `5284581592` | `-5284581592` |
+| Codex CLI | `4929463515` | `-4929463515` |
+| OpenCode | `5200822877` | `-5200822877` |
+| Pi | `5156256333` | `-5156256333` |
+| Gemini CLI | `5207762142` | `-5207762142` |
+| AMP CLI | `5230875989` | `-5230875989` |
 
 ### Pattern
 
@@ -113,3 +113,9 @@ All integration test tiers are fully automatable by Claude Code.
 | `test_loop_coverage.py` | Update loop edge cases, message routing, shutdown |
 | `test_exec_runner.py` | Event tracking, ring buffer, PID in StartedEvent meta |
 | `test_runner_utils.py` | Error formatting, drain_stderr, stderr sanitisation |
+| `test_trigger_server.py` | Webhook HTTP server, multipart, rate limit burst, fire-and-forget dispatch |
+| `test_trigger_actions.py` | file_write (multipart short-circuit), http_forward (SSRF), notify_only |
+| `test_trigger_cron.py` | Cron expression matching, timezone conversion, step validation |
+| `test_trigger_settings.py` | CronConfig/WebhookConfig/TriggersSettings validation, timezone |
+| `test_trigger_ssrf.py` | SSRF blocking (IPv4/IPv6, DNS rebinding, allowlist) |
+| `test_trigger_fetch.py` | Cron data-fetch (HTTP, file read, parse modes, failure) |

.claude/skills/untether-architecture/SKILL.md

@@ -270,6 +270,31 @@ chat_id = -1001234567890   # optional per-project chat
 - `/ctx set <project>` binds a chat context
 - Project alias used as directive prefix: `/untether fix the bug`
 
+## Trigger system
+
+Triggers let external events or schedules start agent runs automatically. Opt-in via `[triggers] enabled = true`.
+
+### Cron
+
+`run_cron_scheduler()` ticks every minute, checking each `[[triggers.crons]]` entry against the current time via `cron_matches()` (5-field standard syntax). Per-cron `timezone` or global `default_timezone` converts UTC to local wall-clock time via `_resolve_now()` + `zoneinfo.ZoneInfo`. DST transitions handled automatically. `last_fired` dict prevents double-firing within the same minute.
+
+### Webhooks
+
+`run_webhook_server()` runs an aiohttp server. Each `[[triggers.webhooks]]` maps a URL path to auth (bearer/HMAC-SHA256/SHA1) + prompt template with `{{field.path}}` substitutions. Rate-limited per-webhook and globally.
+
+### Dispatch
+
+Both crons and webhooks feed into `TriggerDispatcher.dispatch_cron()`/`dispatch_webhook()` → sends a notification message to Telegram (`⏰`/`⚡`) → calls `run_job()` with the prompt, threading under the notification.
+
+### Key files
+
+- `triggers/cron.py` — cron parser, timezone-aware scheduler
+- `triggers/settings.py` — `CronConfig`, `WebhookConfig`, `TriggersSettings` (pydantic)
+- `triggers/dispatcher.py` — notification + `run_job()` bridge
+- `triggers/server.py` — aiohttp webhook server
+- `triggers/auth.py` — bearer/HMAC verification
+- `triggers/templating.py` — `{{field.path}}` prompt substitution
+
 ## Key conventions
 
 - Python 3.12+, anyio for async, msgspec for JSONL parsing, structlog for logging

.github/workflows/ci.yml

@@ -183,7 +183,7 @@ jobs:
           path: dist/
 
       - name: Publish to TestPyPI
-        uses: pypa/gh-action-pypi-publish@ed0c53931b1dc9bd32cbe73a98c7f6766f8a527e # v1.13.0
+        uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0
         with:
           repository-url: https://test.pypi.org/legacy/
           packages-dir: dist/

.github/workflows/notify-website.yml

@@ -14,9 +14,11 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Trigger website rebuild
+        env:
+          TAG_NAME: ${{ github.event.release.tag_name }}
         run: |
           curl -s -X POST \
             -H "Accept: application/vnd.github+json" \
             -H "Authorization: Bearer ${{ secrets.WEBSITE_DISPATCH_TOKEN }}" \
             https://api.github.com/repos/littlebearapps/littlebearapps.com/dispatches \
-            -d '{"event_type":"release-published","client_payload":{"repo":"untether","tag":"${{ github.event.release.tag_name }}"}}'
+            -d "$(jq -n --arg tag "$TAG_NAME" '{"event_type":"release-published","client_payload":{"repo":"untether","tag":$tag}}')"

.github/workflows/release.yml

@@ -91,7 +91,7 @@ jobs:
           path: dist/
 
       - name: Publish package distributions to PyPI
-        uses: pypa/gh-action-pypi-publish@ed0c53931b1dc9bd32cbe73a98c7f6766f8a527e # v1.13.0
+        uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0
         with:
           packages-dir: dist/
           skip-existing: true
@@ -119,7 +119,7 @@ jobs:
           path: dist/
 
       - name: Create GitHub release and upload artifacts
-        uses: softprops/action-gh-release@a06a81a03ee405af7f2048a818ed3f03bbf83c7b # v2.5.0
+        uses: softprops/action-gh-release@b4309332981a82ec1c5618f44dd2e27cc8bfbfda # v3.0.0
         with:
           generate_release_notes: true
           files: |