[loganj]

🤖

Summary

• Plugins can now keep a list of shared records up to date without polling. A plugin asks for "the current records of this type in these channels", gets the complete list once, and then gets each change as it happens.
• Before this, a plugin could only read once and read again later. Plugins had to poll, so changes showed up late, and a list over its read limit was silently incomplete.
• Relays that cannot do this report "unsupported", so plugins keep polling there. This needs feat(relay): NIP-AR sync subscriptions buzz#8522 on the relay; until that ships, nothing changes for users.

Details

• New host call: session.artifacts.sync(filter) returns a view with snapshot(), subscribe() and dispose(). The status is loading, live, stale (reconnecting; the last complete list is kept), restricted, error or unsupported.
• The filter must name its channels with #h (at most 256). Paging keys such as limit are refused at the call site, because the relay refuses them too.
• On the wire it is one relay subscription (REQ) with "artifact": "current" on the existing live socket, sent after sign-in (NIP-AR sync, block/buzz docs/nips/NIP-AR.md). Changes that arrive before the complete list ends (EOSE) are held, then the list is replaced at once. After that the view applies each new head, deletions, records that stop matching, and move removals.
• When the relay ends the subscription to ask for a fresh copy (resync), or the socket drops, the view restarts with backoff and jitter (1 s to 60 s) and keeps the last list as stale. restricted, invalid, unsupported, blocked and auth-required end it.
• Support comes from the relay's NIP-11 document (artifacts.sync.version 1), in both the native transport and the browser broker. The browser broker gets a matching stream route.
• The filter checks live in their own module with no runtime imports, so the browser broker can load them.
• The view types are exported to plugin authors next to RelayData.

Demo

I ran a container relay built from #8522 with three demo channels. In a browser build of this branch, a demo plugin synced three record types over those channels. When I edited a record from another client, the open plugin view showed the change about 30 ms after the write returned, with no refresh. The relay saw three sync subscriptions over the three channels.

[wesbillman]

🤖 Star Lord’s automated source review via Wes’s account, integrating Rocket, Mantis and Groot: both prior P2 findings are resolved; no new required changes, source assessment 9/10. Access loss/cache clear now purge sync views and fence old frames; rate-limited syncs pause shared admission before retry. Reviewed head 46f34cd against base c40dfdf, including the fix tests, transport lifecycle and public PR material. Source-only: no tests or apps executed; the hosted-check snapshot still had browser/native checks running, and live/native acceptance remains unverified.

[wesbillman]

🤖 Star Lord’s automated source review via Wes’s account, integrating Rocket, Mantis and Groot: the prior required fixes are addressed; no new changes requested, source assessment 9/10. Retry reentrancy, max-events termination, shared capacity and aggregate filter validation now match the reviewed contracts. Reviewed head 5b215a6 against base c40dfdf, including the follow-up tests and public PR material. Source-only: no tests or apps executed; the hosted-check snapshot still had browser, native and JavaScript jobs running, so runtime acceptance remains unverified.