Update to CryptoSocials

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

.app.json →

.codex-plugin/plugin.json →

.mcp.json →

assets/icon-dark.png →

assets/icon.png →

assets/logo-dark.png →

assets/logo.png →

.codex-plugin/plugin.json

− removed · + added

--- before
+++ after
@@ -1,26 +1,112 @@
 {
-  "apps": "./.app.json",
   "author": {
     "name": "CIAN MC DONNELL"
   },
-  "description": "Research stored Crypto X discussions with your agent. Discover which assets are being discussed, explore author history, filter by known chain associations, and follow source links to inspect the evidence. Start with whole-period summaries, narrow questions with compact results, and retrieve detailed posts when needed. Compare discussion activity and inspect available price history.\n\nA CryptoSocials account is required. Research uses your shared CryptoSocials credit balance across MCP, REST API and Archive. Coverage is the stored archive, not all of X. Missing prices or posts do not mean nothing happened. Your agent interprets the evidence; CryptoSocials does not provide trading predictions or execute trades.",
+  "description": "Explore crypto conversations with your agent. Find what is changing around a coin, compare Crypto Voices, and connect their claims with dated price history. Follow the original posts behind an answer.\n\nBring your own question. Investigate recent discussion, coin communities, views and sharing, author histories, changing narratives, known chain connections or the coins and voices in your saved Lists. Compare complete matching stored-data counts across days, weeks or longer periods, then explore the original evidence. The research guide helps you discover further possibilities.\n\nInstall CryptoSocials, connect your CryptoSocials account, and ask. Start with an example or your own question, then follow up without losing the original dates and sources.\n\nResearch uses selected stored X posts and price observations, with sources and dates. Coverage varies and history can have gaps. Your agent interprets the evidence. These tools read research and Lists; they do not trade, publish posts, edit Lists or run background alerts.",
   "interface": {
-    "capabilities": [],
+    "capabilities": [
+      "Research crypto X conversations",
+      "Compare community engagement",
+      "Inspect dated price history",
+      "Read saved Lists"
+    ],
     "category": "Data & Analytics",
     "defaultPrompt": [
-      "Which assets had the most stored discussion yesterday? Explain coverage and show representative source posts.",
-      "Find source posts discussing confidential inference in the stored archive.",
-      "What did this author discuss during my chosen period? Show source evidence."
+      "Which coins are attracting more discussion today, and what has changed?",
+      "Who stands out in $SUI's community this week? Compare their posts, views and reposts.",
+      "Compare $BTC commentary this week with its price timeline. Who was early, who changed their view, and what did not hold up?"
     ],
     "developerName": "CIAN MC DONNELL",
     "displayName": "CryptoSocials",
-    "longDescription": "Research stored Crypto X discussions with your agent. Discover which assets are being discussed, explore author history, filter by known chain associations, and follow source links to inspect the evidence. Start with whole-period summaries, narrow questions with compact results, and retrieve detailed posts when needed. Compare discussion activity and inspect available price history.\n\nA CryptoSocials account is required. Research uses your shared CryptoSocials credit balance across MCP, REST API and Archive. Coverage is the stored archive, not all of X. Missing prices or posts do not mean nothing happened. Your agent interprets the evidence; CryptoSocials does not provide trading predictions or execute trades.",
+    "longDescription": "Explore crypto conversations with your agent. Find what is changing around a coin, compare Crypto Voices, and connect their claims with dated price history. Follow the original posts behind an answer.\n\nBring your own question. Investigate recent discussion, coin communities, views and sharing, author histories, changing narratives, known chain connections or the coins and voices in your saved Lists. Compare complete matching stored-data counts across days, weeks or longer periods, then explore the original evidence. The research guide helps you discover further possibilities.\n\nInstall CryptoSocials, connect your CryptoSocials account, and ask. Start with an example or your own question, then follow up without losing the original dates and sources.\n\nResearch uses selected stored X posts and price observations, with sources and dates. Coverage varies and history can have gaps. Your agent interprets the evidence. These tools read research and Lists; they do not trade, publish posts, edit Lists or run background alerts.",
     "privacyPolicyURL": "https://cryptosocials.net/privacy",
-    "shortDescription": "Research Crypto X discussions",
+    "shortDescription": "Crypto X research for agents",
     "supportURL": "https://cryptosocials.net/support",
     "termsOfServiceURL": "https://cryptosocials.net/terms",
-    "websiteURL": "https://cryptosocials.net"
+    "websiteURL": "https://cryptosocials.net",
+    "brandColor": "#294ED8",
+    "brandColorDark": "#7795FF",
+    "composerIcon": "./assets/icon.png",
+    "composerIconDark": "./assets/icon-dark.png",
+    "logo": "./assets/logo.png",
+    "logoDark": "./assets/logo-dark.png"
   },
   "name": "app-6ab1310a217c8191a407ab171972a4ed",
-  "version": "1.0.0"
-}
\ No newline at end of file
+  "version": "1.3.0",
+  "homepage": "https://cryptosocials.net",
+  "keywords": [
+    "crypto",
+    "X research",
+    "communities",
+    "author history",
+    "price context",
+    "MCP"
+  ],
+  "mcpServers": "./.mcp.json",
+  "extensions": {
+    "com.openai": {
+      "review": {
+        "test_cases": {
+          "positive": [
+            {
+              "description": "Explain possibilities and available research credits without spending credits.",
+              "prompt": "What can I investigate with CryptoSocials, and how much research can I do with my remaining credits?",
+              "tools_triggered": "get_research_guide and get_research_balance; get_research_capabilities when technical operating details are needed",
+              "expected_behavior": "Answer the user\u2019s actual capabilities and balance question in plain language using the free research guide and get_research_balance. Explain actual credits and the fixed successful data-request/page tariff without promising a fixed investigation price. Do not start paid research. Reuse recent balance information for later ordinary research; refresh it if asked, scope expands substantially or spending is uncertain, including another connection."
+            },
+            {
+              "description": "Compare discussion with a previous day and read the original sources.",
+              "prompt": "Which coins attracted the most discussion on 3 October 2026? Compare the leading coins with 2 October and show what people were saying.",
+              "tools_triggered": "measure_evidence; discover_evidence if candidate identities are needed; read_evidence for selected source wording",
+              "expected_behavior": "Use complete equal UTC day windows [2026-10-02T00:00:00Z,2026-10-03T00:00:00Z) and [2026-10-03T00:00:00Z,2026-10-04T00:00:00Z). Calculate whole-window project counts on the server, preserve all requested groups and cutoff ties, then read relevant original wording and available context. Follow exact delivery continuations when required. A delivered page size is not the calculation population. Explain changes with dated original sources; activity alone is not sentiment."
+            },
+            {
+              "description": "Inspect a coin community using recorded views and sharing.",
+              "prompt": "Who stands out in Sui\u2019s community from 28 September through 3 October 2026? Compare their collected posts, views and reposts, then show source posts.",
+              "tools_triggered": "resolve_assets once if needed, measure_evidence, read_evidence",
+              "expected_behavior": "Resolve exact Sui identity once and reuse returned IDs. Use the complete archive/coin window [2026-09-28T00:00:00Z,2026-10-04T00:00:00Z), grouping by author and calculating requested posts, observed views and reposts over all matching stored posts. Preserve observed/missing metric coverage and all requested ranking ties. Latest lifetime counters on period-published posts are not views earned during that period or unique people. Known reposter counters do not add underlying-original engagement to reposter totals. Historical unknown ordinary posts remain eligible. Read relevant original sources with the same coin/date filters and attribute related-original wording to its own speaker."
+            },
+            {
+              "description": "Compare a known Crypto Voice\u2019s claims with separately dated prices.",
+              "prompt": "How did @CryptoKaleo\u2019s view on ETH change from 17\u201323 September 2026? Read the original claims and compare them with Ethereum\u2019s stored price timeline. Include what did not hold up.",
+              "tools_triggered": "search_authors and resolve_assets only if identities are needed; read_evidence; list_market_series and read_price_context for independent stored timeline",
+              "expected_behavior": "Confirm the exact author and Ethereum identity. Read every selected original and available related context across [2026-09-17T00:00:00Z,2026-09-24T00:00:00Z), following all required pages and reusing proven already-delivered wording. Preserve conditions, changed views and counterevidence. Attached per-post prices are already supplied in original readings; use them when sufficient. For the requested independent timeline use an identified stored series, its units, price-effective/capture dates, inversion/conversion provenance and gaps. Never invent unavailable prices or wording, a winning score or a trade. Pair original source links with substantive claims. Agent interpretation remains separate from server arithmetic."
+            },
+            {
+              "description": "Catch up using the dedicated account\u2019s saved sample List.",
+              "prompt": "What did I miss from the OpenAI review sample List on 3 October 2026? Pick three original posts worth reading and explain why.",
+              "tools_triggered": "list_lists, then read_evidence with the selected List/revision; get_list only when requested membership itself is needed",
+              "expected_behavior": "Choose the account-owned OpenAI review sample List and complete UTC window [2026-10-03T00:00:00Z,2026-10-04T00:00:00Z). Pass the returned List identity/current revision directly into research; do not inspect every List member as a prerequisite. Preserve deduplicated author-OR-asset scope, read selected originals/context and cite three worthwhile findings honestly. Do not replace full scope with a newest-only sample or claim all relevant originals were checked before they were. Do not edit Lists, mark items seen or create alerts. Follow-up/recovery reuses exact received evidence when sufficient."
+            }
+          ],
+          "negative": [
+            {
+              "description": "An unrelated request should not trigger crypto research.",
+              "prompt": "What is the weather in Dublin tomorrow?",
+              "tools_triggered": "None",
+              "expected_behavior": "Use an appropriate weather capability or explain that CryptoSocials does not supply weather. Do not call CryptoSocials research or spend its credits."
+            },
+            {
+              "description": "Research access cannot execute a trade.",
+              "prompt": "Buy 100 euros of BTC for me using CryptoSocials.",
+              "tools_triggered": "None",
+              "expected_behavior": "Explain briefly that CryptoSocials cannot buy, sell or transfer crypto. Do not run paid research without a separate research request or claim a trade occurred."
+            },
+            {
+              "description": "Research access cannot publish to X.",
+              "prompt": "Post my bullish SUI opinion to X with CryptoSocials.",
+              "tools_triggered": "None",
+              "expected_behavior": "Explain that these tools cannot publish to X; optionally help draft wording in the conversation. Do not call a nonexistent write tool or claim publication."
+            }
+          ]
+        },
+        "demo_recording_url": "https://api.cryptosocials.net/review/openai-20260921-8fbbe946/demo.mp4?v=1.2.0",
+        "commerce": false
+      },
+      "publication": {
+        "release_notes": "1.3.0 aligns the existing plugin with the deployed MCP/REST research rebuild. New connected operations calculate complete accepted populations server-side before result paging, return full retained original wording and available context, preserve observed metric/price/source provenance, and provide permission-bound exact free recovery. Six independent MCP controls expose capabilities, balance, recent requests, status, exact recovery and cancellation with separate schemas and accurate read/cancel annotations. The REST action route and cached control requests remain compatible. Updated guides cover citations, Lists, ties, changed scope, attached versus independent prices, efficient body reading and recent-balance reuse. Cached published V1 calls remain supported during tool review. Current-source production acceptance independently checked 82 matching originals, complete MCP/REST arithmetic, exact recovery and ledger charges; ten mobile/desktop published-route checks passed. The preserved private connected-agent inventory is 209; component checks are not agent-question counts. The existing three approved starter questions, endpoint, stable identity, branding, account connection and tariff remain. Test cases are updated for V2; the retained short walkthrough illustrates supported legacy calls, not a new ChatGPT model evaluation."
+      }
+    }
+  },
+  "apps": "./.app.json"
+}