npm - @hybridlabor-api/aos - Versions diffs - 4.3.0 → 4.4.0 - Mend

@hybridlabor-api/aos 4.3.0 → 4.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1052) hide show

package/mcps/windows-computer-use-mcp/docs/_stale/notepadpp/LANGUAGE_SERVER_PROTOCOL_EXPLAINED.md DELETED Viewed

@@ -1,416 +0,0 @@
-# 🧠 Language Server Protocol (LSP) - Explained
-**Created**: October 8, 2025
-**Context**: Understanding Serena MCP's semantic code understanding
----
-## 🎯 **What is LSP?**
-**Language Server Protocol** (LSP) is a **standardized protocol** created by **Microsoft in 2016** for providing language intelligence (code completion, go-to-definition, refactoring) to ANY text editor.
-**Not new academic research** - it's 9 years old, battle-tested, and powers VS Code! ✅
----
-## 🏆 **The Problem LSP Solved**
-### **Before LSP (The Dark Ages)**
-Every text editor had to implement language support separately:
-**Example: Python support**
-- **VS Code**: Implemented Python parser, AST analysis, symbol resolution
-- **Sublime Text**: Implemented their OWN Python parser
-- **Atom**: Implemented YET ANOTHER Python parser
-- **Vim**: Yet another...
-- **Emacs**: Yet another...
-**Result**:
-- ❌ Duplicate work (5 editors = 5 Python parsers!)
-- ❌ Inconsistent features
-- ❌ Bugs in each implementation
-- ❌ Hard to add new languages (had to convince each editor team)
----
-### **After LSP (The Renaissance)**
-**One language = One server** that works with ALL editors:
-```
-┌─────────────┐
-│  VS Code    │─┐
-├─────────────┤ │
-│  Cursor     │─┤
-├─────────────┤ │     ┌──────────────────┐
-│  Sublime    │─┼────→│  Python LSP      │
-├─────────────┤ │     │  (pylsp)         │
-│  Vim        │─┤     └──────────────────┘
-├─────────────┤ │
-│  Emacs      │─┘
-└─────────────┘
-```
-**Result**:
-- ✅ **Write once, use everywhere**
-- ✅ Consistent features across all editors
-- ✅ Easy to add new languages (just write one server)
-- ✅ Better quality (one implementation = more focus)
----
-## 🔧 **How LSP Works**
-### **Architecture**
-```
-┌──────────────────┐          ┌─────────────────────┐
-│                  │          │                     │
-│  Text Editor     │  ←LSP→   │  Language Server    │
-│  (Client)        │          │  (Server)           │
-│                  │          │                     │
-│  - VS Code       │          │  - Analyzes code    │
-│  - Cursor        │          │  - Maintains AST    │
-│  - Sublime       │          │  - Tracks symbols   │
-│  - Any editor!   │          │  - Finds refs       │
-│                  │          │                     │
-└──────────────────┘          └─────────────────────┘
-```
-### **Communication Protocol**
-**JSON-RPC over stdio/HTTP:**
-**Example: Go to Definition**
-1. **Editor sends**:
-   ```json
-   {
-     "jsonrpc": "2.0",
-     "id": 1,
-     "method": "textDocument/definition",
-     "params": {
-       "textDocument": {"uri": "file:///code.py"},
-       "position": {"line": 10, "character": 15}
-     }
-   }
-   ```
-2. **Language server analyzes code and responds**:
-   ```json
-   {
-     "jsonrpc": "2.0",
-     "id": 1,
-     "result": {
-       "uri": "file:///utils.py",
-       "range": {
-         "start": {"line": 42, "character": 4},
-         "end": {"line": 42, "character": 20}
-       }
-     }
-   }
-   ```
-3. **Editor jumps to utils.py line 42!**
-**Same protocol works for**: autocomplete, hover tooltips, refactoring, diagnostics, etc.
----
-## 🎓 **LSP Capabilities**
-**What Language Servers Provide:**
-### **Code Intelligence**
-- ✅ **Go to definition** - Jump to where symbol is defined
-- ✅ **Find references** - Find all uses of a symbol
-- ✅ **Hover tooltips** - Show documentation on hover
-- ✅ **Autocomplete** - IntelliSense suggestions
-- ✅ **Signature help** - Function parameter hints
-### **Code Quality**
-- ✅ **Diagnostics** - Errors, warnings (like linting)
-- ✅ **Code actions** - Quick fixes, refactorings
-- ✅ **Formatting** - Auto-format code
-- ✅ **Rename symbol** - Rename across entire project
-### **Code Navigation**
-- ✅ **Document symbols** - Outline view of file structure
-- ✅ **Workspace symbols** - Search all symbols in project
-- ✅ **Call hierarchy** - Who calls this function?
-- ✅ **Type hierarchy** - Class inheritance tree
----
-## 🌟 **LSP in the Wild**
-### **Major Language Servers**
-| Language | Server Name | Stars | Status |
-|----------|-------------|-------|--------|
-| **Python** | pylsp | 2.5k | ✅ Mature |
-| **JavaScript/TypeScript** | typescript-language-server | 1.8k | ✅ Official |
-| **Rust** | rust-analyzer | 15k | ✅ Amazing |
-| **Go** | gopls | Official | ✅ Google-backed |
-| **Java** | eclipse.jdt.ls | Official | ✅ Eclipse |
-| **C/C++** | clangd | Official | ✅ LLVM |
-| **C#** | omnisharp | 1.7k | ✅ Microsoft |
-**Over 100+ language servers exist!**
----
-## 🚀 **How Serena Uses LSP**
-### **The Genius of Serena**
-**Traditional MCP servers**:
-- Read files as text
-- Use grep/regex to search
-- No code understanding
-- Send entire files to AI
-**Serena MCP**:
-- Uses LSP to **understand code semantically**
-- Knows: "This is a class, this is a function, these are related"
-- Can answer: "Find all classes that implement IAuthService"
-- Sends **only relevant code** to AI (70% token savings!)
-### **Example: Finding Authentication Code**
-**Without Serena:**
-```
-AI: Reads every .py file
-AI: Searches for "auth", "login", "password"
-AI: Sends 50,000 tokens of code
-AI: You pay for all that!
-```
-**With Serena:**
-```
-AI: Calls Serena's find_symbol("authenticate")
-Serena: Uses Python LSP to find exact matches
-Serena: Returns only the 5 relevant functions
-AI: Sends 5,000 tokens
-You save: 90% tokens! 🎉
-```
----
-## 🎨 **The Dashboard**
-**Serena's Dashboard** = Live visualization at http://localhost:24282
-### **What You See**
-**1. Tool Usage Stats**
-```
-find_symbol:           45 calls
-find_references:       23 calls
-replace_symbol_body:   12 calls
-read_file:             89 calls
-```
-**2. Language Server Status**
-```
-✅ Python LSP:     Running (pid 12345)
-✅ TypeScript LSP: Running (pid 12346)
-❌ Rust Analyzer:  Not needed (no Rust files)
-```
-**3. Project Memories**
-```
-.serena/memories/
-  - architecture.md
-  - api-structure.md
-  - database-schema.md
-  - authentication-flow.md
-```
-**4. Real-Time Logs**
-```
-[14:23:45] find_symbol: UserService
-[14:23:46] LSP response: Found in src/services/user.py:42
-[14:23:47] Token estimate: 2,341 saved
-```
-**5. Session Analytics**
-```
-Total calls:     234
-Tokens saved:    ~125,000 (estimated)
-Avg response:    0.3s
-Active duration: 2h 15m
-```
----
-## 💡 **LSP vs Traditional Tools**
-| Feature | grep/regex | LSP |
-|---------|-----------|-----|
-| **Find "User"** | All text occurrences | Only User class/symbol |
-| **Understands code** | No | Yes |
-| **Find references** | Text search (can miss) | Semantic (exact) |
-| **Rename safely** | Can't | Yes (updates all refs) |
-| **Knows relationships** | No | Yes (inheritance, calls) |
-| **Speed** | Fast | Fast (indexed) |
-| **Accuracy** | ~70% | ~99% |
----
-## 🔬 **LSP Deep Dive**
-### **How It Actually Works**
-**1. Editor opens file:**
-```json
-{
-  "method": "textDocument/didOpen",
-  "params": {
-    "textDocument": {
-      "uri": "file:///code.py",
-      "languageId": "python",
-      "version": 1,
-      "text": "def authenticate(user): ..."
-    }
-  }
-}
-```
-**2. Language server parses:**
-- Builds Abstract Syntax Tree (AST)
-- Indexes symbols (functions, classes, variables)
-- Tracks relationships (calls, imports, inheritance)
-- Maintains in-memory representation
-**3. Editor requests info:**
-```json
-{"method": "textDocument/completion"}
-{"method": "textDocument/definition"}
-{"method": "textDocument/references"}
-```
-**4. Server responds with semantic data:**
-- Exact locations
-- Type information
-- Documentation
-- Related symbols
-**All in milliseconds!** ⚡
----
-## 🎯 **Why This Matters for Serena**
-**Serena = AI + LSP**
-**What Serena does**:
-1. Starts language servers for your project
-2. AI asks questions via MCP tools
-3. Serena translates to LSP queries
-4. LSP returns semantic answers
-5. Serena sends precise results to AI
-6. **70% fewer tokens needed!**
-**It's like giving Claude/Cursor the same intelligence VS Code has!**
----
-## 📚 **LSP History & Context**
-### **Timeline**
-- **2016**: Microsoft releases LSP with VS Code
-- **2017**: Eclipse, Atom, Vim adopt it
-- **2018**: Every major editor supports LSP
-- **2019**: 50+ language servers exist
-- **2025**: 100+ language servers, industry standard
-- **2025**: Serena applies LSP to AI assistants! 🚀
-### **Why Microsoft Created It**
-**Original problem**:
-- VS Code team wanted to support 50+ languages
-- Couldn't implement parsers for each language
-- Needed a way to delegate language intelligence
-**Solution**:
-- Define a standard protocol
-- Let language communities build servers
-- VS Code just implements the client
-- Win-win: Editor gets all languages, communities control their implementations
----
-## 🔗 **LSP in Other Tools**
-### **Editors Using LSP**
-- VS Code (pioneer)
-- Cursor (VS Code fork)
-- Sublime Text (via LSP package)
-- Vim/Neovim (via plugins)
-- Emacs (via lsp-mode)
-- Atom (RIP)
-- Kate, Geany, and dozens more
-### **Beyond Editors**
-**LSP is used in**:
-- Code review tools (GitHub Codespaces)
-- CI/CD linters (use LSP for semantic checks)
-- Documentation generators (understand code structure)
-- **Now: AI assistants via Serena!** 🎉
----
-## 🎓 **Academic Roots**
-**You're right that it has academic connections!**
-**Influenced by**:
-- **Compiler design** - Lexing, parsing, semantic analysis
-- **IDE research** - Eclipse JDT (Java Development Tools)
-- **Programming language theory** - Type systems, abstract syntax trees
-**Not brand new research** - but a brilliant **engineering solution** to a real problem!
-**Microsoft's paper**: "Language Server Protocol: The Missing Link"
----
-## 💡 **Why This is Exciting for You**
-**Serena + notepadpp-mcp connection**:
-1. **Learn from Serena's design**
-   - See how they use 15 tools vs Basic Memory's 43
-   - Portmanteau approach in action
-   - Dashboard for monitoring
-2. **Complement notepadpp-mcp**
-   - notepadpp-mcp: Text editing in Notepad++
-   - Serena: Semantic code understanding
-   - Together: Powerful combo!
-3. **Dashboard inspiration**
-   - Serena has localhost:24282 dashboard
-   - Could add similar to notepadpp-mcp?
-   - Visualize tool usage, Notepad++ state
-4. **Token savings**
-   - Helps with your €100/month budget
-   - More AI assistance for same cost
-   - Smart, efficient code navigation
----
-## 🚀 **Let's Install It!**
-**Installing for notepadpp-mcp repo specifically** (not global):
-<function_calls>
-<invoke name="run_terminal_cmd">
-<parameter name="command">if (-not (Test-Path ".cursor")) { New-Item -Path ".cursor" -ItemType Directory -Force; Write-Host "✅ Created .cursor folder" } else { Write-Host "✅ .cursor folder exists" }

