[TASK] Persist scan phase timestamps in task detail responses

[utksh1]

Summary

Task detail payloads should expose started and completed timestamps for each scan phase, not just coarse status.

Why this task exists

This area already has active backend behavior and tests, but the current contract is either implicit or incomplete. A contributor should be able to improve reliability without changing unrelated execution flow.

Scope

• Suggested files or directories: backend/secuscan/executor.py, backend/secuscan/routes.py, testing/backend/unit/test_scan_phases.py
• Out of scope: broad UI redesigns, unrelated schema migrations, or plugin-wide refactors

Starting points

Review the existing route and model patterns in backend/secuscan/routes.py, adjacent unit/integration tests under testing/backend/, and similar implementations already used for tasks, notifications, or workflows.

Acceptance criteria

• The target backend behavior is implemented with a clear contract
• Regressions are covered by focused unit or integration tests
• Error handling stays consistent with existing API patterns

Test plan

Run the most specific backend tests that exercise the touched route or module, then run the adjacent integration coverage if a route contract changes.

Notes for contributors

Keep the change scoped to the described behavior. Avoid bundling unrelated cleanup into the same PR.

[Rakshak05]

Hii @utksh1, I would like to work on this. Can you please assign it to me under GSSoC'26 contributor!?

[diksha78dev]

@utksh1 I would like to work on this issue under GSSoC'26.

Proposed Solution

To persist scan phase timestamps, I will update the task detail schema and the executor logic to ensure accurate tracking.

• Action: Modify the data model in backend/secuscan/executor.py and the response structure in backend/secuscan/routes.py.
• Implementation:
  • Model Update: Update the scan phase data structure to include started_at and completed_at fields (ISO 8601 format).
  • Execution Logic: In the executor, capture these timestamps at the start and conclusion of each defined phase and persist them to the database.
  • API Contract: Update the task detail endpoint to expose these new fields, ensuring that existing API clients do not break.
• Testing: Add a test suite in testing/backend/unit/test_scan_phases.py to verify that phases correctly capture and return timestamps, and validate the behavior when a scan is in progress versus completed.