- Shipped
- September 12, 2026 at 7:23 PM UTC
- Author
- Kamo
- Commit
- f9e5a2e
Every successful write through forwardToApi now publishes rt.org.{orgId}.{domain} on core NATS (the domain is the first backend path segment, skipping security/). MediaService relays it to /topic/rt/org/{orgId}/{domain}, and useOrgChanges subscribes over the shared socket, coalesces bursts and fires again after a reconnect. The los, billing and oauth-config routes, which do not go through forwardToApi, publish themselves. Pages that loaded once now refetch silently when their domain changes: no skeleton flash, and never over unsaved input. - Accounts: assign, and the account view (overview, history, leads, members, notes, orders) - Notes - Commerce: orders, agreements, bookings, procurement, requests, service jobs, service requests, signups, subscriptions, personal loans and the aging report - Loans, loan detail and offers - Knowledge base home and article - Careers, legal and compliance - Settings, account settings, integrations, the document category page, and the market and subscription plan pages The calendar coalesces its existing change feed. Achievements follow the member's unlock topic.