fetchFullBodyLogDetail

Fetches the complete log entry for logId directly from the device's disk cache, including the full (un-truncated) request and response bodies.

When to call this: Only call this for entries where LogEvent.isRequestBodyTruncated or LogEvent.isResponseBodyTruncated is true. The server writes a disk record only when at least one body exceeds the truncation threshold; for all other entries no disk file exists and this method returns Result.failure.

Behaviour contract:

• Returns Result.success with the full LogEvent if a disk record exists.

• Returns Result.failure (HTTP 404) if the entry was never truncated, has been cleaned up by the session-start eviction policy, or has been explicitly deleted.

• Does not consult the in-memory ring buffer — the result is independent of whether the entry is still in memory, making it safe to call after an app restart.

Disk lifetime / cleanup: The server retains disk records until one of two conditions is met:

1. The management UI reconnects (sends a new clientSessionStart timestamp via fetchMonitorLogsSince). The server then deletes records older than min(oldest_in_memory_entry, clientSessionStart).

2. No management UI connects within 60 seconds of server start — the server falls back to deleting records older than 2 days.

This means entries from a previous app session remain accessible as long as the management UI reconnects within the 2-day window and the session-start eviction threshold hasn't passed them.

Parameters