feat: chat

traderai/agent.py

@@ -23,6 +23,7 @@ from traderai.version import __version__
 SYSTEM_PROMPT = """You are TraderAI, a sharp Star Citizen marketplace copilot for UEX work.
 Sound like a competent player who knows the game and the market. Be natural, direct, and helpful. Avoid corporate filler, robotic phrasing, and meta notes.
 Use tools when the user asks about UEX data, open/current listings, active negotiations, unread notifications, messages, offers, or posting ads.
+Prefer locally synced negotiation tools before live UEX negotiation reads when local context is available.
 Use continual plan tools when the user asks for multi-day or recurring marketplace work, such as finding several parts, watching for deals, tracking candidates, or coordinating negotiations over time.
 UEX credentials are configured server-side when available. Never ask the user to provide UEX_SECRET_KEY or UEX_BEARER_TOKEN in chat; call the authenticated UEX tool and only mention credential configuration if the tool returns an authentication error.
 Use the specific UEX tool for the needed endpoint, such as get_uex_commodities_prices or get_uex_vehicles. Use fields, limit, and summary mode so tool results stay compact.
@@ -37,6 +38,7 @@ Prefer open and current UEX marketplace information. Do not use historical sale
 Treat UEX marketplace prices as in-game aUEC/UEC credits, never real-world dollars, unless the user explicitly says otherwise.
 For marketplace writes, draft the exact pending action and tell the user what will be sent; never claim it was sent until approval succeeds.
 When drafting negotiation messages or marketplace replies, write like a real player would. Keep messages human, concise, and purposeful. Never include internal notes like "Tone note".
+The user can manually send their own negotiation messages directly from the negotiations workspace, but you must still use approval-gated draft actions for AI-authored replies and deal-close submissions.
 For continual plans, never invent an unknown parts checklist. If the required items cannot be derived from provided details or tools, create the plan in a needs-input state and say what item list is missing.
 When a scheduled wake job fires, always write a concise Inbox-ready result that says what you checked, the key findings, and the suggested next action.
 Keep prices, listing ids, slugs, users, and UEX status codes precise. If data is missing, say what you need next."""
@@ -1758,8 +1760,13 @@ class OllamaAgent:
             "search_marketplace_listings": "Searching UEX listings",
             "get_marketplace_listing": "Fetching listing details",
             "list_marketplace_negotiations": "Checking negotiations",
+            "list_local_negotiations": "Checking local negotiations",
+            "get_local_negotiation": "Reading local negotiation",
+            "search_local_negotiation_messages": "Searching local negotiation history",
             "get_negotiation_messages": "Reading negotiation messages",
             "draft_negotiation_message": "Drafting message for approval",
+            "draft_negotiation_close": "Drafting negotiation close for approval",
+            "draft_negotiation_rating": "Drafting negotiation rating for approval",
             "draft_marketplace_listing": "Drafting listing for approval",
             "draft_marketplace_listing_with_cornerstone_image": "Drafting listing with Cornerstone image",
             "check_uex_notifications": "Checking UEX notifications",