aboutsummaryrefslogtreecommitdiffstats
path: root/docs/superpowers/plans
diff options
context:
space:
mode:
Diffstat (limited to 'docs/superpowers/plans')
-rw-r--r--docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md23
1 files changed, 22 insertions, 1 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 cc74be9..323af39 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
@@ -144,7 +144,7 @@ taking that too literally.
| 204 | No recipient completion, in the composer or the query bar | workflow | S | **done** 2026-09-24, shipped, built via subagent-driven-development, `3303c78..7454096`. `ContactStore` over the vdirsyncer vCard 3.0 directory feeds one shared `QCompleter` for the composer's To/Cc/Bcc and the query bar's `from:`/`to:`. Hand-tested and confirmed. One review fix (control-character/RFC 5322 sanitisation of `FN`) landed and was re-reviewed clean. Section in the closed file |
| 205 | Contacts can be read but not edited from the app | workflow | M | open, 2026-09-18, from 72's split, **asked for by the user** while settling 204. Writing a vdir, so it shares the write-during-sync question with 206 and the fold/escape rules with 204's parser. Its write-during-sync question is answered by 206's spec, § Writing: the same writer and stale check serve a vCard. Needs a brainstorm of its own |
| 206 | No calendar: events cannot be viewed, added or edited | workflow | L | **done** 2026-09-29, shipped in 0.30.0, built via subagent-driven-development on branch calendar and merged. Month and Agenda views, a side pane that edits, undoable create/edit/delete over the vdirsyncer vdir. Hand-tested and confirmed; three hand-test fixes (cell colour flood, pane hidden while empty, Escape closes it). Writing a `VALARM` from the edit form was raised and deferred by the user. Section in the closed file |
-| 207 | An invitation cannot be accepted, refused or sent | workflow | M | open, 2026-09-18, from 72's split, **asked for by the user**: "as it is today I don't have a way of accepting an invitation." `text/calendar` in the pane, an iMIP reply through the existing `send_command`. **Blocked on 206**, which owns the calendar it writes to |
+| 207 | An invitation cannot be accepted or refused | workflow | M | open, designed 2026-11-16: `specs/2026-11-16-receiving-invitations-design.md`. RECEIVING only, split from the original 207 at the user's choice; sending is 216. A native invitation bar in `MessageView`, the target calendar mapped per account, Accept/Tentative/Decline sent through the countdown with a "...with note" composer route, the calendar written only after the reply sends, organiser updates and cancels applied by a button |
| 208 | No way to add a new correspondent to the contacts | workflow | ? | open, 2026-09-18, **asked for by the user** while settling 204: an "add to contacts" button on mail from someone not in the store. Writes a vcard, so it lands on 205's writer rather than 204's reader. **Needs a brainstorm when picked up** |
| 209 | The calendar has no Week view | presentation | M | open, from 206's brainstorm. The occurrence list is the seam: a new painter over CalendarItem, no store change |
| 210 | A repeating event cannot be edited "this and following" | workflow | S-M | open, from 206's brainstorm. Splits a series into two files, divides EXDATEs and overrides, shifts moved RECURRENCE-IDs, converts COUNT; see the spec's Out of scope |
@@ -153,6 +153,7 @@ taking that too literally.
| 213 | A rule removing `inbox` is skipped whole by the hook, so promo mail arrives untagged | defect | S-M | open, designed: same spec, Part B. Optional per-rule `allow_archive`, both readers, no version bump; `unread` stays refused; the dialog warns about rules the hook will skip |
| 214 | A rule can tag mail spam but cannot move it to the spam or trash folder | workflow | M | **done** 2026-11-16, unreleased, on `rule-move`. Spec: `specs/2026-11-16-rule-move-design.md`. The nesting assumption held: `notmuch new --no-hooks` runs inside `post-new`. Review fixes: a bad `move` is kept raw rather than dropped (the rule-id lesson), a nested account without the role resolves to itself, and `_quote` doubles quotes (it never matched an id holding one, on the carve-out path too). Section in the closed file. Original note: Optional `move` field, `spam` or `trash` (an account role, never a folder name), both readers, no version bump; the hook moves on arrival, strips `inbox`, keeps `unread`; Apply (212) inherits it later. First task: verify `notmuch new` can run inside `post-new` |
| 215 | Archive, Restore and the Inbox filter lost their icons, and three icon tests fail | defect | S | open, 2026-11-16, found by the full suite while building 214. The icon names (`mail-archive`, `edit-undelete`, `mail-inbox`) exist in no installed theme: not candy-icons, and not breeze-dark, breeze, Adwaita or hicolor, which it inherits. Breeze was last updated 2026-11-05/11. Needs fallback names, the second slot `kThemeIcons` already has; the tests also read the DESKTOP theme, so the suite's result depends on the machine |
+| 216 | An invitation cannot be sent, and replies to one are not applied | workflow | M | open, 2026-11-16, split from 207. Editing an event's attendee list, sending `METHOD:REQUEST` through `MessageBuilder`, and applying the `METHOD:REPLY`s that come back to the stored event's `PARTSTAT`s. Builds on 207's `Invitation` parsing and calendar-part support |
| 73 | This backlog is past four thousand lines | maintenance | S | **done** 2026-08-13; 5056 lines to 578, closed sections moved to `2026-08-03-post-0.1.0-usability-closed.md` |
| 74 | "Searching..." keeps claiming a query is running while rows are already arriving | feedback | XS | **done** 2026-08-15, unreleased. The status-bar half only: the bar now counts threads per batch. The cold-cache delay itself was measured in 2026-08-11 and is not fixable here |
| 75 | The tagging rules window forgets its size and its column widths | persistence | S | **done** 2026-08-13, shipped in 0.17.0. The window-kind question is left open, see the closed-items file |
@@ -1764,3 +1765,23 @@ packages, which is how a system update broke them with no code change. Item 199
(ship our own icon set) would remove that dependency for the panes, but the
chrome deliberately stays on the system theme, so this item stands on its own.
+## 216. An invitation cannot be sent, and replies to one are not applied
+
+**Observed.** Split from 207 on 2026-11-16, when the user chose to design the
+receiving half first. The original 207 note covered both: "Sending an invite
+is the same builder with a `METHOD:REQUEST` and an attendee list."
+
+**Cause.** The calendar's attendee list is read-only (206's decision 6) and
+nothing builds or reads `METHOD:REQUEST` / `METHOD:REPLY`.
+
+**Approach.** Three parts: an attendee editor in `EventPane` for events the
+user organises; a send of `METHOD:REQUEST` to every attendee on save, through
+the per-account `send_command`; and an invitation-bar state for an incoming
+`REPLY` that updates that attendee's `PARTSTAT` in the stored event. Builds on
+207's parsing and on `OutgoingMessage::calendarPart`.
+
+**Constraints.** Adding an attendee is inviting them, so a save that sends
+mail needs the countdown, like a reply. A `REPLY` comes from a stranger and
+may name an attendee the event does not have: apply only to an existing
+attendee, never add one.
+