{"items":[{"id":"8f921211-bdb2-4fb9-a10a-f3ae8cad5ab4","type":"pull_request","org":"lattice-pns","repo":"lattice","title":"Simplified push notification architecture by removing topic-based broadcasting","summary":"We've refactored the push notification server by removing topic-based subscriptions and the associated broadcast functionality. This change streamlines the system to focus exclusively on direct agent-to-agent messaging and one-to-one push notifications, significantly reducing code complexity and removing unused infrastructure like Redis topic sets and bearer authentication. It's always satisfying to delete over 200 lines of dead code to make the codebase cleaner and easier to maintain. ![Code Deletion](https://enxegfybrygakxrhnabg.supabase.co/storage/v1/object/public/meme-images/cacafc26-7102-4f09-b00d-64c8224d6e8f.jpg)","url":"https://nomit.dev/lattice-pns/lattice/status/c4c466a7c413f7720874c353fe5af3e3fd3bd81f8dc10ac426567b25e1ffc83e","author":"lws803","contributors":["lws803","claude"],"updated_at":"2026-03-25T14:52:10+00:00"},{"id":"71601cf4-7dec-46c6-bbdf-bdf09b162f86","type":"pull_request","org":"lattice-pns","repo":"lattice","title":"Introduce /push/topics with built-in deduplication","summary":"We've replaced the single-topic `/push/topic` endpoint with `/push/topics`, which now supports broadcasting to multiple topics in a single request. This update uses a Redis `SUNION` operation to automatically deduplicate subscribers across the provided topics, ensuring that agents only receive a notification exactly once even if they are subscribed to several of the target topics. This reduces both network overhead and improves the developer experience for handling multi-topic notifications. ![No duplicates here](https://enxegfybrygakxrhnabg.supabase.co/storage/v1/object/public/meme-images/26e06be6-1e5f-465b-8256-3f2cc2be4a71.jpg)","url":"https://nomit.dev/lattice-pns/lattice/status/92397044af4dc96adf98c605950c51317515bab51e1501b30f6b93e1392de2bc","author":"lws803","contributors":["lws803","claude"],"updated_at":"2026-03-25T12:23:58+00:00"},{"id":"f6e8e501-6828-46ee-be6d-ceffa74dc541","type":"pull_request","org":"lattice-pns","repo":"lattice","title":"SSE notifications now include topic information","summary":"This update modifies the SSE notification event format to include the `topic` name when messages are broadcast via `/push/topic`. By adding the topic to the notification data, subscribers can now easily identify which channel triggered a specific push event. I've also updated the tests to verify that the topic field is correctly propagated to recipients.","url":"https://nomit.dev/lattice-pns/lattice/status/f139a7d2e865ad71ac859a4935fb01ccc11536c7613b53c623121388a2b74e9c","author":"lws803","contributors":["lws803"],"updated_at":"2026-03-20T21:58:49+00:00"},{"id":"b723bcb6-5efb-439d-b877-309da5126fe0","type":"pull_request","org":"lattice-pns","repo":"lattice","title":"Refactored /push endpoint to use path parameters for improved REST compliance","summary":"We've transitioned the `/push` endpoint from utilizing a query parameter (`?pubkey=`) to a cleaner path parameter structure (`/push/:pubkey`). This change aligns the API with standard REST practices, allows for stricter schema validation, and maps missing keys to a more appropriate 404 status code. It's a small change that significantly improves the clarity and resource-oriented design of our endpoint architecture. ![Refactor progress](https://enxegfybrygakxrhnabg.supabase.co/storage/v1/object/public/meme-images/645c2aa5-d7f5-4b2b-9df7-11770112ba67.png)","url":"https://nomit.dev/lattice-pns/lattice/status/459c272f7371f5dcf1c80be4189845eb15f74c547051c02bf3b0bbb4abd2b752","author":"lws803","contributors":["lws803","claude"],"updated_at":"2026-03-20T00:57:37+00:00"},{"id":"0c44d48f-149f-419f-9565-dc61201f88da","type":"pull_request","org":"lattice-pns","repo":"lattice","title":"Added Dokku deployment support and HTTPS configuration","summary":"This update introduces a streamlined deployment workflow for Dokku, including a `setup-dokku.sh` script to automate app creation, port mapping, Redis integration, and HTTPS via Let's Encrypt. A custom `nginx.conf.sigil` was added to handle HTTPS redirects and proxy configurations, ensuring secure and scalable deployments for production environments. This lowers the barrier to entry for hosting by codifying the infrastructure setup.","url":"https://nomit.dev/lattice-pns/lattice/status/662e774892529fbbef1a0ca4aaedeecea6016499f22d2b12281e99745aa2eea7","author":"lws803","contributors":["lws803"],"updated_at":"2026-03-19T22:33:00+00:00"}],"pagination":{"offset":0,"limit":5,"has_more":true}}