feat: Add HTTP API to export captured network logs

[abdullahsohailcs]

Summary

Adds a built-in HTTP export API to the Flocon desktop server, allowing
external tools (test frameworks, CI pipelines, scripts) to query captured
network logs directly over HTTP without opening the desktop UI.

Endpoints

All endpoints are served on the existing HTTP server (port 9024).

Method	Endpoint	Description
GET	/api/network-logs	All captured network calls across all devices
GET	/api/network-logs/{deviceId}	All calls for a specific device
GET	/api/network-logs/{deviceId}/filter	Calls filtered by device and time range

Query Parameters (endpoint 3)

Parameter	Type	Description
startTimestamp	Long (Unix ms)	Return calls at or after this time
endTimestamp	Long (Unix ms)	Return calls at or before this time

Example Response

{
  "data": [
    {
      "callId": "7b6f09e6-...",
      "method": "GET",
      "url": "https://api.example.com/endpoint",
      "startTime": 1779192773561,
      "startTimeFormatted": "17:12:53.561",
      "statusCode": 200,
      "durationMs": 398.84,
      "requestHeaders": { "Authorization": "Bearer ..." },
      "responseHeaders": { "Content-Type": "application/json" },
      "requestBody": null,
      "responseBody": "{ ... }",
      "contentType": "application/json",
      "deviceId": "87b5d37fd3c32ce3",
      "appInstance": 1780479786702
    }
  ],
  "metadata": {
    "exportedAt": 1779200000000,
    "totalItems": 1,
    "filteredBy": {
      "deviceId": "87b5d37fd3c32ce3",
      "startTimestamp": 1779192773000,
      "endTimestamp": 1779199999999
    }
  }
}

[gemini-code-assist]

Code Review

This pull request introduces a feature to export network logs, adding new Ktor API endpoints under /api/network-logs along with corresponding Room database queries, data sources, and a new use case (ExportNetworkLogsAsJsonUseCase). Key feedback points out a compilation error in TimeFormatter.kt due to invalid datetime properties, suggests returning an empty list instead of a failure when no logs match the filter, advises using a proper serializer instead of manual JSON string interpolation for error responses, and recommends performing timestamp filtering at the database level rather than in memory to prevent performance bottlenecks.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[abdullahsohailcs]

Added improvements please check now