update docs from upload -> deploy, add deprecation notice

Author: dskvr

README.md

@@ -37,8 +37,8 @@ curl -fsSL https://nsyte.run/get/install.sh | bash
 # Initialize project (interactive setup)
 nsyte init
 
-# Upload website
-nsyte upload ./dist
+# Deploy website
+nsyte deploy ./dist
 ```
 
 ## Table of Contents
@@ -80,8 +80,9 @@ deno task compile:all
 | ----------------------- | ------------------------------------------------ |
 | `nsyte`                 | Interactive setup wizard                         |
 | `nsyte init`            | Initialize configuration                         |
-| `nsyte upload <dir>`    | Upload files                                     |
+| `nsyte deploy <dir>`    | Deploy files                                     |
 | `nsyte ls`              | List published files                             |
+| `nsyte browse`          | Interactive TUI browser for files                |
 | `nsyte download <dir>`  | Download files                                   |
 | `nsyte run`             | Run resolver server with npub subdomains         |
 | `nsyte serve -d <div>`  | Serve local nsite files from directory (current dir is default)           |
@@ -91,26 +92,26 @@ deno task compile:all
 | `nsyte ci`              | Generate CI/CD credentials (nbunksec)            |
 | `nsyte bunker <action>` | Manage NIP-46 bunkers                            |
 
-### Uploading Files
+### Deploying Files
 
 ```bash
-# Basic upload
-nsyte upload ./dist
+# Basic deploy
+nsyte deploy ./dist
 
 # With options
-nsyte upload ./dist --force --concurrency 8 --verbose
+nsyte deploy ./dist --force --concurrency 8 --verbose
 
 # With metadata publishing
-nsyte upload ./dist --publish-profile --publish-relay-list --publish-server-list
+nsyte deploy ./dist --publish-profile --publish-relay-list --publish-server-list
 
 # With NIP-89 app handler
-nsyte upload ./dist --app-handler --handler-kinds "1,30023"
+nsyte deploy ./dist --app-handler --handler-kinds "1,30023"
 
 # With NIP-94 release artifacts (auto-create archive)
-nsyte upload ./dist --publish-file-metadata --version v1.0.0
+nsyte deploy ./dist --publish-file-metadata --version v1.0.0
 
 # With NIP-94 release artifacts (use existing archives)
-nsyte upload ./dist --publish-file-metadata --version v1.0.0 --release-artifacts dist.tar.gz,dist.zip
+nsyte deploy ./dist --publish-file-metadata --version v1.0.0 --release-artifacts dist.tar.gz,dist.zip
 ```
 
 ### Purging Files
@@ -331,7 +332,7 @@ nsyte ci
 
 # Add the nbunksec to your CI/CD secrets (e.g., NBUNK_SECRET)
 # Then use in your pipeline:
-nsyte upload ./dist --nbunksec ${NBUNK_SECRET}
+nsyte deploy ./dist --nbunksec ${NBUNK_SECRET}
 ```
 
 **Security Best Practices:**
@@ -350,7 +351,7 @@ jobs:
     steps:
       - uses: actions/checkout@v3
       - uses: denoland/setup-deno@v1
-      - run: nsyte upload ./dist --nbunksec ${{ secrets.NBUNK_SECRET }}
+      - run: nsyte deploy ./dist --nbunksec ${{ secrets.NBUNK_SECRET }}
 ```
 
 ## Configuration
@@ -442,7 +443,7 @@ nsyte supports [NIP-89](https://github.com/nostr-protocol/nips/blob/master/89.md
 **Command Line:**
 ```bash
 # Publish app handler for specific event kinds
-nsyte upload ./dist --app-handler --handler-kinds "1,30023,30311"
+nsyte deploy ./dist --app-handler --handler-kinds "1,30023,30311"
 ```
 
 When enabled, other Nostr clients can suggest your nsite when users encounter the specified event types.
@@ -496,7 +497,7 @@ nsyte bunker migrate
 For client-side routing (React, Vue, etc.):
 
 ```bash
