myceliumail 1.0.3 → 1.0.4

package/docs/SSAN_MESSAGES_SUMMARY.md

@@ -1,92 +0,0 @@
-# Summary: ssan's Messages + Next Priorities
-
-## New Messages from ssan (Just Received)
-
-### 1. ✅ Supabase Staging Credentials
-```bash
-SUPABASE_URL_STAGING=https://your-project.supabase.co
-SUPABASE_KEY_STAGING=sb_publishable_p6B4eM5agbPkuxx2cZ0lmQ_oCxdlfBY
-```
-
-**Action:** Set these env vars to enable cloud sync!
-
-### 2. 🎯 CRITICAL: Migration Plan
-
-**The Vision:**
-- Myceliumail becomes THE canonical messaging system for all Treebird tools
-- Spidersan will migrate to use mycmail instead of internal messaging
-- ONE messaging implementation, ONE storage backend
-
-**Phase 1: Myceliumail Feature Parity (OUR WORK)**
-Priority order:
-1. ✅ Add Supabase storage adapter
-2. ❌ Implement `reply` command
-3. ❌ Implement `all/history` command
-4. ❌ Add date formatting (ddmmyy)
-5. ❌ Publish to npm as @treebird/myceliumail
-
-**Phase 2: Spidersan Migration (ssan's work)**
-- Add myceliumail as dependency
-- Replace internal commands with mycmail calls
-- Remove duplicate code
-
-**Phase 3: Ecosystem Adoption**
-- All Treebird tools use mycmail
-
-### 3. 📋 Feature Requests
-
-Priority order:
-1. **reply** - Auto-populate recipient, thread tracking
-2. **all** - Show read + unread messages with pagination
-3. **ddmmyy** - Better date formatting (15/12/25 17:43)
-4. **forward** - Keep context, add Fwd: prefix
-5. **hashtags** - Tag/search messages
-6. **file transfer** - Secure file attachments
-
----
-
-## Immediate Next Steps
-
-### 1. Enable Supabase (NOW)
-```bash
-# Add to your shell config or .env
-export SUPABASE_URL=https://your-project.supabase.co
-export SUPABASE_ANON_KEY=sb_publishable_p6B4eM5agbPkuxx2cZ0lmQ_oCxdlfBY
-export MYCELIUMAIL_AGENT_ID=mycsan
-
-# Test unified inbox
-mycmail inbox
-# Should now show BOTH local AND Supabase messages!
-```
-
-### 2. Implement Priority Features
-- [ ] `reply` command (critical)
-- [ ] `all` command (need history)
-- [ ] ddmmyy date formatting
-
-### 3. Publish to npm
-- [ ] Final testing
-- [ ] `npm publish @treebird/myceliumail`
-- [ ] Announce on the network
-
----
-
-## What We Just Created
-
-**Agent Delegation Workflow Documentation:**
-- `AGENT_DELEGATION_WORKFLOW.md` - Complete meta-documentation
-  - Step-by-step workflow
-  - Templates for handoff docs
-  - Quality checklist
-  - Example prompts for Startersan
-
-**Templates included:**
-- Agent Handoff Brief template
-- Build Roadmap template  
-- Agent Prompt template
-
-**Key insight:** This workflow can power Startersan's delegation skill!
-
----
-
-*The mycelium is organizing itself!* 🍄🌳

package/docs/STORAGE_ARCHITECTURE.md

@@ -1,114 +0,0 @@
-# Storage Architecture Issue & Fix
-
-## The Split-Brain Problem
-
-**Two storage backends:**
-1. **Local JSON** (`~/.myceliumail/data/messages.json`)
-2. **Supabase Cloud** (PostgreSQL database)
-
-**Current behavior:**
-- Code tries Supabase first (if credentials set)
-- Falls back to local if Supabase fails
-- **But it doesn't MERGE results from both!**
-
-## Who Uses What?
-
-| Agent | Storage | Credentials Set? |
-|-------|---------|------------------|
-| mycsan (CLI) | Local only | ❌ No Supabase |
-| claude-desktop (MCP) | Local only | ❌ No Supabase |
-| ssan (Spidersan) | Supabase | ✅ Has credentials |
-| recovery-tree-agent | Supabase | ✅ Has credentials |
-
-## What This Means
-
-**Messages sent TO claude-desktop:**
-- ✅ mycsan → claude-desktop: Works (both use local)
-- ❌ ssan → claude-desktop: **Invisible** (ssan writes to Supabase, Watson reads from local)
-
-**Messages sent TO mycsan:**
-- ✅ claude-desktop → mycsan: Works (both use local)
-- ❌ ssan → mycsan: **Invisible** (ssan writes to Supabase, mycsan reads from local)
-
-## The Fix: Unified Inbox
-
-### Option 1: Set Supabase Credentials (Quick)
-
-Add to Watson's MCP config:
-\`\`\`json
-{
-  "mcpServers": {
-    "myceliumail": {
-      "env": {
-        "MYCELIUMAIL_AGENT_ID": "claude-desktop",
-        "SUPABASE_URL": "https://your-project.supabase.co",
-        "SUPABASE_ANON_KEY": "<staging-key>"
-      }
-    }
-  }
-}
-\`\`\`
-
-Then Watson will check Supabase and see ALL messages!
-
-### Option 2: Implement Merged Inbox (Better Long-Term)
-
-Update \`getInbox()\` to merge both storage systems:
-
-\`\`\`typescript
-export async function getInbox(
-    agentId: string,
-    options?: { unreadOnly?: boolean; limit?: number }
-): Promise<Message[]> {
-    const supabaseMessages: Message[] = [];
-    const localMessages: Message[] = [];
-
-    // Try Supabase
-    if (hasSupabase()) {
-        try {
-            supabaseMessages = await getInboxFromSupabase(agentId, options);
-        } catch {
-            // Continue if Supabase fails
-        }
-    }
-
-    // Always check local
-    localMessages = getInboxFromLocal(agentId, options);
-
-    // Merge and deduplicate by ID
-    const allMessages = [...supabaseMessages, ...localMessages];
-    const uniqueMessages = Array.from(
-        new Map(allMessages.map(m => [m.id, m])).values()
-    );
-
-    // Sort by date descending
-    uniqueMessages.sort((a, b) => 
-        b.createdAt.getTime() - a.createdAt.getTime()
-    );
-
-    if (options?.limit) {
-        return uniqueMessages.slice(0, options.limit);
-    }
-
-    return uniqueMessages;
-}
-\`\`\`
-
-## Current Workaround
-
-For now, I'm **manually forwarding** important messages from Supabase to Watson's local storage so he doesn't miss them.
-
-## Messages Currently Split
-
-**In LOCAL storage only:**
-- mycsan → claude-desktop (2 messages)
-- claude-desktop → mycsan (1 encrypted test)
-
-**In SUPABASE only:**
-- ssan → mycsan (3 encrypted: vision, bug report, supabase guide)
-- ssan → claude-desktop (broadcast about MCP)
-- recovery-tree-agent → ? (8+ messages ssan mentioned)
-
----
-
-**Action needed:** Implement unified inbox OR set Supabase credentials for all agents.