diff options
Diffstat (limited to 'docs/superpowers/specs')
| -rw-r--r-- | docs/superpowers/specs/2026-10-31-rule-apply-and-archive-design.md | 8 | ||||
| -rw-r--r-- | docs/superpowers/specs/2026-11-16-rule-move-design.md | 5 |
2 files changed, 12 insertions, 1 deletions
diff --git a/docs/superpowers/specs/2026-10-31-rule-apply-and-archive-design.md b/docs/superpowers/specs/2026-10-31-rule-apply-and-archive-design.md index 247cfd5..6a1af9c 100644 --- a/docs/superpowers/specs/2026-10-31-rule-apply-and-archive-design.md +++ b/docs/superpowers/specs/2026-10-31-rule-apply-and-archive-design.md @@ -215,3 +215,11 @@ the user looks at it. - **Relaxing `unread`.** Nothing asks for it. - **A dry-run list** of the affected messages. *Preview in list* already shows which mail a rule collects. + +## Addendum, 2026-11-16: rules that move (item 214) + +A rule may now carry `"move": "spam" | "trash"`. When Apply is built it must +honour that field by sending the matched ids through +`NotmuchWorker::moveMessages()` with the same tags Mark spam / Delete use +(minus `unread`, matching the hook), so the move lands on the undo stack. +The count in the confirmation names the move as well as the tag change. diff --git a/docs/superpowers/specs/2026-11-16-rule-move-design.md b/docs/superpowers/specs/2026-11-16-rule-move-design.md index 95bac9c..37dd51b 100644 --- a/docs/superpowers/specs/2026-11-16-rule-move-design.md +++ b/docs/superpowers/specs/2026-11-16-rule-move-design.md @@ -46,7 +46,10 @@ One optional field on a rule: - The "adds and removes nothing" check becomes "adds, removes and moves nothing": a move-only rule is valid. - An unknown value is an invalid rule in `TagRules::validate()` (the dialog - cannot write one). The Python reader logs it and ignores the `move` while + cannot write one). The C++ reader keeps a bad value from the file RAW in + `unknown` and still loads the rule, even when the move was its only action, + so a save writes it back rather than deleting it (the rule-id lesson in + `AGENTS.md`); a role chosen in the dialog replaces it. The Python reader logs it and ignores the `move` while still applying the rule's tags, since the tags are harmless and the hook must never guess a destination. |
