feat: extend update-agent reporting

[AlexKaravaev]

Extend update agent reporting, modify backend status connect to not depend on if update agent is alive or not. Example of status sent with new update and new field "state"

Jul 20 14:06:21 localhost.localdomain worldcoin-backend-status[627981]: 
Sending status to backend: CurrentStatus 
....update_progress: Some(UpdateProgress { download_progress: 100, processed_progress: 100, install_progress: 100, total_progress: 100, error: None, state: NoNewVersion }), ...

[Copilot]

Pull Request Overview

This PR extends the update agent's reporting capabilities by adding new progress states and overall status tracking, plus removes the backend status dependency on whether the update agent is alive. The changes enhance monitoring of update processes from "no new version" through completion and reboot.

Key changes:

• Adds comprehensive state tracking with new UpdateAgentState enum values (NoNewVersion, Installing, Rebooting)
• Replaces individual component property updates with unified progress reporting via update_dbus_progress
• Migrates backend status from polling-based to signal-based update progress monitoring

Reviewed Changes

Copilot reviewed 15 out of 16 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
update-agent/src/main.rs	Core update agent logic updated to use new progress reporting and handle "no new version" case
update-agent/src/lib.rs	Adds utility mappers for state conversion between different components
update-agent/src/dbus/interfaces.rs	Replaces individual property updates with unified progress reporting system
update-agent/src/component.rs	Updates download progress reporting to use new unified interface
update-agent/src/claim.rs	Adds NoNewVersion error type for better error handling
update-agent/dbus/src/lib.rs	Extends dbus interface with new state enums and overall progress properties
backend-status/src/update_progress.rs	Replaces polling mechanism with signal-based progress monitoring
backend-status/src/main.rs	Updates logging messages to reflect new signal-based approach
backend-status/src/dbus/intf_impl.rs	Adds immediate send logic for critical update states
backend-status/src/backend/types.rs	Adds state field to update progress structure
backend-status/src/backend/status.rs	Includes state in status request building
backend-status/dbus/src/types.rs	Adds state field to UpdateProgress type

Comments suppressed due to low confidence (1)

backend-status/src/update_progress.rs:348

• The test function references UpdateProgressCalculator::from_update_agent_data but this struct/method doesn't exist in the visible code. The test should reference the actual implementation or the struct should be defined.

    fn test_update_progress_calculator() {

[Michael-Preibisch]

Left some minor comments.

@AlexKaravaev would it be feasible to include downloaded_bytes and bytes_total instead of progress %?

[Michael-Preibisch]

Nit: Weird formatting

[AlexKaravaev]

this is clippy :(

[Michael-Preibisch]

This should be 33, not 66. The Fetched state means "download complete" which is 1/3 of the total update process.

Currently causes the progress bar to jump from 33% to 66% instantly when downloads finish.

[AlexKaravaev]

This should be 33, not 66. The Fetched state means "download complete" which is 1/3 of the total update process.

I was thinking for a bit on what to do here. Download is 1/3 of the whole process, but in fact for the user download is majority of the whole update process time due to the slow connection speed. So I think that if we hardcode it for 66(for now - we should improve it better) it would reflect a bit better for the actual user the overall installation progress

[Michael-Preibisch]

:lfg:

[vmenge]

lgtm