v0.5.0

• @lowdefy/modules-mongodb-layout: ### Patch Changes

• #55 eb4971a Thanks @Gervwyk! - Fetch the notifications unread-count request on mount so the bell badge actually renders.

  The page component already wired notifications/unread-count-request into its requests array (when hide_notifications is false), and notification-config.yaml reads the count via _request: notifications_unread_count.0.total. But the _request operator only reads previously-fetched data — it does not auto-trigger a fetch — and the layout never invoked the request, so the count stayed null, fell through _if_none to 0, and the badge never appeared regardless of how many unread notifications a user had.

  onMountAsync runs the fetch in parallel with the consumer's mount sequence, so it neither blocks render nor delays consumer-supplied mount actions.

• @lowdefy/modules-mongodb-notifications: ### Minor Changes

• #52 246c413 Thanks @Gervwyk! - Export the file-download page and notifications-files-bucket-public connection from the notifications module. Previously shipped as scaffolding in 0.4.2 but not consumable; the manifest now wires the page, the public S3 connection, and the supporting secrets so notification templates can link to /{entryId}/file-download?_id={notification._id}&index={file_index} to redirect recipients to a presigned S3 URL for an attachment without requiring them to be logged in.

  Secrets to add: FILES_S3_ACCESS_KEY_ID, FILES_S3_SECRET_ACCESS_KEY, FILES_S3_REGION, FILES_S3_BUCKET_PUB — share with the files module by convention when both are installed.

  No new vars are required on the module entry.