pearcord/pearcord-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Phase 883: gossip RPC registry, payload helper, sync responders extract (v0.8.850)

Browse Source 
Non-breaking refactor: centralize handler-to-config registry alignment in
gossip-rpc-registry.js, shared targeted fetch payloads for audit/digest pulls,
and extract guild sync/member page RPC responders into a dedicated mixin.
Default gossip v1 unchanged; fleet v2 cutover still deferred.
This commit is contained in:
Raven Scott
2026-06-04 18:22:52 -04:00
parent 89e0103557
commit 5244c0fb41
7 changed files with 90 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
release_notes/RELEASE_v0.8.850.md
+9
View File
@@ -0,0 +1,9 @@
# Release v0.8.850 — Phase 883
Non-breaking refactor: centralize guild gossip RPC handler-to-config registry alignment; shared targeted fetch payload builder for audit/digest pulls; extract guild sync/member page RPC responders into `platform-guild-sync-rpc-responders-mixin.js`. Default gossip v1 unchanged; fleet v2 cutover still deferred.
- `gossip-rpc-registry.js` — maps request methods to pull configs with `validateGuildGossipRpcRegistryAlignment()`
- `gossip-rpc-payload.js` — `buildTargetedGuildGossipRpcFetchPayload()` for audit/digest mesh pulls
- `platform-guild-sync-rpc-responders-mixin.js` — guild sync + member page RPC responders
- Platform view adds `guildGossipRpcPullConfigKeys` and `guildGossipRpcPullRegistry`
- CI: `npm run test:ci-phase883`