diff options
Diffstat (limited to 'docs/superpowers')
| -rw-r--r-- | docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md | 12 |
1 files changed, 10 insertions, 2 deletions
diff --git a/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md b/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md index f9f8c53..00a7f76 100644 --- a/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md +++ b/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md @@ -4904,8 +4904,16 @@ Fixed on the `rule-builder` branch as part of item 76, with regression test. It fails against the unfixed code. **Damage in the field, and the repair.** The live rules file had exactly one -casualty: the account rule sitting first in the list, with both `query` and -`add` empty while every sibling account rule was intact. +casualty: the account rule sitting first in the list, with its `query`, its +`add` and its `note` all empty while every sibling account rule was intact. + +**The note was missed on the first pass of the repair**, because the shell +backup was read for the tagging command and the note comes from the comment +block ABOVE it, which the migration had given to all five account rules +alike. The user spotted the gap. `applyEditsToCurrentRule()` writes every +field, so every field is equally exposed: repair work here must check the +whole rule, not the fields that first drew attention. Restored from the four +siblings, which carry byte-identical notes. Restored from `post-new.shell-backup`, which item 44's migration kept, and verified by loading the file through mailctl's own reader: 17 rules, correct scoping. The rule had stopped tagging, but only one message had arrived in the |