Document log message formatting improvement as backlog issue

[Copilot]

Converted a code review comment about string concatenation formatting into a backlog issue rather than addressing it immediately in the current PR.

Changes

• Created .github/BACKLOG_ISSUE_LOG_MESSAGE_FORMATTING.md documenting the formatting improvement for whack-a-mole/backend/app.py:518-519

Context

The current code uses continuation with leading space:

print(
    f"[Thread-{thread_name}] Whack success!"
    f" Hole {hole}, Time: {result['reaction_time']:.3f}s"
)

Suggested improvement for clarity (trailing space instead):

print(
    f"[Thread-{thread_name}] Whack success! "
    f"Hole {hole}, Time: {result['reaction_time']:.3f}s"
)

Both produce identical output; this is purely a readability concern suitable for future cleanup.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.