Scoop User-Space Installation Policy

This rule applies to files matching the patterns above.

# Scoop User-Space Installation Policy

## Rule
Scoop MUST be installed and operated in user space. Never use administrator privileges. Never install to system directories.

## Installation
```powershell
# Good: user-space installation
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Invoke-RestMethod -Uri https://get.scoop.sh | Invoke-Expression

# Bad: admin/system installation
# Do NOT run PowerShell as Administrator for Scoop
```

## Directory Structure
```
~/scoop/                    # Default root (USERPROFILE/scoop)
├── apps/                   # Installed applications
│   ├── scoop/             # Scoop itself
│   ├── git/               # Example app
│   └── nodejs/
├── buckets/               # Bucket repositories
├── cache/                 # Downloaded files
├── persist/               # Persistent app data
└── shims/                 # PATH shim executables
```

## Good
```powershell
# Normal user context
scoop install git nodejs neovim
scoop update *
```

## Bad
```powershell
# Running as Administrator — NEVER
# Changes system PATH, creates admin-owned files
scoop install --global git  # Avoid global installs
```

## Why User-Space
- No admin password prompts
- Works on locked-down corporate machines
- Clean uninstall (delete ~/scoop)
- No system PATH pollution
- Multiple users can have different installations