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

@hybridlabor-api/aos 4.2.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 (1098) hide show

package/mcps/windows-computer-use-mcp/docs/_stale/repository-protection/BACKUP_AND_RECOVERY_GUIDE.md DELETED Viewed

@@ -1,455 +0,0 @@
-# 🛡️ Git Repository Backup & Recovery Guide
-**Your Complete Protection Strategy for notepadpp-mcp**
----
-## 🎯 **TL;DR - Quick Protection**
-```powershell
-# 1. Create backup branch (do this NOW)
-git branch backup-safe
-git push origin backup-safe
-# 2. Run manual backup
-.\scripts\backup-repo.ps1
-# 3. Done! You're protected.
-```
----
-## 📊 **Multi-Layer Protection Strategy**
-Your repository is protected by **5 independent layers**:
-| Layer | What It Protects | Recovery Time | Auto? |
-|-------|------------------|---------------|-------|
-| **1. GitHub Remote** | All commits, history | Instant | ✅ |
-| **2. Git Reflog** | Local operations (90 days) | Instant | ✅ |
-| **3. Backup Branches** | Known-good states | Instant | Manual |
-| **4. Local Bundles** | Complete repo copy | 5 minutes | Setup |
-| **5. Multiple Remotes** | GitHub outages | Instant | Setup |
----
-## 🚨 **Layer 1: GitHub Already Protects You!**
-### What GitHub Keeps
-Even if your local repo is "borked":
-- ✅ **All commits** - Full history is on GitHub
-- ✅ **All branches** - Including deleted ones (30 days)
-- ✅ **All tags** - Including deleted ones (can restore)
-- ✅ **Pull request history** - Even if closed
-- ✅ **Issue history** - All discussions
-### Recovery from GitHub
-```powershell
-# If local repo is broken, just re-clone
-cd D:\Dev\repos
-Rename-Item notepadpp-mcp notepadpp-mcp-broken
-git clone https://github.com/sandraschi/notepadpp-mcp.git
-cd notepadpp-mcp
-# Your code is back! ✅
-```
-**This works even if Cursor/AI messed up your local copy.**
----
-## 🔄 **Layer 2: Git Reflog (Auto-Backup)**
-Git automatically tracks EVERYTHING you do for 90 days:
-### View All Operations
-```powershell
-# See everything that happened (even "deleted" commits)
-git reflog
-# Output shows:
-# b4b21d3 HEAD@{0}: commit: Release v1.2.0
-# abc1234 HEAD@{1}: commit: Previous commit
-# def5678 HEAD@{2}: reset: moving to HEAD~1
-# (and so on for 90 days)
-```
-### Recover "Lost" Work
-```powershell
-# Undo last 3 operations
-git reset --hard HEAD@{3}
-# Or recover specific commit
-git reflog  # Find the commit hash
-git cherry-pick abc1234  # Restore that commit
-# Or create branch from old state
-git branch recovered-work HEAD@{5}
-```
-**The reflog is your time machine - use it freely!**
----
-## 🌿 **Layer 3: Backup Branches (Recommended)**
-### Strategy: Snapshot Before Major Changes
-```powershell
-# Before ANY risky operation, create a backup branch
-git branch backup-before-cursor-push
-git push origin backup-before-cursor-push
-# Now do risky operation...
-# If it fails, you can restore:
-git reset --hard backup-before-cursor-push
-```
-### Automated Backup Branch
-Add to your workflow:
-```powershell
-# Create daily backup branch (add to Task Scheduler)
-$Date = Get-Date -Format "yyyy-MM-dd"
-git branch "backup-$Date"
-git push origin "backup-$Date"
-# Clean old backup branches (keep 30 days)
-git branch | Where-Object { $_ -match 'backup-\d{4}-\d{2}-\d{2}' } |
-    Where-Object {
-        $BranchDate = [DateTime]::ParseExact($_.Substring(7), "yyyy-MM-dd", $null)
-        $BranchDate -lt (Get-Date).AddDays(-30)
-    } | ForEach-Object {
-        git branch -D $_
-        git push origin --delete $_
-    }
-```
----
-## 📦 **Layer 4: Local Git Bundles (Best Practice)**
-### What Are Git Bundles?
-A **single file** containing your entire repository:
-- ✅ All commits, branches, tags
-- ✅ Complete history
-- ✅ Can restore ANYWHERE
-- ✅ ~2-5 MB per backup
-### Manual Backup
-```powershell
-# Create backup
-.\scripts\backup-repo.ps1
-# Default location: D:\Backups\notepadpp-mcp\
-# Creates: notepadpp-mcp_2025-10-08_14-30-00.bundle
-```
-### Automated Daily Backups
-#### Setup Windows Task Scheduler
-```powershell
-# Create scheduled task (run as Administrator)
-$Action = New-ScheduledTaskAction -Execute "PowerShell.exe" `
-    -Argument "-NoProfile -ExecutionPolicy Bypass -File `"D:\Dev\repos\notepadpp-mcp\scripts\backup-repo.ps1`""
-$Trigger = New-ScheduledTaskTrigger -Daily -At 3:00AM
-$Settings = New-ScheduledTaskSettingsSet -StartWhenAvailable -RunOnlyIfNetworkAvailable
-Register-ScheduledTask -TaskName "Notepadpp-MCP Backup" `
-    -Action $Action `
-    -Trigger $Trigger `
-    -Settings $Settings `
-    -Description "Daily backup of notepadpp-mcp repository"
-# Verify
-Get-ScheduledTask -TaskName "Notepadpp-MCP Backup"
-```
-#### Test the Backup
-```powershell
-# Run backup manually
-.\scripts\backup-repo.ps1
-# Should create: D:\Backups\notepadpp-mcp\notepadpp-mcp_[timestamp].bundle
-```
-### Restore from Bundle
-```powershell
-# Option 1: Clone from bundle to new directory
-git clone D:\Backups\notepadpp-mcp\notepadpp-mcp_2025-10-08.bundle restored-repo
-cd restored-repo
-git remote set-url origin https://github.com/sandraschi/notepadpp-mcp.git
-# Option 2: Restore to existing repo
-cd D:\Dev\repos\notepadpp-mcp
-git bundle unbundle D:\Backups\notepadpp-mcp\notepadpp-mcp_2025-10-08.bundle
-git reset --hard origin/main
-```
----
-## 🌐 **Layer 5: Multiple Git Remotes (Advanced)**
-### Add Backup Remote (GitLab, Bitbucket, etc.)
-```powershell
-# Add GitLab as backup remote
-git remote add backup https://gitlab.com/yourusername/notepadpp-mcp.git
-# Push to both remotes
-git push origin main
-git push backup main
-# Or push to both at once
-git remote set-url --add --push origin https://github.com/sandraschi/notepadpp-mcp.git
-git remote set-url --add --push origin https://gitlab.com/yourusername/notepadpp-mcp.git
-# Now 'git push origin main' pushes to BOTH!
-```
-### Local Network Backup
-```powershell
-# Create bare repo on network drive or second disk
-git clone --bare . E:\GitBackups\notepadpp-mcp.git
-# Add as remote
-git remote add localbackup E:\GitBackups\notepadpp-mcp.git
-# Push to local backup
-git push localbackup --all
-git push localbackup --tags
-```
----
-## 🔧 **Protection Best Practices**
-### Before Using Cursor/AI for Git Operations
-```powershell
-# 1. Create safety branch
-git branch pre-cursor-operation
-git push origin pre-cursor-operation
-# 2. Check current state
-git status
-git log --oneline -5
-# 3. Now let Cursor/AI do its thing
-# 4. If something goes wrong:
-git reset --hard pre-cursor-operation
-```
-### Branch Protection Rules (GitHub)
-Enable on GitHub to prevent force-pushes:
-1. Go to: `Settings` > `Branches`
-2. Click `Add rule` for `main`
-3. Enable:
-   - ✅ Require pull request before merging
-   - ✅ Require status checks to pass
-   - ✅ Do not allow force pushes
-   - ✅ Do not allow deletions
-**This prevents Cursor from force-pushing to main!**
-### Review Before Pushing
-```powershell
-# Always review what will be pushed
-git log origin/main..HEAD  # Commits to be pushed
-git diff origin/main HEAD  # Changes to be pushed
-# If you see something wrong, DON'T PUSH
-# Instead, fix it locally first
-```
----
-## 🚑 **Emergency Recovery Scenarios**
-### Scenario 1: Cursor Pushed Wrong Code
-```powershell
-# Find the good commit
-git log --oneline -10
-# Reset to good commit (local only)
-git reset --hard abc1234
-# Force push (if you're sure)
-git push origin main --force-with-lease
-# Or create new branch and PR
-git branch fix-cursor-mistake
-git push origin fix-cursor-mistake
-# Then merge via GitHub PR
-```
-### Scenario 2: Accidentally Deleted Branch
-```powershell
-# Find the branch in reflog
-git reflog | Select-String "branch-name"
-# Restore it
-git branch branch-name abc1234  # Use commit hash from reflog
-git push origin branch-name
-```
-### Scenario 3: Local Repo Completely Broken
-```powershell
-# Nuclear option: Re-clone
-cd D:\Dev\repos
-Rename-Item notepadpp-mcp notepadpp-mcp-broken
-git clone https://github.com/sandraschi/notepadpp-mcp.git
-cd notepadpp-mcp
-# Copy over any uncommitted work
-Copy-Item ..\notepadpp-mcp-broken\scripts\new-script.ps1 .\scripts\
-```
-### Scenario 4: Lost Uncommitted Work
-```powershell
-# Check git stash
-git stash list
-# Restore from stash
-git stash pop
-# Or use VS Code local history (if enabled)
-# File > Preferences > Settings > "Local History"
-```
----
-## 📋 **Recommended Setup Checklist**
-### Immediate (Do Now)
-- [ ] Create backup branch: `git branch backup-safe; git push origin backup-safe`
-- [ ] Run manual backup: `.\scripts\backup-repo.ps1`
-- [ ] Enable GitHub branch protection on `main`
-- [ ] Test recovery: Clone from GitHub to verify
-### This Week
-- [ ] Set up automated daily backups (Task Scheduler)
-- [ ] Create second remote (GitLab or local)
-- [ ] Document your backup locations
-- [ ] Test bundle restore procedure
-### Monthly Maintenance
-- [ ] Verify backups are running
-- [ ] Test restore from bundle
-- [ ] Clean old backup branches
-- [ ] Review reflog for any issues
----
-## 🎯 **Your Current Protection Status**
-Based on what we just set up:
-✅ **Layer 1**: GitHub remote (automatic)
-✅ **Layer 2**: Git reflog (automatic, 90 days)
-🔄 **Layer 3**: Backup branches (manual, but easy)
-✅ **Layer 4**: Bundle script created (needs scheduling)
-⏳ **Layer 5**: Multiple remotes (optional, not set up)
-**Protection Level**: **GOOD** (3/5 layers active)
-**Recommendation**: Set up automated bundling for **EXCELLENT**
----
-## 💡 **Daily Workflow Tips**
-### Before Major Operations
-```powershell
-# Quick safety snapshot
-git branch backup-$(Get-Date -Format 'yyyy-MM-dd-HHmm')
-git push origin backup-$(Get-Date -Format 'yyyy-MM-dd-HHmm')
-```
-### After Cursor Makes Changes
-```powershell
-# Review changes before committing
-git status
-git diff
-# If unsure, create branch first
-git checkout -b cursor-changes
-git add .
-git commit -m "Cursor changes"
-# Test, then merge to main
-git checkout main
-git merge cursor-changes
-```
-### Weekly Health Check
-```powershell
-# Verify backups exist
-Get-ChildItem D:\Backups\notepadpp-mcp\*.bundle |
-    Sort-Object LastWriteTime -Descending |
-    Select-Object -First 5
-# Verify GitHub is synced
-git fetch origin
-git status
-```
----
-## 🏆 **Summary: You're Protected!**
-Your repository is protected by **multiple independent layers**:
-1. **GitHub** keeps everything (even if local is broken)
-2. **Git reflog** is a 90-day time machine
-3. **Backup branches** for known-good states
-4. **Local bundles** for offline recovery
-5. **Multiple remotes** for redundancy
-**Bottom Line**: It's almost impossible to permanently lose your code with these protections in place.
----
-## 📞 **Need Help?**
-If something goes wrong:
-1. **DON'T PANIC** - Your code is safe on GitHub
-2. **Check reflog** - `git reflog`
-3. **Check backups** - `Get-ChildItem D:\Backups\notepadpp-mcp\`
-4. **Re-clone if needed** - GitHub has everything
-5. **Ask for help** - With reflog output
-**Remember**: Git is designed to be hard to break permanently!
----
-*Document created: October 8, 2025*
-*Backup script: `scripts/backup-repo.ps1`*
-*Your code is safe! 🛡️*

package/mcps/windows-computer-use-mcp/docs/_stale/repository-protection/BRANCH_PROTECTION_SETTINGS.md DELETED Viewed

@@ -1,236 +0,0 @@
-# Branch Protection Settings - Quick Reference
-**For Repository**: notepadpp-mcp
-**Setup Time**: ~5 minutes
----
-## 🚀 Quick Setup Instructions
-### 1. Go to Settings
-**URL**: https://github.com/sandraschi/notepadpp-mcp/settings/branches
-Or:
-1. Open repository on GitHub
-2. Click `Settings` tab
-3. Click `Branches` in left sidebar
----
-## 2. Add Rule for `main` Branch
-Click: **Add branch protection rule** or **Add rule**
-### **Branch name pattern**
-```
-main
-```
-### **Protection Settings to Enable**
-Copy these exact settings:
-#### ✅ **Protect matching branches**
-- [x] **Require a pull request before merging**
-  - [x] Require approvals: `0` (you can self-approve)
-  - [x] Dismiss stale pull request approvals when new commits are pushed
-  - [x] Require review from Code Owners (optional)
-- [x] **Require status checks to pass before merging**
-  - [x] Require branches to be up to date before merging
-  - Select status checks when available:
-    - [ ] `ci` (will appear after first CI run)
-    - [ ] `build` (will appear after first build)
-- [x] **Require conversation resolution before merging**
-- [x] **Require signed commits** (optional, skip if you don't use GPG)
-- [x] **Include administrators**
-  - This prevents even YOU from bypassing protections
-  - Ensures safety from accidental force pushes
-#### ❌ **Do NOT enable** (leave unchecked)
-- [ ] ~~Allow force pushes~~ - **LEAVE UNCHECKED**
-- [ ] ~~Allow deletions~~ - **LEAVE UNCHECKED**
-#### ✅ **Additional Settings**
-- [x] **Restrict who can push to matching branches**
-  - Leave empty (allows PR merges only)
-  - Or add specific users/teams if desired
-- [x] **Require deployments to succeed before merging** (optional)
----
-### Click: `Create` or `Save changes`
----
-## 3. Optional: Protect `develop` Branch
-**Branch name pattern**: `develop`
-Use lighter restrictions:
-- [x] **Require a pull request before merging** (optional)
-  - [ ] Require approvals: `0`
-- [ ] Allow force pushes (enabled for cleanup)
-- [x] Restrict deletions
----
-## 4. Leave `feature/*` Branches Unprotected
-**Do NOT create rules for**:
-- `feature/experimental`
-- `feature/*`
-- Other feature branches
-**Why**: These are playground branches - AI needs full freedom here!
----
-## ✅ Verification
-After setup, test the protection:
-```powershell
-# Should FAIL (protected)
-git checkout main
-echo "test" >> test.txt
-git add test.txt
-git commit -m "test"
-git push origin main
-# Expected: "remote: error: GH006: Protected branch update failed"
-# Should SUCCEED (unprotected)
-git checkout feature/experimental
-echo "test" >> test.txt
-git add test.txt
-git commit -m "test"
-git push origin feature/experimental
-# Expected: Success!
-# Clean up
-git reset --hard HEAD~1
-git checkout main
-```
----
-## 🎯 What Protection Does
-### **Prevents** ❌
-- Direct pushes to `main`
-- Force pushes to `main`
-- Deleting `main` branch
-- Merging without review
-- Bypassing CI checks
-### **Allows** ✅
-- Pull Request merges (after review)
-- Emergency hotfixes (via PR)
-- Tag creation
-- Branch creation
-- Full freedom on `feature/*` branches
----
-## 📋 Visual Settings Checklist
-When you see the settings page, it should look like this:
-```
-Branch name pattern
-┌────────────────────────────────────┐
-│ main                                │
-└────────────────────────────────────┘
-Protect matching branches
-☑ Require a pull request before merging
-  ☑ Require approvals: [0]
-  ☑ Dismiss stale pull request approvals
-☑ Require status checks to pass
-  ☑ Require branches to be up to date
-☑ Require conversation resolution
-☑ Include administrators
-Restrict who can push
-┌────────────────────────────────────┐
-│ [empty - no restrictions]           │
-└────────────────────────────────────┘
-☐ Allow force pushes          [UNCHECKED]
-☐ Allow deletions             [UNCHECKED]
-```
----
-## 🚨 Common Issues
-### "I can't push to main anymore!"
-**This is correct!** ✅ You now need to:
-1. Create a branch
-2. Make changes
-3. Create Pull Request
-4. Merge via PR
-### "AI says it can't push to main"
-**Perfect!** ✅ Tell AI to use:
-1. Work on `feature/experimental`
-2. Create PR when ready
-3. You review and merge
-### "I need to make an urgent fix!"
-**No problem!** ✅
-1. Create hotfix branch: `git checkout -b hotfix/urgent`
-2. Make fix
-3. Push branch: `git push origin hotfix/urgent`
-4. Create PR on GitHub
-5. Merge immediately (you can self-approve)
----
-## 🎊 After Setup
-**You can now safely say to AI**:
-> "Work on feature/experimental and try adding [wild idea]!"
-> "Go crazy on the experimental branch!"
-> "Add 10 experimental features and let's see what works!"
-**And your production code on `main` stays 100% safe!**
----
-## 📞 Need Help?
-If protection blocks something you need:
-1. **Check**: Are you using the PR workflow?
-2. **Temporarily disable**: Settings → Branches → Edit rule → Disable
-3. **Make change**: Do what you need
-4. **Re-enable**: Turn protection back on
-**Or just ask AI**: "The branch protection is blocking me, help!"
----
-*Setup Guide created: October 8, 2025*
-*Estimated setup time: 5 minutes*
-*Difficulty: Easy*