package/mcps/windows-computer-use-mcp/docs/_stale/notepadpp/MCP_TOOL_CORRUPTION_ISSUE.md DELETED Viewed

@@ -1,279 +0,0 @@
-# 🚨 MCP Tool Corruption Issue - Lesson Learned
-**Date**: October 8, 2025
-**Severity**: HIGH
-**Status**: IDENTIFIED - Our tools likely caused Notepad++ corruption
----
-## 🎯 **The Discovery**
-**User Report**:
-- Notepad++ worked fine for months/years
-- Started having white-on-white text issue ~1 week ago
-- **Timeline matches**: Testing of notepadpp-mcp tools
-- **Conclusion**: Our MCP tools likely corrupted Notepad++ config
----
-## 🔍 **Suspected Culprits**
-### **Tool 1: `fix_invisible_text()`**
-**What it does**:
-```python
-# Lines 1741-1917 in server.py
-- Opens Style Configurator via keyboard automation
-- Navigates menus blindly with Tab/Arrow keys
-- Tries to change theme and colors
-- Presses buttons without visual confirmation
-```
-**Risk**:
-- ❌ Keyboard navigation can go wrong
-- ❌ Dialog layouts differ by version
-- ❌ Tab counts can be off
-- ❌ Can activate wrong settings
-- ❌ **Can corrupt stylers.xml**
----
-### **Tool 2: `fix_display_issue()`**
-**What it does**:
-```python
-# Lines 1922-2022 in server.py
-- Opens Settings menu
-- Navigates to Style Configurator
-- Tries to reset theme
-- More blind keyboard automation
-```
-**Same risks as above**
----
-## ⚠️ **The Problem with These Tools**
-**Blind UI Automation**:
-```python
-# Example from fix_invisible_text()
-keybd_event(win32con.VK_TAB, 0, 0, 0)  # Press Tab
-keybd_event(win32con.VK_TAB, 0, win32con.KEYEVENTF_KEYUP, 0)
-await asyncio.sleep(0.1)
-# Press Tab 2 times to "navigate to theme dropdown"
-for _ in range(2):
-    keybd_event(win32con.VK_TAB, 0, 0, 0)
-    ...
-```
-**Why This is Dangerous**:
-- 🚨 Assumes dialog layout (can change between versions)
-- 🚨 No visual verification
-- 🚨 Can focus wrong controls
-- 🚨 Can change unintended settings
-- 🚨 **Can corrupt configuration files!**
----
-## 📋 **What Likely Happened**
-**Scenario**:
-1. User runs `fix_invisible_text()` or `fix_display_issue()`
-2. Tool opens Style Configurator
-3. Blind Tab navigation focuses wrong control
-4. Tool changes wrong setting or corrupts theme
-5. Notepad++ saves corrupted stylers.xml
-6. Text becomes invisible (white-on-white)
-7. Split view gets activated accidentally
-8. User is stuck with broken Notepad++
----
-## ✅ **Immediate Fix Applied**
-**For the current corruption**:
-1. Stopped Notepad++
-2. Deleted corrupted config files (config.xml, stylers.xml, session.xml)
-3. Started fresh with `-nosession` flag
-4. Notepad++ creates new default configs
-**Expected**: Should work now!
----
-## 🔧 **Long-Term Solutions**
-### **Option 1: Deprecate These Tools** (Recommended)
-**Mark as DANGEROUS**:
-```python
-@app.tool()
-@deprecated("This tool uses blind UI automation and can corrupt Notepad++ config. Use manual Style Configurator instead.")
-async def fix_invisible_text():
-    return {
-        "success": False,
-        "error": "This tool is deprecated due to config corruption risk",
-        "recommendation": "Manually use: Settings → Style Configurator → Select theme"
-    }
-```
----
-### **Option 2: Rewrite with Direct API**
-**Instead of keyboard automation**, use Scintilla messages directly:
-```python
-# Safer approach - direct Scintilla color setting
-SCI_STYLESETFORE = 2051
-SCI_STYLESETBACK = 2052
-STYLE_DEFAULT = 32
-# Set default style colors directly
-await controller.send_message(
-    controller.scintilla_hwnd,
-    SCI_STYLESETFORE,
-    STYLE_DEFAULT,
-    0x000000  # Black
-)
-await controller.send_message(
-    controller.scintilla_hwnd,
-    SCI_STYLESETBACK,
-    STYLE_DEFAULT,
-    0xFFFFFF  # White
-)
-```
-**Benefits**:
-- ✅ Direct API calls (no UI automation)
-- ✅ No risk of wrong button presses
-- ✅ Immediate effect
-- ✅ No config file corruption
-- ✅ Reversible
----
-### **Option 3: Add Safety Warnings**
-**If keeping the tools**:
-```python
-@app.tool()
-async def fix_invisible_text():
-    """
-    ⚠️ WARNING: This tool uses UI automation and may corrupt Notepad++ config!
-    BACKUP YOUR CONFIG FIRST:
-    - Copy C:\\Users\\...\\AppData\\Roaming\\Notepad++\\ to safe location
-    SAFER ALTERNATIVE:
-    - Manually use Settings → Style Configurator
-    - Select "Obsidian" or "Default" theme
-    USE AT YOUR OWN RISK!
-    """
-    # ... existing code ...
-```
----
-## 📊 **Impact Assessment**
-**Tools with UI Automation Risk**:
-1. `fix_invisible_text()` - HIGH RISK ⚠️
-2. `fix_display_issue()` - HIGH RISK ⚠️
-3. `install_plugin()` - MEDIUM RISK ⚠️
-4. `execute_plugin_command()` - MEDIUM RISK ⚠️
-5. `find_text()` - LOW RISK (simpler automation)
-**Safe tools**:
-- `open_file()` - Uses command line ✅
-- `new_file()`, `save_file()` - Simple Ctrl+N/S ✅
-- `insert_text()` - Uses clipboard ✅
-- All linting tools - File operations only ✅
----
-## 🎯 **Recommendations**
-### **Immediate**
-1. **Deprecate** `fix_invisible_text()` and `fix_display_issue()`
-2. **Add warnings** to plugin automation tools
-3. **Document** this corruption risk
-4. **Test** all tools for side effects
-### **v1.3.0 Release**
-1. **Rewrite** display fix tools with direct Scintilla API
-2. **Add backup** functionality before any UI automation
-3. **Implement** verification after tool execution
-4. **Create** restore functionality
----
-## 📝 **Documentation Updates Needed**
-### **README.md**
-Add warning:
-```markdown
-### ⚠️ Known Issues
-**Display Fix Tools** (`fix_invisible_text`, `fix_display_issue`):
-- Use UI automation which can corrupt Notepad++ config
-- **Recommend**: Manual theme changes via Style Configurator
-- **If using**: Backup config first
-- **v1.3.0**: Will be rewritten with safe direct API calls
-```
-### **Tool Descriptions**
-Update warnings in server.py docstrings.
----
-## 🏆 **Lesson Learned**
-**Blind UI automation is dangerous**:
-- ❌ Can't verify what control is focused
-- ❌ Dialog layouts change between versions
-- ❌ Can press wrong buttons
-- ❌ Can corrupt configuration
-- ❌ Hard to debug when it goes wrong
-**Better approaches**:
-- ✅ Direct API calls (Scintilla messages)
-- ✅ File-based operations
-- ✅ Command-line parameters
-- ✅ With visual verification
-- ✅ With automatic backups
----
-## 📞 **User Impact**
-**This user's experience**:
-- Spent hours troubleshooting
-- Multiple fix attempts
-- Fresh install required
-- Still potentially broken via RustDesk
-**Our responsibility**:
-- Remove dangerous tools
-- Add proper warnings
-- Implement safer alternatives
-- Prevent future corruption
----
-*Issue documented: October 8, 2025*
-*Affected tools: fix_invisible_text, fix_display_issue*
-*Root cause: Blind UI automation*
-*Action: Deprecate or rewrite with safe API*
-*Priority: HIGH*
-**Our tools should NEVER corrupt user configurations!** ⚠️