Release: develop -> main - #128
Merged
Merged
Conversation
* 01a0923c - Route forum replies to Notifications, not chat A living-room reply now writes a notification for the parent author and pushes /notifications. It no longer copies into the private Messages thread. * 01a0923c - Document the Notifications store in CONTRIBUTING List notification modules, tests, schema, and DATABASE_URL migrate alongside conversation and push. * 01a0923c - Name notification migrate in CONTRIBUTING boot lists db_change attach follows migrateNotificationSchema; the default-boot unreachable-export list includes PostgresNotificationStore. * 01a0923c - Format CONTRIBUTING.md with Prettier CI lint failed on the env-var table column widths after the Notifications store was added to DATABASE_URL. * 01a0923c - Stamp notification read_at in one UPDATE Return the row from UPDATE … RETURNING so a second parallel mark-read cannot invent a readAt that is not stored. * 01a0923c - Align notification TSDoc and SPEC unreadCount Document notifyForumReply returns/throws and make the GET /notifications example unreadCount match a null readAt. * 01a0923c - Document reply push and inbound notify in JSDoc Clarify enqueueReplyPush tag vs URL, inbound notifyForumReply on the worker tick, and journey 7 as Notifications plus Web Push. * 01a0923c - Say inbound notify is optional per store Worker tick JSDoc now matches the call: notification row and push enqueue only when those stores are wired. * 01a0923c - Word optional notification and push stores Docs now match the code: a reply notify writes a row only when the notification store is set, and pushes only when the push store is set. * 01a0923c - Say the booted process always has notify stores SPEC, handbook, and CONCEPT describe the HTTP product: memory or Postgres notification and push stores are always present after boot. * 01a0923c - Store the notification row before enqueueing the reply push Journey 7 now matches notifyForumReply: persist first, then targeted push. CONTRIBUTING and CONCEPT table padding follow Prettier after the debug-messages rebase. * 01a0923c - Document getByIdForRecipient and markRead returns Port and both stores now have @returns on the recipient lookup and mark-read methods, matching create/list/unreadCount. --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
* 01a0949e - Require a live forum post before spend invoices GET /invoices/posted reports whether a Lightning Address has a live non-profile forum message. POST /invoices returns 403 Forum post required after the passkey check, before LNURL. * 01a0949e - Report hasPosted on GET /me Owner JSON includes whether the account has a live non-profile forum post, using the same lookup as spend invoices. * 01a0949e - Format CONTRIBUTING after the posted-token row Prettier reflows the SPEND_API_TOKEN table cell after adding GET /invoices/posted next to the notifications DATABASE_URL row. --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
TaprootFreak
approved these changes
Sep 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automatic Release PR
Commits: 1 new commit(s)