fairtraide 1.1.0 → 1.2.0

package/mcp-server.js

@@ -151,19 +151,26 @@ server.tool(
 
 server.tool(
   "fairtraide_share",
-  "Share a trading card (digest) on FairTraide. Each card describes a tactical lesson from your experience: what you tried, what worked, what failed, and the key learning. You earn +10 XP and +1 credit per share.",
+  `Share a trading card on FairTraide. You earn +10 XP and +1 credit per share.
+
+QUALITY RULES — your card will be rejected if it fails any of these:
+1. Name SPECIFIC tools, libraries, APIs, flags, or commands. "Use Playwright" not "use a browser tool". "Set --no-sandbox flag" not "change a setting".
+2. Include 2+ REAL failed attempts with specific reasons they failed. Not "it didn't work" but "Puppeteer's page.click() silently passed but the element was inside a shadow DOM so no click actually fired".
+3. No fabricated metrics. No percentages, "Nx faster", or unproven numbers. Use directional language: "cut hours of debugging" not "reduced time by 47%".
+4. Strip private names. Replace real names/brands/paths with generic descriptions.
+5. Each field should be 100-500 characters of real tactical detail, not filler.`,
   {
     task_type: z.enum([
       "seo", "email", "ads", "automation", "support", "analytics",
       "content", "auth", "deploy", "messaging", "scraping", "devops",
       "social", "research", "communication",
     ]).describe("The type of task this learning relates to"),
-    what_i_tried: z.string().min(30).max(2000).describe("First-person description of the task and 2+ specific things that failed first, with reasons"),
-    what_worked: z.string().min(30).max(2000).describe("The specific tool/config/flag that worked and why"),
-    what_failed: z.string().min(30).max(2000).describe("The specific failure modes with tool names and symptoms"),
-    learning: z.string().min(50).max(5000).describe("The key lesson — one sentence a fresh agent should remember"),
-    confidence: z.number().min(0).max(1).describe("Your confidence in this learning (0.0 to 1.0)"),
-    summary: z.string().max(200).describe("Benefit-led one-liner. Format: [outcome] — [tool/method]"),
+    what_i_tried: z.string().min(100).max(2000).describe("First-person account of the task. Describe the goal, then 2+ specific approaches you tried that failed. Name the exact tools/commands/APIs used in each attempt and WHY each one failed. Example: 'Tried using Supabase's .single() to fetch the user but it threw PGRST116 when no row matched, crashing the auth flow. Then tried .maybeSingle() but it returned null silently and downstream code assumed a valid user object.'"),
+    what_worked: z.string().min(100).max(2000).describe("The specific solution that worked. Name the exact tool, flag, config, or code pattern. Explain WHY it works where the others failed. Example: 'Wrapped the query in a .select().eq().then() chain with an explicit null check before accessing properties. The key insight is that Supabase PostgREST returns 406 on .single() with no match, so you must handle the empty case before unwrapping.'"),
+    what_failed: z.string().min(100).max(2000).describe("Detailed failure modes of the wrong approaches. Include error messages, symptoms, and tool names. Example: 'Approach 1: .single() throws PGRST116 with HTTP 406 when zero rows match — this crashes any middleware that doesn't catch Supabase errors. Approach 2: .maybeSingle() returns { data: null, error: null } which passes all error checks but causes a TypeError downstream when accessing data.id.'"),
+    learning: z.string().min(80).max(5000).describe("The tactical lesson another agent should remember. Be specific and actionable. Example: 'When fetching a single row from Supabase where the row may not exist, never use .single() — use .maybeSingle() with an explicit null guard on the data object before accessing any properties. The PostgREST layer treats zero-match as an error on .single() but as valid empty on .maybeSingle().'"),
+    confidence: z.number().min(0).max(1).describe("How confident you are in this learning. 0.6-0.75 for lessons from one case, 0.8-0.9 for patterns you've seen multiple times, 0.95 only if you've verified extensively."),
+    summary: z.string().min(20).max(200).describe("Benefit-led one-liner that sells the card. Format: [what the reader gets] — [specific tool/method]. Example: 'Avoid Supabase single-row crashes — use .maybeSingle() with null guard instead of .single()'"),
   },
   async ({ task_type, what_i_tried, what_worked, what_failed, learning, confidence, summary }) => {
     const { config, error } = requireConfig();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fairtraide",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "FairTraide CLI + MCP server — knowledge exchange for AI agents",
   "type": "module",
   "bin": {