@beeos-ai/cli 1.0.16 → 1.0.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@beeos-ai/cli",
-  "version": "1.0.16",
+  "version": "1.0.18",
   "type": "module",
   "description": "BeeOS CLI — run AI agents from your desktop",
   "bin": {

package/scripts/_existing_install_actions.json

@@ -1,40 +1,65 @@
 {
   "$comment": [
-    "P1-E of the install-link review (shared anchor file).",
+    "Existing-install copy lint anchor (was P1-E of the install-link review).",
     "",
-    "Three call sites render the 'BeeOS is already installed — what now?'",
-    "menu with subtly different copy:",
+    "## Historical context",
     "",
-    "  1. web/packages/cli/scripts/install.sh   (bash, pre-Node)",
-    "  2. web/packages/cli/scripts/install.ps1  (PowerShell, pre-Node)",
-    "  3. web/packages/cli/src/commands/init.ts (TS, post-Node)",
+    "Before CLI 1.0.18 the same 'BeeOS is already installed — what now?'",
+    "menu was rendered from THREE places — install.sh, install.ps1, and",
+    "init.ts — and this manifest enforced shared keyword wording across",
+    "all three. The bash + PowerShell sites can't import TypeScript",
+    "constants, so a vitest grep lint",
+    "(`web/packages/cli/src/__tests__/existing-install-actions.test.ts`)",
+    "kept the three menus from drifting apart.",
     "",
-    "Pre-Node sites can't import TypeScript constants, so we anchor the",
-    "wording with this manifest plus a vitest grep lint",
-    "(`web/packages/cli/src/__tests__/existing-install-actions.test.ts`).",
-    "If you change a label in any of the three files, update the",
-    "matching `keywords` here so the lint stays representative; if you",
-    "add a new action altogether, add a new entry below + render it",
-    "in all three sites."
+    "## CLI 1.0.18 simplification",
+    "",
+    "The bootstrap scripts (install.sh / install.ps1) are now framework-",
+    "agnostic: their only job is `detect Node + npm i -g @beeos-ai/cli +",
+    "exec beeos init`. They no longer render any menu — 'what to do",
+    "when BeeOS is already installed' is `beeos init`'s job, where the",
+    "user sees the upgrade / rebind / reset-all / skip choices.",
+    "",
+    "Consequence: the cross-site copy alignment lint shrinks to a",
+    "**single-file** lint on detect.ts. install.sh and install.ps1 are",
+    "removed from `files`. The `actions` block stays as a sanity check",
+    "that detect.ts's `initDecisionLabel` keeps recognisable terminology",
+    "(Upgrade / Re-bind / Skip).",
+    "",
+    "The `advisory` block (added in 1.0.17 for the soft-rebind / reset-all",
+    "split) is preserved and still pins the must-appear-in copy on",
+    "detect.ts so users can tell the two rebind variants apart from the",
+    "label alone."
   ],
   "actions": {
     "upgrade": {
-      "$comment": "Reinstall the CLI to the latest version, then proceed. install.sh/install.ps1 wording differs slightly from init.ts which says 'Upgrade CLI & agents'; both must hit at least one keyword from `keywords`.",
-      "keywords": ["Reinstall", "Upgrade"]
+      "$comment": "detect.ts 'Upgrade CLI & agents' label.",
+      "keywords": ["Upgrade"]
     },
     "rerun": {
-      "$comment": "Reuse the existing install (no npm i -g). install.sh/install.ps1 say 'Re-run beeos init', init.ts shows the 'Re-bind' wording for the same conceptual action.",
-      "keywords": ["Re-run", "Re-bind", "Reusing"]
+      "$comment": "detect.ts soft-rebind label includes 'Re-bind'; advisory block below pins the full phrasing.",
+      "keywords": ["Re-bind", "Reusing"]
     },
     "skip": {
-      "$comment": "Do nothing. Stable wording across all three sites.",
+      "$comment": "Stable across releases.",
       "keywords": ["Skip"]
     }
   },
-  "$files_root_comment": "Paths below are relative to the `web/` workspace root (the test resolves them against that anchor).",
+  "$files_root_comment": "Path is relative to the `web/` workspace root (the test resolves it against that anchor).",
   "files": [
-    "packages/cli/scripts/install.sh",
-    "packages/cli/scripts/install.ps1",
     "packages/core/src/detect.ts"
-  ]
+  ],
+  "$advisory_comment": "Strings below are advisory — not enforced by the lint, but checked by `existing-install-actions.test.ts` to make sure detect.ts's two rebind variants stay distinguishable from each other.",
+  "advisory": {
+    "rebind_soft": {
+      "$comment": "1.0.17+ : detect.ts must include this exact phrase so users see the soft-rebind keeps the same instance_id.",
+      "must_appear_in": ["packages/core/src/detect.ts"],
+      "keywords": ["keep key, refresh binding", "same instance"]
+    },
+    "rebind_destructive": {
+      "$comment": "1.0.17+ : detect.ts must include this phrase so the destructive rebind is unmistakable.",
+      "must_appear_in": ["packages/core/src/detect.ts"],
+      "keywords": ["NEW key", "NEW instance"]
+    }
+  }
 }

