Force sending Telegram notification upon stopping for user input
This commit is contained in:
@@ -562,7 +562,7 @@ Present summary:
|
||||
**Branch:** implement/<plan-folder-name> (merged and deleted)
|
||||
```
|
||||
|
||||
### Phase 9: Telegram Completion Notification (MANDATORY)
|
||||
### Phase 9: Telegram Notification (MANDATORY)
|
||||
|
||||
Resolve the Telegram notifier helper from the installed OpenCode skills directory:
|
||||
|
||||
@@ -579,9 +579,10 @@ fi
|
||||
```
|
||||
|
||||
Rules:
|
||||
- Telegram is the only supported completion notification path. Do not use desktop notifications, `say`, email, or any other notifier.
|
||||
- Telegram is the only supported notification path. Do not use desktop notifications, `say`, email, or any other notifier.
|
||||
- Notification failures are non-blocking, but they must be surfaced to the user.
|
||||
- If Telegram is not configured, state that no completion notification was sent.
|
||||
- Before stopping for any user interaction, approval, or manual decision, send a Telegram summary first if configured.
|
||||
- If Telegram is not configured, state that no Telegram notification was sent.
|
||||
|
||||
## Tracker Discipline (MANDATORY)
|
||||
|
||||
@@ -615,4 +616,4 @@ Note: Commit hashes are backfilled into story Notes after the milestone commit (
|
||||
- [ ] Final test suite passes
|
||||
- [ ] Worktree branch merged to parent and worktree deleted
|
||||
- [ ] Story tracker updated with final status
|
||||
- [ ] Telegram completion notification attempted if configured
|
||||
- [ ] Telegram notification attempted if configured
|
||||
|
||||
Reference in New Issue
Block a user