FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Separating Sync Targets and Settings state explanations
Distinguishing a stopped Connector from zero candidates and showing connection, account, and storage boundaries
Purpose
An empty Sync Targets screen did not distinguish unfinished functionality, zero candidates, and a stopped Connector, and it exposed an internal error name. Settings also made the purpose and storage location of values difficult to understand.
Implementation
administration application source now separates a stopped Connector from a connected Connector with zero root candidates. The stopped state hides ipc_socket_unavailable, explains the service requirement inside the empty state, and avoids an unnecessary refresh warning.
Settings was reorganized into four cards: current environment, signed-in account, production connection profile, and local storage and security. The roles of Keychain, Application Support, and credentials that are not retained on screen are explained separately.
Rendering diagram…
What was confirmed
Verification results
Code inspection confirmed separate display branches for a stopped Connector and zero candidates, while the Swift build and all seven tests passed.
The specification audit, secret scan, and repository-policy checks passed.
No database or external service changed, and real candidate display from a running Connector remained outside the cutoff.
Basis for completion
Completion required distinct UI states and a Settings layout that explains connection, account, and storage boundaries, with automated checks passing.