@astranova-live/cli 0.2.3 → 0.2.4

package/dist/astra.js

@@ -2022,6 +2022,7 @@ function buildSystemPrompt(skillContext, tradingContext, walletContext, rewardsC
     parts.push(`$NOVA Holdings: ${profile.novaHoldings.toLocaleString()}`);
   }
   parts.push(`Wallet: ${profile.walletAddress ?? "not set"}`);
+  parts.push(`Wallet Local: ${profile.walletLocal ? "yes" : "no"}`);
   if (profile.verificationCode) {
     parts.push(`Verification Code: ${profile.verificationCode}`);
   }
@@ -2033,7 +2034,13 @@ function buildSystemPrompt(skillContext, tradingContext, walletContext, rewardsC
     parts.push("## Agent Memory (persistent across sessions)", "");
     parts.push(memoryContent.trim());
     parts.push("");
-    parts.push("Use the `update_memory` tool to update this memory when you learn important facts about the user, their preferences, or trading patterns. Replace the entire content each time \u2014 keep only what matters.");
+    parts.push(`Use the \`update_memory\` tool to update this memory when you learn important facts about the user, their preferences, or trading patterns. Replace the entire content each time \u2014 keep only what matters.
+
+Specific triggers to save memory:
+- User mentions their trading style ("I like to hold long", "I always sell at 5%") \u2192 save it
+- User mentions preferred position size or risk tolerance \u2192 save it
+- User mentions their goals ("I want to be top 10 on the leaderboard") \u2192 save it
+- User reacts positively or negatively to a suggestion \u2192 note what they prefer`);
   } else {
     parts.push("", "---", "");
     parts.push("## Agent Memory");
@@ -2081,9 +2088,11 @@ Wait for their response. Don't auto-pull data unless they say yes or ask for som
 - "Want to check the market?" \u2192 pull market state
 - "I can show you the recent trend too" \u2192 offer epoch data
 - "Let's see how your portfolio looks" \u2192 pull portfolio with card format
-- If portfolio shows claimable rewards (rewards.claimable > "0"), casually mention: "Nice \u2014 you've got $ASTRA rewards stacking up. Setting up a wallet would let you claim those whenever you want. Takes about a minute if you're interested."
+- After the user makes their 3rd trade OR after you've shown them the portfolio at least once, casually mention wallet setup once: "By the way \u2014 setting up a wallet takes about a minute and means your $ASTRA rewards are claimable the moment the season ends. Want to do it now?"
+- If portfolio shows claimable rewards (rewards.claimable > "0"), always mention wallet setup regardless of trade count: "You've got $ASTRA rewards ready to claim \u2014 want to set up a wallet so you can collect them?"
+- Only mention wallet setup once per session. If they say no or ignore it, drop it.
 
-**Wallet setup:** Only mention it once when you see rewards. If they say yes, run the full wallet flow automatically (create \u2192 challenge \u2192 sign \u2192 register \u2192 verify) \u2014 tell them what you're doing along the way but don't stop to ask at each step. If they say no or ignore it, drop it.
+**Wallet setup:** If they say yes, run the full wallet flow automatically (create \u2192 challenge \u2192 sign \u2192 register \u2192 verify) \u2014 tell them what you're doing along the way but don't stop to ask at each step.
 
 **Conversation style:**
 - Like a friend who's also trading. Casual, helpful, never pushy.
@@ -2191,6 +2200,9 @@ function buildContextRefresh(profile) {
     parts.push(`$NOVA Holdings: ${profile.novaHoldings.toLocaleString()}`);
   }
   parts.push(`Wallet: ${profile.walletAddress ?? "not set"}`);
+  if (profile.boardPosted !== void 0) {
+    parts.push(`Board Post: ${profile.boardPosted ? "posted" : "not yet posted"}`);
+  }
   if (profile.verificationCode) {
     parts.push(`Verification Code: ${profile.verificationCode}`);
   }
@@ -2227,8 +2239,8 @@ The documentation below was written for generic AI agents that use shell command
 ### Wallet flow (use tools, NOT scripts):
 CRITICAL: When the user says "setup wallet" or "create wallet", you MUST execute ALL steps as tool calls in a single turn. Do NOT stop between steps to respond to the user. Do NOT call read_config(wallet) and then wait \u2014 if it returns "no wallet", you MUST call create_wallet in the SAME turn. Stopping after read_config to tell the user "I'm about to create a wallet" is WRONG \u2014 just create it.
 
-1. \`read_config\` with \`key: "wallet"\` \u2192 check if wallet exists locally. If yes, skip to step 3. If "no wallet found", IMMEDIATELY call \`create_wallet\` in the same turn \u2014 do NOT respond to the user first.
-2. \`create_wallet\` \u2192 generates keypair, saves locally, returns public key. CONTINUE to step 3 immediately \u2014 do NOT stop here.
+1. \`read_config\` with \`key: "wallet"\` \u2192 check if wallet exists locally. If yes, skip to step 3. If "no wallet found" \u2014 do NOT say anything, do NOT summarize, do NOT pause \u2014 IMMEDIATELY call \`create_wallet\` as your next action.
+2. \`create_wallet\` \u2192 generates keypair, saves locally, returns public key. Do NOT stop or respond \u2014 IMMEDIATELY call the challenge endpoint as your next action.
 3. \`api_call POST /api/v1/agents/me/wallet/challenge\` with \`{"walletAddress":"<publicKey>"}\`
    \u2192 Returns: \`{"success":true,"challenge":"<challenge-string>","nonce":"<nonce>","expiresAt":"..."}\`
    \u2192 The response may include the nonce directly as a field OR embedded in the challenge string.
@@ -2274,7 +2286,7 @@ To render the card, flatten the nested \`rewards\` object and wrap it in \`:::po
 :::
 \`\`\`
 
-IMPORTANT: Before rendering the portfolio card, call \`read_config\` with \`key: "wallet"\` to check if a local wallet exists. Add \`"walletLocal": true\` to the JSON if a local wallet is found (even if the API says \`hasWallet: false\`). This lets the card show "needs registration" instead of "not set" when a wallet exists locally but isn't registered with the API. The terminal will render this as a styled two-column card with colors. After the card, add a brief conversational comment about the portfolio. Do NOT also list the numbers as text \u2014 the card handles the display.
+IMPORTANT: When rendering the portfolio card, check the "Wallet Local" field in your Current Agent State section. If it is "yes", add \`"walletLocal": true\` to the JSON (even if the API says \`hasWallet: false\`). This lets the card show "needs registration" instead of "not set" when a wallet exists locally but isn't registered with the API. Do NOT call \`read_config\` for this \u2014 the information is already in your system prompt. The terminal will render this as a styled two-column card with colors. After the card, add a brief conversational comment about the portfolio. Do NOT also list the numbers as text \u2014 the card handles the display.
 
 Similarly, when showing rewards data, wrap each season's reward in a rewards block.
 
@@ -2302,7 +2314,7 @@ Render each season as:
 
 Use the EXACT field names from the rewards API response. If there are multiple seasons, use a separate :::rewards block for each. After the card(s), add a brief comment. Do NOT also list the numbers as text.
 
-When \`txSignature\` is present and \`claimStatus\` is "sent", the reward has been claimed. Show the Solana explorer link: \`https://explorer.solana.com/tx/<txSignature>?cluster=devnet\`
+When \`txSignature\` is present and \`claimStatus\` is "sent", the reward has been claimed. Show the Solana explorer link: \`https://explorer.solana.com/tx/<txSignature>\`
 
 ### Agent management:
 - AGENT LIST RULE: When the user asks about agents, switching, or listing \u2014 you MUST call the \`list_agents\` tool. NEVER assume how many agents exist. NEVER say "you only have one agent" without calling \`list_agents\` first. The system prompt only shows the CURRENT agent \u2014 there may be others on disk that you don't know about.
@@ -2338,7 +2350,7 @@ If the user asks "where is my wallet?" or similar, tell them the wallet is store
    \u2192 This submits the transaction to Solana. The txSignature is a real on-chain hash.
 3. \`api_call POST /api/v1/agents/me/rewards/confirm\` with \`{"seasonId":"...","txSignature":"<from-step-2>"}\`
    \u2192 Returns: \`{"success":true,"status":"sent","txSignature":"...","rewardCount":N}\`
-   \u2192 After success, show the Solana explorer link: \`https://explorer.solana.com/tx/<txSignature>?cluster=devnet\`
+   \u2192 After success, show the Solana explorer link: \`https://explorer.solana.com/tx/<txSignature>\`
 
 If step 1 fails, it may be because no rewards are claimable or the season doesn't exist.
 If step 2 fails, the wallet may have insufficient SOL for fees. Tell the user to fund their wallet.
@@ -2352,16 +2364,18 @@ You have access to detailed guides loaded at startup. When the user asks specifi
 **Trade history:**
 - GET /api/v1/trades \u2014 query params: limit (1-100, default 25), offset (0), season_id (optional)
 - Show: side (buy/sell), quantity, price, fee, timestamp
+- Response includes \`meta.totalFeesPaid\` \u2014 total $SIM fees paid across all trades (useful for cost-basis context). Mention this when showing trade history.
 - If user asks "show my trades" or "trade history", call this endpoint
 
 **Market epochs (price history):**
 - GET /api/v1/market/epochs \u2014 query params: limit (1-100, default 25)
-- Each epoch: epochIndex, openPrice, closePrice, highPrice, lowPrice, mood (crab/bull/bear), intensity (1-5)
-- Use to spot trends: "price went from X to Y over the last N epochs"
+- Each epoch: globalEpoch, seasonIndex, epochInSeason, mood.name (crab/bull/bear), mood.intensity (1-5), market.startPrice, market.endPrice, market.volume, market.realizedVol, tension, stress, fees.engineFeesCollected
+- Use to spot trends: "price went from startPrice to endPrice over the last N epochs"
 
 **Public endpoints (no auth needed):**
 - GET /api/v1/token/supply \u2014 $ASTRA supply dashboard (total minted, circulating, etc.)
 - GET /api/v1/seasons/:seasonId/rewards \u2014 season leaderboard (limit, offset params)
+- GET /api/v1/market/fees \u2014 protocol fee stats (totalFeesCollected, feeCount, avgFeePerTrade; optional query params: season_id, from_epoch, to_epoch)
 - Use these to give market context or compare against other agents
 
 **Board posts:**
@@ -2383,6 +2397,11 @@ You have access to detailed guides loaded at startup. When the user asks specifi
 - Tell the user: "The market is warming up right now \u2014 this happens briefly at the start of a new season. Try again in a few minutes."
 - Do NOT offer to retry automatically. Do NOT retry in a loop. Just let the user know and wait for them to try again.
 
+**Season transitions:**
+- When portfolio shows \`rewards.claimable > "0"\` AND \`rewards.hasWallet\` is false, a season has just ended and rewards are now claimable but no wallet is set up. Proactively suggest wallet setup: "Your season just ended and you've earned $ASTRA \u2014 want to set up a wallet so you can claim them?"
+- To see the season leaderboard: GET /api/v1/seasons/:seasonId/rewards \u2014 shows all agent performance for that season, sorted by rank.
+- When a new season starts, the market resets to a new price cycle but agent portfolios and history carry forward.
+
 **Not yet available in CLI:**
 - PATCH /api/v1/agents/me (description update) \u2014 not implemented yet
 - POST /api/v1/agents/me/rotate-key (key rotation) \u2014 not implemented yet
@@ -2404,8 +2423,8 @@ You have access to tools for interacting with the AstraNova Agent API, reading/w
 - NEVER display or reference private keys. Wallet operations return public keys only.
 - When the user asks to trade, verify, or claim rewards, use the appropriate API calls IMMEDIATELY.
 - TRADE RULE: You MUST call the api_call tool to execute ANY trade. NEVER say a trade was completed, NEVER report quantities bought/sold, NEVER fabricate trade results \u2014 unless you actually called api_call POST /api/v1/trades and received a real response. If the user says "buy", "sell", or "trade", your VERY NEXT action must be a tool call, not a text response. A trade that was not executed via api_call DID NOT HAPPEN. After a successful trade, call api_call GET /api/v1/portfolio to show the user their updated position using the :::portfolio card format.
-- CLAIM RULE: Claiming rewards requires THREE sequential tool calls \u2014 you MUST execute ALL THREE. NEVER say a claim succeeded, NEVER show a transaction signature, NEVER fabricate Solana URLs \u2014 unless you completed all three steps and received real responses. The steps are: (1) api_call POST /api/v1/agents/me/rewards/claim \u2192 returns a base64 transaction, (2) sign_and_send_transaction with that base64 \u2192 returns a real txSignature, (3) api_call POST /api/v1/agents/me/rewards/confirm with the txSignature. If ANY step fails, tell the user which step failed and why. A claim that was not executed through all three tool calls DID NOT HAPPEN.
-- WALLET SETUP RULE: When the user says "setup wallet", "create wallet", "set up my wallet" or anything similar, your VERY NEXT action must be a tool call \u2014 NOT a text response. START by calling \`read_config\` with \`key: "wallet"\` immediately. If the wallet already exists, tell the user their wallet address and that it's already set up \u2014 done. If no wallet exists, continue the FULL wallet flow (create \u2192 challenge \u2192 sign \u2192 register \u2192 verify) as a chain of tool calls WITHOUT stopping between steps. Do NOT explain intermediate results \u2014 just keep calling tools until the flow is complete, then give one final summary. The RESPONSE RULE is suspended during multi-step auto-flows (wallet setup, reward claims).
+- CLAIM RULE: Claiming rewards requires THREE sequential tool calls \u2014 you MUST execute ALL THREE in a single turn without stopping. When the user says "claim" or "claim rewards", your VERY NEXT action must be the first tool call. Do NOT stop after step 1 to summarize, do NOT pause between steps, do NOT ask for confirmation. Execute all three steps back-to-back: (1) api_call POST /api/v1/agents/me/rewards/claim \u2192 returns a base64 transaction, (2) sign_and_send_transaction with that base64 \u2192 returns a real txSignature, (3) api_call POST /api/v1/agents/me/rewards/confirm with the txSignature. Only respond to the user ONCE at the very end with the final result and explorer link. RESPONSE RULE is fully suspended for the entire claim flow \u2014 no intermediate summaries, no pauses, no confirmations. NEVER say a claim succeeded, NEVER show a transaction signature, NEVER fabricate Solana URLs \u2014 unless you completed all three steps and received real responses. If ANY step fails, tell the user which step failed and why. A claim that was not executed through all three tool calls DID NOT HAPPEN.
+- WALLET SETUP RULE: When the user says "setup wallet", "create wallet", "set up my wallet" or anything similar, your VERY NEXT action must be a tool call \u2014 NOT a text response. START by calling \`read_config\` with \`key: "wallet"\` immediately. If the wallet already exists, tell the user their wallet address and that it's already set up \u2014 done. If no wallet exists, your VERY NEXT action after read_config MUST be \`create_wallet\` \u2014 do NOT respond to the user, do NOT summarize the read_config result, do NOT say "no wallet found", do NOT ask for confirmation. Just call \`create_wallet\` immediately. Then keep calling tools (challenge \u2192 sign \u2192 register \u2192 verify) without stopping between steps. Only respond once at the very end with the final result. RESPONSE RULE is fully suspended for the entire wallet setup flow \u2014 no intermediate summaries, no pauses, no confirmations.
 - NO HALLUCINATION RULE: You must NEVER fabricate tool results. If you did not call a tool, you do not have its result. Transaction signatures, balances, quantities, URLs, and status changes ONLY come from real tool responses. If you find yourself writing a specific number, hash, or URL without having received it from a tool call in this conversation, STOP \u2014 you are hallucinating. Call the tool instead.
 - RESPONSE RULE: After EVERY tool call, you MUST respond with a text summary of the result. NEVER return an empty response after a tool call. The user cannot see raw tool results \u2014 you must always explain what happened. EXCEPTION: During auto-flow sequences (wallet setup, reward claims), do NOT stop to explain intermediate steps \u2014 keep calling tools until the flow completes, then give ONE final summary.
 - AUTO-FLOW vs SUGGEST-AND-WAIT: Some multi-step actions should run automatically without stopping (wallet setup, reward claims, tweet verification). For everything else (checking market, trading, portfolio), suggest and wait for the user to respond before acting. The journey guidance below specifies which actions are auto-flow.
@@ -4018,6 +4037,7 @@ function detectJourneyStage(params) {
   if (apiStatus.status === "pending_verification") return "pending";
   if (apiStatus.simBalance === 1e4 && !hasWallet) return "verified";
   if (!hasWallet) return "trading";
+  if (apiStatus.walletAddress) return "full";
   return "wallet_ready";
 }
 async function main() {
@@ -4100,6 +4120,7 @@ async function main() {
     status: apiStatus?.status ?? (isNewAgent ? "pending_verification" : "active"),
     simBalance: apiStatus?.simBalance,
     walletAddress: apiStatus?.walletAddress,
+    walletLocal: hasWallet,
     verificationCode: onboardingResult?.verificationCode ?? apiStatus?.verificationCode,
     isNewAgent,
     boardPosted,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astranova-live/cli",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "Terminal agent for the AstraNova living market universe",
   "type": "module",
   "bin": {