[WIP] Update RX log listen window to 10 seconds

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

MeshCore GOME WarDriver Enhancement Tasks

Context

This is a JavaScript-based web application for MeshCore wardrive functionality. The codebase handles RX (receive) logging, ping/repeat listening, and API posting.

Task 1: Update RX Log Listen Window

Requirements

• Change RX_LOG_LISTEN_WINDOW_MS from its current value to 10 seconds (10000ms)
• Ensure the UnifiedRX Handler properly hands off repeats to the session log during this extended window
• Verify that all timing-dependent logic accounts for the new 10-second window

Acceptance Criteria

• RX_LOG_LISTEN_WINDOW_MS is set to 10000
• UnifiedRX Handler correctly processes repeats throughout the full 10-second window
• Session log receives repeat data as expected
• No race conditions or timing issues with the extended window

---

Task 2: Refactor Ping/Repeat Listener Flow

Current Behavior (to be changed)

1. Ping starts
2. Listen for heard repeats
3. Delay 3 seconds
4. Post to API
5. Start new timer

New Desired Behavior

1. Ping starts
2. Listen for heard repeats
3. Background the API posting (3-second delay + POST runs asynchronously)
4.  Immediately start new timer (don't wait for API)
5. UI shows "Listening for heard repeats" → "Waiting for next ping" (or idle)
6. API status messages should ONLY appear if there's an error

Requirements

• The 3-second delay and API POST should run in the background (non-blocking)
• The new timer should start immediately after repeat listening completes
• UI Status Flow (Success): "Listening for heard repeats" → "Waiting for next ping" / "Idle"
• UI Status Flow (Error): Show API error message only when the background POST fails
• Remove or suppress success status messages for API calls

Acceptance Criteria

• API posting is backgrounded and does not block the main ping/listen cycle
• New timer starts immediately after repeat listening, not after API response
• User sees smooth transition: "Listening for heard repeats" → "Waiting for next ping/Idle"
• API success messages are suppressed from UI
• API error messages ARE displayed to the user
• No data loss - all repeats are still logged and posted to API
• Background API failures don't crash or stall the main loop

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.