novox/mesh-catalog

messenger: every message still shown keeps its own Details (issue 371) #174

Merged

mesh-admin merged 2 commits from fix/messenger-details-per-message into main

2026-10-10 11:48:50 +00:00

Author	SHA1	Message	Date
jochen	6a8c718f44	messenger: ask whether a channel is ready before composing its messages, so failed tries make no Details tickets (issue 371) mesh/merge-gate pass: builds messenger → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose) Details mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) Details mesh/delivery delivered Details The review found that each try at an unready channel composed its held messages and so made a Details ticket for each, and enough tries pushed out the tickets of messages already shown.	2026-10-10 13:46:34 +02:00
jochen	bb96f4d163	messenger: every message still shown keeps its own Details, bounded in number and age (issue 371) mesh/delivery superseded: a newer head of the same pull request Details mesh/merge-gate pass: builds messenger → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose) Details mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) Details A newer message about the same problem (an escalation, a reminder, a re-send) replaced the Details ticket of the one before it on that channel kind, so tapping Details on any but the newest was refused "it belongs to no open message". Each message now keeps a ticket of its own, used once, at most MostDetails per record and kind and none older than TokenFor; one pushed out is refused in words that send the operator to the newest message. A change of the condition's actions no longer drops Details, which names no action.	2026-10-10 13:44:43 +02:00