story-kit: done 321_story_whatsapp_htop_adaptation_for_no_edit_platforms
This commit is contained in:
@@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
name: "WhatsApp htop adaptation for no-edit platforms"
|
||||||
|
agent: coder-opus
|
||||||
|
---
|
||||||
|
|
||||||
|
# Story 321: WhatsApp htop adaptation for no-edit platforms
|
||||||
|
|
||||||
|
## User Story
|
||||||
|
|
||||||
|
As a project owner using WhatsApp, I want the htop command to work even though WhatsApp doesn't support message editing, so that I can monitor system load from any chat platform.
|
||||||
|
|
||||||
|
## Acceptance Criteria
|
||||||
|
|
||||||
|
- [ ] htop on WhatsApp sends a new message each update instead of editing
|
||||||
|
- [ ] Rate-limited to avoid spamming (e.g. one message per 15 seconds instead of every 5)
|
||||||
|
- [ ] Each new message replaces the previous one visually (includes a 'last updated' timestamp)
|
||||||
|
- [ ] htop stop still works to cancel the loop
|
||||||
|
- [ ] ChatTransport trait has a supports_editing() method so htop can adapt its behavior per platform
|
||||||
|
|
||||||
|
## Out of Scope
|
||||||
|
|
||||||
|
- TBD
|
||||||
Reference in New Issue
Block a user