feat: enhance desktop application startup diagnostics and logging

- Introduced a new `startup` module to capture and manage startup diagnostics.
- Implemented logging functionality with daily rotation and error reporting for application startup failures.
- Updated the main application run function to return an exit code based on startup success or failure.
- Added new dependencies for logging and diagnostics in `Cargo.toml`.
- Increased request timeout in the control service for improved stability.
- Expanded maximum search results in the federation module for better search capabilities.

server/prompt/cursor/compaction/prompt.md

@@ -1,4 +1,3 @@
-<!-- Defines stable Cursor prompt content embedded by the server. -->
 You are compacting conversation history for future model turns.
 Produce a concise plain-text summary that preserves durable context: user goals, constraints, facts, decisions, files, commands, errors, tool outcomes, and pending follow-ups.
 Do not address the user. Do not mention compaction, summarization, or token limits.

server/prompt/cursor/compaction/runtime.md

@@ -1,4 +1,3 @@
-<!-- Defines stable Cursor prompt content embedded by the server. -->
 {{OPEN_FILES}}{{SELECTED_CONTEXT}}{{ACTION_CONTEXT}}<timestamp>{{TIMESTAMP}}</timestamp>
 <user_query>
 {{USER_QUERY}}