mesh-issues: carry each value the issues bucket kept, read through the runtime's history, so the log begins with all the bucket still knew (hq ADR 0300 §6, ADR 0307)

modules/mesh-issues/README.md

@@ -272,9 +272,11 @@ below. Until then a `list` reads the bucket and a write carries the issue it cha
 for every issue the bucket holds with no `folded`, each value the bucket still keeps of it, oldest first, is
 appended as a `carried` operation holding the whole issue, and the fold written. It is idempotent: an issue the
 log already begins is not carried again (where the bucket holds something other than its fold — written by an
-instance from before the switch — that value is carried as one more operation). The runtime offers no read of a
-key's older values today, so the carry takes each issue's current value and says so in its start line; with a
-store that reads them, it takes every one. It runs on start rather than as a verb because it must precede every
+instance from before the switch — that value is carried as one more operation). The values kept are read through
+the runtime's `mesh/state.history` (hq ADR 0307, the SDK's `State("issues").History`), oldest first; a deletion
+among them is passed over and counted in the start line, since the tracker never deletes an issue and every
+value after one holds the issue whole. A store that reads no history gives each issue's current value alone,
+and the start line says so. It runs on start rather than as a verb because it must precede every
 write, and a verb could be called late or never.
 
 **In memory** the tracker holds every folded issue, kept current by the watch and its own writes, and a
@@ -365,5 +367,7 @@ open refused at validation taking no number, an append failing after the number
 failure, an emptied bucket restored exactly by the fold on start, a bucket behind its log catching up, the
 counter raised to the log, each write saying its event beside its one operation, `before` paging 530 issues
 without a gap or a repeat, a ranked search with the index rebuilt on start and kept current by the watch, and
-the carry carrying each value kept, oldest first, once. Over the bus, the stream the controller makes holds one
+the carry carrying each value kept, oldest first, once, passing over a deletion among them. Over the bus, a
+write to an issue the bucket kept before the switch carries its three kept values first, read through the
+runtime's history. Over the bus, the stream the controller makes holds one
 operation per change of `TestAnIssueIsOpenedNotedLinkedMovedAndListedOverTheBus`.