-nsyte upload ./dist --fallback=/index.html
+nsyte deploy ./dist --fallback=/index.html
 ```
 
 ## Troubleshooting

VERSION

@@ -1 +1 @@
-0.18.0
+0.18.1

deno.json

@@ -1,6 +1,6 @@
 {
   "name": "@nsyte/cli",
-  "version": "0.18.0",
+  "version": "0.18.1",
   "description": "nsyte - publish your site to nostr and blossom servers",
   "license": "MIT",
   "exports": "./src/cli.ts",

docs/JSR_SETUP.md

@@ -40,7 +40,7 @@ Ensure your `deno.json` includes:
 ```json
 {
   "name": "@nsyte/cli",
-  "version": "0.18.0",
+  "version": "0.18.1",
   "exports": "./src/cli.ts"
 }
 ```

docs/guides/ci-cd.md

@@ -70,7 +70,7 @@ jobs:
           RELAYS: "wss://some.relay.xyz,wss://another.relay.abc"
           SERVERS: "https://a.blossom.server.com,https://another.blossom.server"
         run: |
-          nsyte upload ./dist -i \
+          nsyte deploy ./dist -i \
             --nbunksec ${{ secrets.NBUNKSEC }} \
             --relays ${{ env.RELAYS }} \
             --servers ${{ env.SERVERS }} \

docs/guides/deployment.md

@@ -10,10 +10,10 @@ nsyte.
 
 ## Basic Deployment
 
-The simplest way to deploy your site is using the `upload` command:
+The simplest way to deploy your site is using the `deploy` command:
 
 ```bash
-nsyte upload ./dist
+nsyte deploy ./dist
 ```
 
 This will:
@@ -35,7 +35,7 @@ Suitable for:
 Steps:
 
 1. Build your site
-2. Run `nsyte upload`
+2. Run `nsyte deploy`
 3. Verify the deployment
 
 ### 2. Automated Deployment
@@ -70,34 +70,34 @@ Steps:
 
 ## Deployment Options
 
-### Basic Upload
+### Basic Deploy
 
 ```bash
-nsyte upload ./dist
+nsyte deploy ./dist
 ```
 
-### Force Re-upload
+### Force Re-deploy
 
 ```bash
-nsyte upload ./dist --force
+nsyte deploy ./dist --force
 ```
 
 ### Purge Deleted Files
 
 ```bash
-nsyte upload ./dist --purge
+nsyte deploy ./dist --purge
 ```
 
 ### Set Concurrency
 
 ```bash
-nsyte upload ./dist --concurrency 8
+nsyte deploy ./dist --concurrency 8
 ```
 
 ### SPA Support
 
 ```bash
-nsyte upload ./dist --fallback=/index.html
+nsyte deploy ./dist --fallback=/index.html
 ```
 
 ## Deployment Checklist
@@ -122,7 +122,7 @@ Before deploying:
 
 4. **Deployment**
    - [ ] Backup current site
-   - [ ] Run upload
+   - [ ] Run deploy
    - [ ] Verify deployment
    - [ ] Check site metadata
 
@@ -160,7 +160,7 @@ Before deploying:
 
 ### Common Issues
 
-1. **Upload Failures**
+1. **Deploy Failures**
    - Check network connectivity
    - Verify relay liveness
    - Ensure you are allowed to publish to provided relays

docs/guides/local-setup.md

@@ -61,10 +61,10 @@ echo "<html><body><h1>Test Site</h1></body></html>" > index.html
 echo "# Test" > README.md
 ```
 
-### Test Upload
+### Test Deploy
 
 ```bash
-nsyte upload .
+nsyte deploy .
 ```
 
 ### Verify Deployment
@@ -106,8 +106,8 @@ npx serve dist/
 ### Deploy to Test Environment
 
 ```bash
-# Upload to staging relays first
-nsyte upload ./dist --relays "wss://test-relay.example.com"
+# Deploy to staging relays first
+nsyte deploy ./dist --relays "wss://test-relay.example.com"
 ```
 
 ## Development Commands
@@ -130,7 +130,7 @@ deno task test
 Use verbose output for debugging:
 
 ```bash
-nsyte upload . --verbose
+nsyte deploy . --verbose
 ```
 
 ## Configuration Tips

docs/guides/nip94-cicd.md

@@ -27,7 +27,7 @@ jobs:
       
       - name: Publish Linux build
         run: |
-          nsyte upload dist \
+          nsyte deploy dist \
             --publish-file-metadata \
             --version ${{ github.ref_name }} \
             --release-artifacts dist-linux.tar.gz \
@@ -47,7 +47,7 @@ jobs:
       
       - name: Publish Windows build
         run: |
