Summary
doc/api/sections/my_notifications.md (codified by BC3 #11628) documents the BC5 bubble-up surface that spec/api-gaps/memories-emptied-regression.md explicitly defers to a separate additive PR. That entry settles the subtractive memories: [] delta; this issue tracks the deferred additions.
Missing surface
bubble_ups_count / scheduled_bubble_ups_count — required top-level integer counts on GET /my/readings.json (present independent of the limit_bubble_ups cap, and even when the scheduled_bubble_ups array is omitted).limit_bubble_ups — optional boolean query param; true caps bubble_ups at 2 current items and omits the scheduled_bubble_ups key.GET /my/readings/bubble_ups.json — a new operation returning a paginated bare array (50/page, Link-header pagination, page param) of current bubble-ups first (most recently bubbled up) then scheduled (scheduled time). Same Notification item shape.
Absorption (this issue's PR — PR-3 of the post-#401 program)
- Add the required counts +
limit_bubble_ups to the existing GetMyNotifications* shapes.
- Add the
GetBubbleUps operation (tagged, service-listed) with a Go wrapper (MyNotificationsService.BubbleUps, Link-following) + a non-breaking WithLimitBubbleUps() option on Get.
- Go tests: multi-page Link-following pagination (with
X-Total-Count + ordering), single-page, and limit_bubble_ups=true → scheduled_bubble_ups omitted with counts preserved.
- New
bubble-ups-surface.md registry entry; memories-emptied-regression.md left intact (its pairwise-retirement scope is the subtractive delta).
Coordination record for the registry scheme; code ships in the linked PR.
Summary
doc/api/sections/my_notifications.md(codified by BC3 #11628) documents the BC5 bubble-up surface thatspec/api-gaps/memories-emptied-regression.mdexplicitly defers to a separate additive PR. That entry settles the subtractivememories: []delta; this issue tracks the deferred additions.Missing surface
bubble_ups_count/scheduled_bubble_ups_count— required top-level integer counts onGET /my/readings.json(present independent of thelimit_bubble_upscap, and even when thescheduled_bubble_upsarray is omitted).limit_bubble_ups— optional boolean query param;truecapsbubble_upsat 2 current items and omits thescheduled_bubble_upskey.GET /my/readings/bubble_ups.json— a new operation returning a paginated bare array (50/page, Link-header pagination,pageparam) of current bubble-ups first (most recently bubbled up) then scheduled (scheduled time). SameNotificationitem shape.Absorption (this issue's PR — PR-3 of the post-#401 program)
limit_bubble_upsto the existingGetMyNotifications*shapes.GetBubbleUpsoperation (tagged, service-listed) with a Go wrapper (MyNotificationsService.BubbleUps, Link-following) + a non-breakingWithLimitBubbleUps()option onGet.X-Total-Count+ ordering), single-page, andlimit_bubble_ups=true→scheduled_bubble_upsomitted with counts preserved.bubble-ups-surface.mdregistry entry;memories-emptied-regression.mdleft intact (itspairwise-retirement scope is the subtractive delta).Coordination record for the registry scheme; code ships in the linked PR.