note why PeachSyncService's locked-vault early return stays silent

@@ -75,6 +75,13 @@7575      * vault's root key, so a locked phone genuinely has nothing to listen with.7676      * That is also why this is re-attempted on every start command rather than7777      * once: the service may well come up before the user has unlocked.78+     *79+     * The early return is deliberately the one terminating path that reports no80+     * outcome. Coming up locked is the normal boot order, not a failed sync;81+     * reporting it would leave a red light waiting on the other side of the82+     * unlock screen. The locked case a person can actually see is reported from83+     * `SyncViewModel.syncNow`, and from a session that reaches a locked vault84+     * mid-handshake.7885      */7986     private fun startReconnectListener() {8087         val master = vault.syncMasterKey() ?: return