-          nsyte upload dist `
+          nsyte deploy dist `
             --publish-file-metadata `
             --version ${{ github.ref_name }} `
             --release-artifacts dist-windows.zip `
@@ -93,7 +93,7 @@ jobs:
       
       - name: Publish artifact
         run: |
-          nsyte upload dist \
+          nsyte deploy dist \
             --publish-file-metadata \
             --version ${{ github.event.release.tag_name }} \
             --release-artifacts ${{ matrix.artifact }} \
@@ -114,7 +114,7 @@ variables:
 .release_template: &release_definition
   stage: release
   script:
-    - nsyte upload dist
+    - nsyte deploy dist
         --publish-file-metadata
         --version $VERSION
         --release-artifacts $ARTIFACT_PATH
@@ -178,7 +178,7 @@ pipeline {
                         sh 'npm ci && npm run build'
                         sh 'tar -czf dist-linux.tar.gz dist/'
                         sh """
-                            nsyte upload dist \
+                            nsyte deploy dist \
                                 --publish-file-metadata \
                                 --version ${params.VERSION} \
                                 --release-artifacts dist-linux.tar.gz \
@@ -193,7 +193,7 @@ pipeline {
                         sh 'npm ci && npm run build'
                         sh 'tar -czf dist-macos.tar.gz dist/'
                         sh """
-                            nsyte upload dist \
+                            nsyte deploy dist \
                                 --publish-file-metadata \
                                 --version ${params.VERSION} \
                                 --release-artifacts dist-macos.tar.gz \
@@ -208,7 +208,7 @@ pipeline {
                         bat 'npm ci && npm run build'
                         powershell 'Compress-Archive -Path dist/* -DestinationPath dist-windows.zip'
                         bat """
-                            nsyte upload dist ^
+                            nsyte deploy dist ^
                                 --publish-file-metadata ^
                                 --version ${params.VERSION} ^
                                 --release-artifacts dist-windows.zip ^
@@ -231,7 +231,7 @@ Use git tags for consistent versioning:
 ```bash
 # In your CI script
 VERSION=$(git describe --tags --abbrev=0)
-nsyte upload --version "$VERSION" ...
+nsyte deploy --version "$VERSION" ...
 ```
 
 ### 2. Secure Key Management
@@ -266,12 +266,12 @@ Take advantage of nsyte's append capability:
 # Job 1: Build and release Linux
 - name: Release Linux
   run: |
-    nsyte upload --version v1.0.0 --release-artifacts linux.tar.gz
+    nsyte deploy --version v1.0.0 --release-artifacts linux.tar.gz
 
 # Job 2: Build and release Windows (runs later)
 - name: Release Windows
   run: |
-    nsyte upload --version v1.0.0 --release-artifacts windows.zip
+    nsyte deploy --version v1.0.0 --release-artifacts windows.zip
     # Automatically appends to existing v1.0.0 release
 ```
 
@@ -291,7 +291,7 @@ upload_with_retry() {
     while [ $attempt -le $max_attempts ]; do
         echo "Upload attempt $attempt of $max_attempts"
 
-        if nsyte upload dist \
+        if nsyte deploy dist \
             --publish-file-metadata \
             --version "$VERSION" \
             --release-artifacts "$1" \
@@ -339,7 +339,7 @@ RELEASE_NOTES=$(git log --pretty=format:"- %s" $(git describe --tags --abbrev=0
 echo "$RELEASE_NOTES" > release-notes.txt
 
 # Include in your release
-nsyte upload dist \
+nsyte deploy dist \
     --publish-file-metadata \
     --version "$VERSION" \
     --release-artifacts dist.tar.gz,release-notes.txt
@@ -366,7 +366,7 @@ When updating a release with a fixed artifact:
 Enable verbose output for troubleshooting:
 
 ```bash
-nsyte upload dist \
+nsyte deploy dist \
     --publish-file-metadata \
     --version v1.0.0 \
     --release-artifacts dist.tar.gz \

docs/guides/security-troubleshooting.md

@@ -183,7 +183,7 @@ nsyte ci  # Follow interactive prompts
 echo $NBUNK_SECRET | head -c 50  # Should start with "nbunksec1"
 
 # Test locally first
-nsyte upload ./dist --nbunksec $NBUNK_SECRET
+nsyte deploy ./dist --nbunksec $NBUNK_SECRET
 
 # Check secret configuration in CI/CD platform
 # GitHub Actions: Repository Settings > Secrets

docs/guides/security.md

@@ -73,7 +73,7 @@ nsyte ci
 # This creates a dedicated nbunksec for CI/CD use
 
 # Use in CI/CD with secrets
-nsyte upload ./dist --nbunksec ${{ secrets.NBUNK_SECRET }}
+nsyte deploy ./dist --nbunksec ${{ secrets.NBUNK_SECRET }}
 ```
 
 ### Key Rotation
@@ -98,7 +98,7 @@ Choose relays carefully:
 
 ```bash
 # Use multiple trusted relays
-nsyte upload ./dist \
+nsyte deploy ./dist \
   --relays "wss://relay.damus.io,wss://relay.nostr.band,wss://nos.lol"
 ```
 
@@ -128,7 +128,7 @@ jobs:
       - name: Deploy
         env:
           NSYTE_BUNKER_KEY: ${{ secrets.NSYTE_BUNKER_KEY }}
-        run: nsyte upload ./dist
+        run: nsyte deploy ./dist
 ```
 
 ### Content Security