package/scripts/install.Tests.ps1

@@ -23,18 +23,24 @@
 
 # ── Parse-time checks ────────────────────────────────────────
 
-$scriptPath = Join-Path $PSScriptRoot "install.ps1"
+# Pester 5 runs file-level code in the discovery phase but does NOT
+# propagate vars defined there into It blocks at run phase. Compute
+# the path inside each test (or via BeforeAll) so $scriptPath is
+# always non-null when the assertions execute.
+BeforeAll {
+    $script:ScriptPath = Join-Path $PSScriptRoot "install.ps1"
+}
 
 Describe "install.ps1 parse-time integrity" {
     It "exists at the expected path" {
-        Test-Path $scriptPath | Should -Be $true
+        Test-Path $script:ScriptPath | Should -Be $true
     }
 
     It "parses without syntax errors (AST round-trip)" {
         $tokens = $null
         $errors = $null
         [System.Management.Automation.Language.Parser]::ParseFile(
-            $scriptPath,
+            $script:ScriptPath,
             [ref]$tokens,
             [ref]$errors
         ) | Out-Null
@@ -45,7 +51,7 @@ Describe "install.ps1 parse-time integrity" {
         $tokens = $null
         $errors = $null
         $ast = [System.Management.Automation.Language.Parser]::ParseFile(
-            $scriptPath,
+            $script:ScriptPath,
             [ref]$tokens,
             [ref]$errors
         )
@@ -55,6 +61,12 @@ Describe "install.ps1 parse-time integrity" {
             $node -is [System.Management.Automation.Language.FunctionDefinitionAst]
         }, $true) | ForEach-Object { $_.Name }
 
+        # CLI >= 1.0.16: Install-DeviceAgentSuite has been removed —
+        # the device suite installs lazily on the first
+        # `beeos device attach` (see core/device-setup.ts).
+        # CLI >= 1.0.18: Read-ExistingInstallAction + Get-BeeosVersion
+        # are gone — `beeos init` is the single owner of the
+        # already-installed menu, the bootstrap script just hands off.
         $expected = @(
             "Write-BeeInfo",
             "Write-BeeOk",
@@ -65,8 +77,6 @@ Describe "install.ps1 parse-time integrity" {
             "Install-NodeAuto",
             "Show-InstallHints",
             "Send-Telemetry",
-            "Read-ExistingInstallAction",
-            "Install-DeviceAgentSuite",
             "Invoke-BeeosCli",
             # P2-8: PSCore + RunAs auto-elevation helpers.
             "Test-IsAdministrator",
@@ -83,7 +93,7 @@ Describe "install.ps1 parse-time integrity" {
 
 Describe "install.ps1 platform guard (P2-8)" {
     It "contains the non-Windows early-exit branch" {
-        $content = Get-Content -Raw -Path $scriptPath
+        $content = Get-Content -Raw -Path $script:ScriptPath
         # Look for the marker comment AND the exit branch so a
         # superficial rename of the variable still trips the test.
         $content | Should -Match "This installer is Windows-only"
@@ -91,12 +101,12 @@ Describe "install.ps1 platform guard (P2-8)" {
     }
 
     It "contains a UAC auto-elevation branch" {
-        $content = Get-Content -Raw -Path $scriptPath
+        $content = Get-Content -Raw -Path $script:ScriptPath
         $content | Should -Match "Start-Process .* -Verb RunAs"
     }
 
     It "honours BEEOS_NO_AUTO_ELEVATE=1 as an opt-out" {
-        $content = Get-Content -Raw -Path $scriptPath
+        $content = Get-Content -Raw -Path $script:ScriptPath
         $content | Should -Match "BEEOS_NO_AUTO_ELEVATE"
     }
 }
@@ -106,13 +116,16 @@ Describe "install.ps1 stdin / TTY handover (P1-J)" {
     # prompts read from the exhausted pipe and silently take defaults.
     # Mirrors install.sh's `</dev/tty` reattachment.
     It "detects [Console]::IsInputRedirected" {
-        $content = Get-Content -Raw -Path $scriptPath
+        $content = Get-Content -Raw -Path $script:ScriptPath
         $content | Should -Match "\[Console\]::IsInputRedirected"
     }
 
     It "uses Start-Process with -NoNewWindow when stdin is redirected" {
-        $content = Get-Content -Raw -Path $scriptPath
-        $content | Should -Match "Start-Process .* -NoNewWindow"
+        $content = Get-Content -Raw -Path $script:ScriptPath
+        # The Start-Process invocation in install.ps1 uses backtick line
+        # continuation, so `-NoNewWindow` lives on a separate line from
+        # `Start-Process`. `(?s)` enables dotall so `.` matches newlines.
+        $content | Should -Match "(?s)Start-Process .*?-NoNewWindow"
     }
 }
 
@@ -121,25 +134,29 @@ Describe "install.ps1 stderr log file (P1-I)" {
     # MUST land in a forensic file instead of `2>$null`. The lint
     # below is structural — assert the variable + the redirect appear.
     It "declares a `$BeeosInstallLog` variable" {
-        $content = Get-Content -Raw -Path $scriptPath
+        $content = Get-Content -Raw -Path $script:ScriptPath
         $content | Should -Match "BeeosInstallLog"
     }
 
     It "redirects winget stderr to the install log" {
-        $content = Get-Content -Raw -Path $scriptPath
+        $content = Get-Content -Raw -Path $script:ScriptPath
         # `2>>$BeeosInstallLog` is the canonical append-redirect syntax;
         # `2>$null` here would be a regression to the silent
         # behaviour the review called out.
-        $content | Should -Match "winget install [^`r`n]+2>>\$BeeosInstallLog"
+        # Use a single-quoted string so `$BeeosInstallLog` is NOT
+        # subject to PowerShell variable interpolation; the .NET regex
+        # engine still treats `\r` / `\n` as CR / LF and `\$` as a
+        # literal `$`.
+        $content | Should -Match 'winget install [^\r\n]+2>>\$BeeosInstallLog'
     }
 
     It "redirects choco stderr to the install log" {
-        $content = Get-Content -Raw -Path $scriptPath
-        $content | Should -Match "choco install [^`r`n]+2>>\$BeeosInstallLog"
+        $content = Get-Content -Raw -Path $script:ScriptPath
+        $content | Should -Match 'choco install [^\r\n]+2>>\$BeeosInstallLog'
     }
 
     It "Show-InstallHints surfaces the log path on failure" {
-        $content = Get-Content -Raw -Path $scriptPath
+        $content = Get-Content -Raw -Path $script:ScriptPath
         $content | Should -Match "Installer log:"
     }
 }
@@ -164,6 +181,6 @@ Describe "install.ps1 dry-run hook" {
         # Dot-source so we exercise the param-block + helper definitions
         # without invoking the main install body. The dry-run hook
         # `return`s before any state-changing call.
-        { . $scriptPath } | Should -Not -Throw
+        { . $script:ScriptPath } | Should -Not -Throw
     }
 }

package/scripts/install.ps1

@@ -4,35 +4,28 @@
     BeeOS CLI Installer for Windows.
 
 .DESCRIPTION
-    Detects or installs Node.js (via winget / Chocolatey fallback), then
-    dispatches into `beeos init` (default) or `beeos device attach` when
-    `-Device` is passed. Heavier deps (Python, uv, adb, scrcpy/vnc bridges)
-    are installed lazily by the CLI itself.
-
-    Staging / dev-loop env vars (CLI >= 1.0.10). All four are inherited by
-    the spawned `beeos init` / `beeos device attach` child via the normal
-    process env passthrough — no extra Set-Item / -PassThru is needed. CLI
-    >= 1.0.10 reads them via the loadOrCreateConfig env-overrides layer;
-    older CLIs only honor BEEOS_API_URL (telemetry) +
-    BEEOS_AGENT_GATEWAY_URL (runtime).
-
-      $env:BEEOS_API_URL              Public API base; both this script
-                                       (telemetry) and the CLI runtime use
-                                       this.
-      $env:BEEOS_AGENT_GATEWAY_URL    Agent Gateway base (Ed25519-signed
-                                       bootstrap requests).
-      $env:BEEOS_DASHBOARD_URL        Dashboard base (OAuth + bind redirect).
-      $env:BEEOS_DEVICE_AGENT_VERSION Pin @beeos-ai/device-agent semver.
-      $env:BEEOS_MCP_SERVER_VERSION   Pin @beeos-ai/device-mcp-server semver.
-      $env:BEEOS_USE_NPX = "1"        Power-user escape hatch: use `npx`
-                                       for a throwaway install. `beeos`
-                                       will NOT persist on PATH after
-                                       the script exits. Default
-                                       behaviour (since CLI 1.0.11) is
-                                       always `npm install -g` so the
-                                       CLI plus the device-agent suite
-                                       are both globally available for
-                                       follow-up commands.
+    Responsibilities (deliberately minimal — framework-agnostic):
+      1. Detect or install Node.js (via winget / Chocolatey fallback).
+      2. `npm install -g @beeos-ai/cli`.
+      3. `exec beeos init` (or `beeos device attach` with `-Device`).
+
+    Anything else — "you already have BeeOS installed, what now?",
+    framework selection, rebind variants — lives inside the CLI's own
+    `beeos init` menu, not here. The bootstrap script stays small so
+    it's easy to maintain and easy to diagnose on a customer machine.
+
+    Optional env vars:
+
+      $env:BEEOS_API_URL            Public API base (this script uses
+                                     it for telemetry; the CLI uses it
+                                     for runtime). Defaults to production.
+      $env:BEEOS_AGENT_GATEWAY_URL  Agent Gateway base (forwarded as-is
+                                     to the spawned CLI).
+      $env:BEEOS_DASHBOARD_URL      Dashboard base (OAuth / bind redirect).
+      $env:BEEOS_INSTALL_DRY_RUN=1  CI smoke-test escape hatch.
+      $env:BEEOS_NO_TELEMETRY=1     Disable script-level telemetry POSTs.
+      $env:BEEOS_USE_NPX = "1"      Power-user throwaway install (beeos
+                                     won't persist on PATH).
 
 .EXAMPLE
     # One-liner (PowerShell 5+):
@@ -40,19 +33,17 @@
 
 .EXAMPLE
     # With specific CLI version:
-    .\install.ps1 -Version 1.0.4
+    .\install.ps1 -Version 1.0.18
 
 .EXAMPLE
     # Jump straight into device attach instead of init:
     .\install.ps1 -Device
 
 .EXAMPLE
-    # Bare-metal one-shot staging install (CLI >= 1.0.11):
+    # Bare-metal staging one-liner:
     $env:BEEOS_API_URL              = "https://public-api-staging.beeos.ai"
     $env:BEEOS_AGENT_GATEWAY_URL    = "https://agent-gw-staging.beeos.ai"
     $env:BEEOS_DASHBOARD_URL        = "https://beeos-staging-web.vercel.app"
-    $env:BEEOS_DEVICE_AGENT_VERSION = "0.4.2"
-    $env:BEEOS_MCP_SERVER_VERSION   = "0.2.3"
     irm https://beeos.ai/install.ps1 | iex
 #>
 param(
@@ -102,18 +93,11 @@ if (-not $script:IsWindowsHost) {
 
 $CliPackage = if ($Version -eq "latest") { "@beeos-ai/cli@latest" } else { "@beeos-ai/cli@$Version" }
 
-# Sibling packages installed alongside the CLI so that `beeos device attach`
-# works on a clean machine without further `npm i -g` steps (a.k.a. the
-# "fleet ready" install strategy — see agents/device-agent/ARCHITECTURE.md
-# for the 0.2.0+ sibling-pair topology between device-agent and
-# device-mcp-server). Versions are independent of `-Version` (which only
-# pins the CLI) — both packages follow their own semver. Override via
-# $env:BEEOS_DEVICE_AGENT_VERSION / $env:BEEOS_MCP_SERVER_VERSION when you
-# need to pin a specific build (e.g. for a staging smoke test).
-$DeviceAgentVersion = if ($env:BEEOS_DEVICE_AGENT_VERSION) { $env:BEEOS_DEVICE_AGENT_VERSION } else { "latest" }
-$McpServerVersion   = if ($env:BEEOS_MCP_SERVER_VERSION)   { $env:BEEOS_MCP_SERVER_VERSION   } else { "latest" }
-$DeviceAgentPackage = "@beeos-ai/device-agent@$DeviceAgentVersion"
-$McpServerPackage   = "@beeos-ai/device-mcp-server@$McpServerVersion"
+# `@beeos-ai/device-agent` + `@beeos-ai/device-mcp-server` are NOT
+# installed here. CLI >= 1.0.16 installs them lazily on the first
+# `beeos device attach` via `ensureDeviceAgent` in
+# `web/packages/core/src/device-setup.ts`. OpenClaw-only users never
+# download the device suite at all.
 
 # Telemetry endpoint (override with $env:BEEOS_API_URL for staging).
 if (-not $env:BEEOS_API_URL -or $env:BEEOS_API_URL.Length -eq 0) {
@@ -426,92 +410,6 @@ function Show-InstallHints {
     }
 }
 
-# ── Existing install detection ───────────────────────────────
-
-function Get-BeeosVersion {
-    try {
-        $out = & beeos --version 2>$null
-        if ($out) {
-            if ($out -match "\d+\.\d+\.\d+") { return $Matches[0] }
-            return ($out -replace '\s+','')
-        }
-    } catch {}
-    return $null
-}
-
-function Read-ExistingInstallAction {
-    # Note on naming: "Reinstall + upgrade CLI" deliberately differs
-    # from the `beeos init` menu's "Upgrade CLI & agents" item. The
-    # script-side action also re-bootstraps Node / pnpm and re-applies
-    # this shell's env vars before exec'ing the new binary, which the
-    # in-CLI upgrade does NOT do — choosing a different verb keeps the
-    # two flows distinguishable. See `install.sh` for the matching
-    # docstring.
-    #
-    # P1-E of the install-link review: the labels rendered below are
-    # anchored against `install.sh::prompt_existing_install_action` +
-    # `init.ts::decideAction` via
-    # `web/packages/cli/scripts/_existing_install_actions.json` and
-    # the vitest grep lint at
-    # `web/packages/cli/src/__tests__/existing-install-actions.test.ts`.
-    # Keep at least one keyword from `keywords[action]` per option.
-    $ver = Get-BeeosVersion
-    if (-not $ver) { $ver = "unknown" }
-    Write-BeeWarn "BeeOS CLI is already installed (v$ver)."
-    Write-Host ""
-    Write-Host "  [1] Reinstall + upgrade CLI to the latest version, then run beeos init"
-    Write-Host "  [2] Re-run beeos init without reinstalling"
-    Write-Host "  [3] Skip (do nothing)"
-    Write-Host ""
-
-    if (-not [Environment]::UserInteractive) {
-        Write-BeeInfo "Non-interactive shell — defaulting to reinstall."
-        return "upgrade"
-    }
-
-    $choice = Read-Host "Choose [1-3]"
-    switch ($choice) {
-        "" { return "upgrade" }
-        "1" { return "upgrade" }
-        "2" { return "rerun" }
-        "3" { return "skip" }
-        default { return "upgrade" }
-    }
-}
-
-# ── Device-agent sibling suite installer ─────────────────────
-#
-# Installs `@beeos-ai/device-agent` + `@beeos-ai/device-mcp-server` globally
-# so the very first `beeos device attach` on a clean machine does not need
-# to fetch them separately. `@beeos-ai/device-common` is pulled
-# transitively as a `dependencies` entry of both — no separate install
-# needed.
-#
-# Failure here is NEVER fatal: the CLI itself was already installed
-# successfully, and `beeos device attach` will prompt to install missing
-# pieces via ensureDeviceAgent on first use. We just emit a WARN with the
-# manual recovery command.
-function Install-DeviceAgentSuite {
-    $npmPath = Get-Command npm -ErrorAction SilentlyContinue
-    if (-not $npmPath) {
-        Write-BeeWarn "npm not available — skipping device-agent suite install."
-        Write-BeeWarn "Manual fix: install Node + run ``npm i -g $DeviceAgentPackage $McpServerPackage``."
-        return
-    }
-
-    Write-BeeInfo "Installing device-agent suite ($DeviceAgentPackage, $McpServerPackage)..."
-    & npm install -g $DeviceAgentPackage $McpServerPackage
-    if ($LASTEXITCODE -eq 0) {
-        Write-BeeOk "device-agent suite installed."
-    } else {
-        Write-BeeWarn "Failed to install device-agent suite — ``beeos device attach`` will prompt for it on first use."
-        Write-BeeWarn "Manual fix: npm i -g $DeviceAgentPackage $McpServerPackage"
-        # Reset $LASTEXITCODE so subsequent `if ($LASTEXITCODE -ne 0)` checks
-        # in callers don't trip on this non-fatal failure.
-        $global:LASTEXITCODE = 0
-    }
-}
-
 # ── Run CLI ──────────────────────────────────────────────────
 
 function Invoke-BeeosCli {
@@ -547,9 +445,7 @@ function Invoke-BeeosCli {
     if ($LASTEXITCODE -ne 0) {
         # P0-A of the install-link review: fail-after-bootstrap signal.
         # The `install.bootstrap.cli_installed` event is only emitted
-        # AFTER npm + the device-agent suite report success, so npm
-        # failures are recorded as a distinct outcome (not as silent
-        # post-success).
+        # AFTER npm reports success.
         Send-Telemetry -Event "install.bootstrap.npm_fail" -ErrorCode "npm_install_cli_failed" -Success $false
         Write-BeeError "npm install -g $CliPackage failed."
         Write-BeeError ""
@@ -559,7 +455,10 @@ function Invoke-BeeosCli {
         Write-BeeError "  - EACCES / permission error: run PowerShell as Administrator"
         exit 1
     }
-    Install-DeviceAgentSuite
+    # Device-agent suite is intentionally NOT installed here; `beeos
+    # device attach` will auto-install it on first use via
+    # `ensureDeviceAgent` (see `web/packages/core/src/device-setup.ts`).
+    # OpenClaw-only users never download those ~20MB.
     Send-Telemetry -Event "install.bootstrap.cli_installed"
 
     # P1-J of the install-link review: when the user invokes the
@@ -641,34 +540,11 @@ if (-not (Test-NodeVersion)) {
 $nodeVer = & node -v
 Write-BeeOk "Node.js $nodeVer detected"
 
-$beeosCmd = Get-Command beeos -ErrorAction SilentlyContinue
-if ($beeosCmd) {
-    $action = Read-ExistingInstallAction
-    switch ($action) {
-        "skip" {
-            Write-BeeInfo "Skipping. Run `beeos init` or `beeos device attach` manually later."
-            exit 0
-        }
-        "upgrade" {
-            Write-BeeInfo "Reinstalling $CliPackage..."
-            & npm install -g $CliPackage
-            if ($LASTEXITCODE -ne 0) {
-                Send-Telemetry -Event "install.bootstrap.npm_fail" -ErrorCode "npm_install_cli_failed_upgrade" -Success $false
-                Write-BeeError "npm install -g $CliPackage failed."
-                Write-BeeError ""
-                Write-BeeError "Common fixes:"
-                Write-BeeError "  - EEXIST on beeos from another package:"
-                Write-BeeError "      npm uninstall -g beeos    # then re-run installer"
-                Write-BeeError "  - EACCES / permission error: run PowerShell as Administrator"
-                exit 1
-            }
-            Install-DeviceAgentSuite
-        }
-        "rerun" {
-            Write-BeeInfo "Reusing existing install."
-        }
-    }
-}
+# Bootstrap is finished. Hand off to `Invoke-BeeosCli` which performs
+# `npm install -g @beeos-ai/cli` (idempotent — npm short-circuits when
+# the requested version is already on disk) and then runs the freshly
+# installed binary. "What does the CLI do when it's already installed?"
+# is now `beeos init`'s problem; we don't second-guess it from out here.
 
 Write-BeeInfo "Running BeeOS CLI..."
 Write-Host ""