lfg2025/archy
1
0
Fork 0
Code Issues 11 Pull Requests Actions Packages Projects Releases 12 Wiki Activity

Track federated node sync reliability and progress UX

Browse Source
This commit is contained in:
archipelago
2026-10-07 07:22:15 -04:00
parent c4b22628af
commit 0338a193db
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/post-1.9.0-work-backlog.md
+6
View File
@@ -470,6 +470,12 @@ functional/UX review. These are additions to existing groups, not closed work.
- Update relationship, request, availability and operation states automatically - Update relationship, request, availability and operation states automatically
across screens without routine manual sync. Handle reconnect, missed events, across screens without routine manual sync. Handle reconnect, missed events,
out-of-order replies and failed refreshes without invented success states. out-of-order replies and failed refreshes without invented success states.
- Federated Nodes sync is currently reported as unreliable and slow. Diagnose
the actual transport, queue and reconciliation path; prevent indefinite
waits; show a loader with a useful phase/status message and elapsed progress;
provide bounded retry and a truthful success, partial-success or failure
result. Preserve the last known state while a refresh is in flight and make
the next retry safe and idempotent.
- When a request changes the 3D map layout, rotate its node to the front, top - When a request changes the 3D map layout, rotate its node to the front, top
centre and clearly expose the request action. Cover multiple requests, centre and clearly expose the request action. Cover multiple requests,
completion, user camera interaction, reduced motion and mobile viewports. completion, user camera interaction, reduced motion and mobile viewports.