pi-revit 0.2.11 → 0.2.13

package/scripts/deploy.ps1

@@ -86,6 +86,18 @@ foreach ($t in $targets) {
 
     $addinsDir = Join-Path $env:APPDATA "Autodesk\Revit\Addins\$($t.Version)"
     $targetDir = Join-Path $addinsDir 'RevitBridge'
+
+    # Replace the add-in folder instead of copying over it. It holds nothing but our own
+    # build output, and an additive copy leaves files from the previous release behind --
+    # a renamed or downgraded dependency stays next to the new one for Revit to load.
+    if (Test-Path $targetDir) {
+        try {
+            Remove-Item -LiteralPath $targetDir -Recurse -Force -ErrorAction Stop
+        }
+        catch {
+            throw "Could not clear '$targetDir': $($_.Exception.Message). Close Revit $($t.Version) and run deploy.ps1 again."
+        }
+    }
     New-Item -ItemType Directory -Force -Path $targetDir | Out-Null
 
     # execute_csharp ships Roslyn: copy the ENTIRE build output (RevitBridge.dll,

package/scripts/setup-workspace.ps1

@@ -1,80 +1,80 @@
-#Requires -Version 5.1
-<#
-Sets up the pi-revit user environment on this PC:
-
-  1. Workspace at Documents\pi-revit (AGENTS.md conventions, Models\ output tree,
-     double-click launcher). An existing AGENTS.md is never overwritten.
-  2. Global `pi-revit` command installed next to the `pi` command, so any terminal can run:
-       pi-revit              -> Pi in the workspace
-       pi-revit -c           -> continue the last session
-     Model output sorts itself: the Revit tools file each export under
-     Models\<model title>\ automatically, keyed by the document it came from.
-
-Idempotent — safe to re-run. Usage:
-  scripts\setup-workspace.ps1
-  scripts\setup-workspace.ps1 -WorkspaceDir "D:\work\pi-revit"
-#>
-param(
-    [string]$WorkspaceDir = (Join-Path ([Environment]::GetFolderPath('MyDocuments')) 'pi-revit')
-)
-
-$ErrorActionPreference = 'Stop'
-$templates = Join-Path (Split-Path $PSScriptRoot -Parent) 'workspace'
-
-# 1. Workspace folders. Models\ is where the Revit tools file per-model output.
-New-Item -ItemType Directory -Force -Path (Join-Path $WorkspaceDir 'Models') | Out-Null
-
-# Conventions / notes: copy only when missing so user edits survive re-runs.
-$workspaceAgents = Join-Path $WorkspaceDir 'AGENTS.md'
-if (-not (Test-Path $workspaceAgents)) {
-    Copy-Item (Join-Path $templates 'AGENTS.md') $workspaceAgents
-}
-
-# Launcher is code, not user data: always refresh.
-Copy-Item (Join-Path $templates 'pi-revit-here.cmd') (Join-Path $WorkspaceDir 'pi-revit.cmd') -Force
-
-Write-Host "Workspace ready: $WorkspaceDir" -ForegroundColor Green
-
-# 2. Global pi-revit command next to pi (that directory is on PATH by definition).
-#    The template's workspace path is rewritten to honor -WorkspaceDir.
-#    Under `npx pi-revit`, npx prepends its ephemeral cache's node_modules\.bin to
-#    PATH, and that folder holds a pi shim pulled in via peerDependencies. A launcher
-#    written next to that shim lands in a folder that is neither on the user's own
-#    PATH nor long-lived, so skip pi entries inside this package's node_modules tree
-#    or any npx cache and use the user's permanent pi instead.
-function Get-PermanentPiCommand {
-    # Long-form both sides of the prefix comparison: PATH entries may carry 8.3
-    # short names (SOMEUS~1.NAM) while $PSScriptRoot is normalized, and a form
-    # mismatch would silently defeat the own-tree exclusion.
-    function Resolve-LongPath([string]$p) {
-        try { (Get-Item -LiteralPath $p -ErrorAction Stop).FullName } catch { $p }
-    }
-    $ownTree = $null
-    $repoRoot = Resolve-LongPath (Split-Path $PSScriptRoot -Parent)
-    $idx = $repoRoot.LastIndexOf('\node_modules\', [StringComparison]::OrdinalIgnoreCase)
-    if ($idx -ge 0) { $ownTree = $repoRoot.Substring(0, $idx + '\node_modules\'.Length) }
-    Get-Command pi -All -ErrorAction SilentlyContinue | Where-Object {
-        if (-not $_.Source) { return $false }
-        $src = Resolve-LongPath $_.Source
-        ($src -notmatch '\\_npx\\') -and
-        (-not $ownTree -or -not $src.StartsWith($ownTree, [StringComparison]::OrdinalIgnoreCase))
-    } | Select-Object -First 1
-}
-
-$pi = Get-PermanentPiCommand
-if ($pi) {
-    $binDir = Split-Path $pi.Source -Parent
-    # Literal line swap (no regex): the workspace path may contain characters
-    # like $ that a -replace replacement string would misinterpret.
-    $globalCmd = Get-Content (Join-Path $templates 'pi-revit-global.cmd') | ForEach-Object {
-        if ($_ -like 'set "WORKSPACE=*') { 'set "WORKSPACE=' + $WorkspaceDir + '"' } else { $_ }
-    }
-    # cmd.exe parses .cmd files in the console's OEM code page: write the launcher
-    # in that encoding so workspace paths with non-ASCII characters (user names,
-    # localized folder names) stay intact.
-    Set-Content -Path (Join-Path $binDir 'pi-revit.cmd') -Value $globalCmd -Encoding Oem
-    Write-Host "Global command installed: $(Join-Path $binDir 'pi-revit.cmd')" -ForegroundColor Green
-    Write-Host 'Run pi-revit from any terminal (pi-revit -c continues the last session).'
-} else {
-    Write-Warning 'No permanent pi command found on PATH. Install Pi first (npm install -g --ignore-scripts @earendil-works/pi-coding-agent), then run npx.cmd -y pi-revit again (or re-run this script) to get the global pi-revit command.'
-}
+#Requires -Version 5.1
+<#
+Sets up the pi-revit user environment on this PC:
+
+  1. Workspace at Documents\pi-revit (AGENTS.md conventions, Models\ output tree,
+     double-click launcher). An existing AGENTS.md is never overwritten.
+  2. Global `pi-revit` command installed next to the `pi` command, so any terminal can run:
+       pi-revit              -> Pi in the workspace
+       pi-revit -c           -> continue the last session
+     Model output sorts itself: the Revit tools file each export under
+     Models\<model title>\ automatically, keyed by the document it came from.
+
+Idempotent — safe to re-run. Usage:
+  scripts\setup-workspace.ps1
+  scripts\setup-workspace.ps1 -WorkspaceDir "D:\work\pi-revit"
+#>
+param(
+    [string]$WorkspaceDir = (Join-Path ([Environment]::GetFolderPath('MyDocuments')) 'pi-revit')
+)
+
+$ErrorActionPreference = 'Stop'
+$templates = Join-Path (Split-Path $PSScriptRoot -Parent) 'workspace'
+
+# 1. Workspace folders. Models\ is where the Revit tools file per-model output.
+New-Item -ItemType Directory -Force -Path (Join-Path $WorkspaceDir 'Models') | Out-Null
+
+# Conventions / notes: copy only when missing so user edits survive re-runs.
+$workspaceAgents = Join-Path $WorkspaceDir 'AGENTS.md'
+if (-not (Test-Path $workspaceAgents)) {
+    Copy-Item (Join-Path $templates 'AGENTS.md') $workspaceAgents
+}
+
+# Launcher is code, not user data: always refresh.
+Copy-Item (Join-Path $templates 'pi-revit-here.cmd') (Join-Path $WorkspaceDir 'pi-revit.cmd') -Force
+
+Write-Host "Workspace ready: $WorkspaceDir" -ForegroundColor Green
+
+# 2. Global pi-revit command next to pi (that directory is on PATH by definition).
+#    The template's workspace path is rewritten to honor -WorkspaceDir.
+#    Under `npx pi-revit`, npx prepends its ephemeral cache's node_modules\.bin to
+#    PATH, and that folder holds a pi shim pulled in via peerDependencies. A launcher
+#    written next to that shim lands in a folder that is neither on the user's own
+#    PATH nor long-lived, so skip pi entries inside this package's node_modules tree
+#    or any npx cache and use the user's permanent pi instead.
+function Get-PermanentPiCommand {
+    # Long-form both sides of the prefix comparison: PATH entries may carry 8.3
+    # short names (SOMEUS~1.NAM) while $PSScriptRoot is normalized, and a form
+    # mismatch would silently defeat the own-tree exclusion.
+    function Resolve-LongPath([string]$p) {
+        try { (Get-Item -LiteralPath $p -ErrorAction Stop).FullName } catch { $p }
+    }
+    $ownTree = $null
+    $repoRoot = Resolve-LongPath (Split-Path $PSScriptRoot -Parent)
+    $idx = $repoRoot.LastIndexOf('\node_modules\', [StringComparison]::OrdinalIgnoreCase)
+    if ($idx -ge 0) { $ownTree = $repoRoot.Substring(0, $idx + '\node_modules\'.Length) }
+    Get-Command pi -All -ErrorAction SilentlyContinue | Where-Object {
+        if (-not $_.Source) { return $false }
+        $src = Resolve-LongPath $_.Source
+        ($src -notmatch '\\_npx\\') -and
+        (-not $ownTree -or -not $src.StartsWith($ownTree, [StringComparison]::OrdinalIgnoreCase))
+    } | Select-Object -First 1
+}
+
+$pi = Get-PermanentPiCommand
+if ($pi) {
+    $binDir = Split-Path $pi.Source -Parent
+    # Literal line swap (no regex): the workspace path may contain characters
+    # like $ that a -replace replacement string would misinterpret.
+    $globalCmd = Get-Content (Join-Path $templates 'pi-revit-global.cmd') | ForEach-Object {
+        if ($_ -like 'set "WORKSPACE=*') { 'set "WORKSPACE=' + $WorkspaceDir + '"' } else { $_ }
+    }
+    # cmd.exe parses .cmd files in the console's OEM code page: write the launcher
+    # in that encoding so workspace paths with non-ASCII characters (user names,
+    # localized folder names) stay intact.
+    Set-Content -Path (Join-Path $binDir 'pi-revit.cmd') -Value $globalCmd -Encoding Oem
+    Write-Host "Global command installed: $(Join-Path $binDir 'pi-revit.cmd')" -ForegroundColor Green
+    Write-Host 'Run pi-revit from any terminal (pi-revit -c continues the last session).'
+} else {
+    Write-Warning 'No permanent pi command found on PATH. Install Pi first (npm install -g --ignore-scripts @earendil-works/pi-coding-agent), then run npx.cmd -y pi-revit again (or re-run this script) to get the global pi-revit command.'
+}

package/scripts/uninstall.ps1

@@ -1,146 +1,146 @@
-#Requires -Version 5.1
-<#
-Removes everything the pi-revit install scripts placed on this PC:
-
-  - Revit bridge add-in:  %APPDATA%\Autodesk\Revit\Addins\<version>\RevitBridge.addin
-                          %APPDATA%\Autodesk\Revit\Addins\<version>\RevitBridge\
-  - Global command:       the pi-revit command next to the pi command
-  - Bridge runtime:       %APPDATA%\RevitBridge\ (per-start connection token / bridge.json)
-  - Pi package:           the pi-revit registration (pi remove), best-effort when pi is on PATH
-
-The workspace at Documents\pi-revit holds YOUR data (AGENTS.md notes, per-project
-session history) and is preserved by default. Pass -RemoveWorkspace to delete it too.
-
-Pi itself (the global coding agent) is yours to manage and is never touched.
-
-Close Revit before running. Idempotent — safe to re-run.
-
-Usage:
-  scripts\uninstall.ps1
-  scripts\uninstall.ps1 -RevitVersion 2027
-  scripts\uninstall.ps1 -RemoveWorkspace
-#>
-param(
-    [string]$RevitVersion = '',
-    [string]$WorkspaceDir = (Join-Path ([Environment]::GetFolderPath('MyDocuments')) 'pi-revit'),
-    [switch]$RemoveWorkspace
-)
-
-$ErrorActionPreference = 'Stop'
-
-function Remove-IfExists {
-    param([string]$Path, [string]$Label)
-    if (Test-Path -LiteralPath $Path) {
-        Remove-Item -LiteralPath $Path -Recurse -Force
-        Write-Host "Removed $Label : $Path" -ForegroundColor Green
-    } else {
-        Write-Host "Not present, skipped $Label : $Path"
-    }
-}
-
-# 1. Revit add-in. With no -RevitVersion, sweep every Addins\<version> folder so the
-#    user need not remember which Revit they deployed to.
-$addinsRoot = Join-Path $env:APPDATA 'Autodesk\Revit\Addins'
-$versions = if ($RevitVersion) {
-    @($RevitVersion)
-} elseif (Test-Path -LiteralPath $addinsRoot) {
-    Get-ChildItem -LiteralPath $addinsRoot -Directory | ForEach-Object { $_.Name }
-} else {
-    @()
-}
-foreach ($v in $versions) {
-    $dir = Join-Path $addinsRoot $v
-    Remove-IfExists (Join-Path $dir 'RevitBridge.addin') "Revit $v add-in manifest"
-    Remove-IfExists (Join-Path $dir 'RevitBridge')       "Revit $v add-in folder"
-}
-
-# 2. Global pi-revit command next to the user's permanent pi. When this script runs
-#    from an npx cache or a node_modules copy, PATH may lead Get-Command to a pi shim
-#    inside that ephemeral tree first (see setup-workspace.ps1) — the launcher was
-#    never installed there, so resolve the permanent pi the same way setup does.
-function Get-PermanentPiCommand {
-    # Long-form both sides of the prefix comparison: PATH entries may carry 8.3
-    # short names (SOMEUS~1.NAM) while $PSScriptRoot is normalized, and a form
-    # mismatch would silently defeat the own-tree exclusion.
-    function Resolve-LongPath([string]$p) {
-        try { (Get-Item -LiteralPath $p -ErrorAction Stop).FullName } catch { $p }
-    }
-    $ownTree = $null
-    $repoRoot = Resolve-LongPath (Split-Path $PSScriptRoot -Parent)
-    $idx = $repoRoot.LastIndexOf('\node_modules\', [StringComparison]::OrdinalIgnoreCase)
-    if ($idx -ge 0) { $ownTree = $repoRoot.Substring(0, $idx + '\node_modules\'.Length) }
-    Get-Command pi -All -ErrorAction SilentlyContinue | Where-Object {
-        if (-not $_.Source) { return $false }
-        $src = Resolve-LongPath $_.Source
-        ($src -notmatch '\\_npx\\') -and
-        (-not $ownTree -or -not $src.StartsWith($ownTree, [StringComparison]::OrdinalIgnoreCase))
-    } | Select-Object -First 1
-}
-
-$pi = Get-Command pi -ErrorAction SilentlyContinue
-$piPermanent = Get-PermanentPiCommand
-if ($piPermanent) {
-    $binDir = Split-Path $piPermanent.Source -Parent
-    Remove-IfExists (Join-Path $binDir 'pi-revit.cmd') 'global pi-revit command'
-} else {
-    Write-Host 'No permanent pi found on PATH; skipping the global pi-revit command.'
-}
-
-# 3. Bridge runtime folder (connection token; recreated on each Revit start).
-Remove-IfExists (Join-Path $env:APPDATA 'RevitBridge') 'bridge runtime folder'
-
-# 4. Pi package registration. Pi keys a package by its install source: the npm
-#    installer (npx.cmd -y pi-revit) registers `npm:pi-revit`, while an install
-#    from a clone of this repo (`pi install ./`) registers the repo path resolved
-#    from the repo root. Try both forms; each succeeds only for the source that
-#    is actually registered, so a machine with both gets both removed.
-if ($pi) {
-    $repoRoot = Split-Path $PSScriptRoot -Parent
-    # When this script runs from the npm-installed copy, `pi remove npm:pi-revit`
-    # deletes the very folder the script lives in — and Windows fails that delete
-    # (EBUSY) while any working directory sits inside it. Step our own process out
-    # if needed; the calling shell's location we can only warn about.
-    if ($repoRoot -match '\\node_modules\\' -and
-        (Get-Location).Path.StartsWith($repoRoot, [StringComparison]::OrdinalIgnoreCase)) {
-        Set-Location $env:SystemRoot
-        Write-Warning "This PowerShell was started inside $repoRoot. If the package removal below fails, run 'cd \' in your shell and re-run the uninstall."
-    }
-    try {
-        $removed = @()
-        # './' resolves against the repo root, so it runs from there — and first,
-        # while this folder is guaranteed to still exist. 'npm:pi-revit' then runs
-        # from a neutral directory so no working directory blocks the folder delete.
-        foreach ($source in @('./', 'npm:pi-revit')) {
-            Push-Location $(if ($source -eq './') { $repoRoot } else { $env:SystemRoot })
-            try {
-                $global:LASTEXITCODE = 0
-                & pi remove $source
-                if ($LASTEXITCODE -eq 0) {
-                    $removed += $source
-                }
-            } finally {
-                Pop-Location
-            }
-        }
-        if ($removed.Count -gt 0) {
-            Write-Host "Removed the pi-revit Pi package ($($removed -join ', '))." -ForegroundColor Green
-        } else {
-            Write-Warning "No pi-revit Pi package registration was found. If pi still lists it, run 'pi remove npm:pi-revit' (npm install) or 'pi remove ./' from this repo (install from source)."
-        }
-    } catch {
-        Write-Warning "Could not auto-remove the Pi package; run 'pi remove npm:pi-revit' (npm install) or 'pi remove ./' from this repo (install from source). ($_)"
-    }
-}
-
-# 5. Workspace (user data) — opt-in only.
-if ($RemoveWorkspace) {
-    Remove-IfExists $WorkspaceDir 'workspace'
-} else {
-    Write-Host ''
-    Write-Host "Workspace preserved (your notes + session history): $WorkspaceDir" -ForegroundColor Yellow
-    Write-Host 'Pass -RemoveWorkspace to delete it too.'
-}
-
-Write-Host ''
-Write-Host 'pi-revit uninstalled. Pi itself is untouched; remove it yourself if you want:' -ForegroundColor Green
-Write-Host '  npm uninstall -g @earendil-works/pi-coding-agent'
+#Requires -Version 5.1
+<#
+Removes everything the pi-revit install scripts placed on this PC:
+
+  - Revit bridge add-in:  %APPDATA%\Autodesk\Revit\Addins\<version>\RevitBridge.addin
+                          %APPDATA%\Autodesk\Revit\Addins\<version>\RevitBridge\
+  - Global command:       the pi-revit command next to the pi command
+  - Bridge runtime:       %APPDATA%\RevitBridge\ (per-start connection token / bridge.json)
+  - Pi package:           the pi-revit registration (pi remove), best-effort when pi is on PATH
+
+The workspace at Documents\pi-revit holds YOUR data (AGENTS.md notes, per-project
+session history) and is preserved by default. Pass -RemoveWorkspace to delete it too.
+
+Pi itself (the global coding agent) is yours to manage and is never touched.
+
+Close Revit before running. Idempotent — safe to re-run.
+
+Usage:
+  scripts\uninstall.ps1
+  scripts\uninstall.ps1 -RevitVersion 2027
+  scripts\uninstall.ps1 -RemoveWorkspace
+#>
+param(
+    [string]$RevitVersion = '',
+    [string]$WorkspaceDir = (Join-Path ([Environment]::GetFolderPath('MyDocuments')) 'pi-revit'),
+    [switch]$RemoveWorkspace
+)
+
+$ErrorActionPreference = 'Stop'
+
+function Remove-IfExists {
+    param([string]$Path, [string]$Label)
+    if (Test-Path -LiteralPath $Path) {
+        Remove-Item -LiteralPath $Path -Recurse -Force
+        Write-Host "Removed $Label : $Path" -ForegroundColor Green
+    } else {
+        Write-Host "Not present, skipped $Label : $Path"
+    }
+}
+
+# 1. Revit add-in. With no -RevitVersion, sweep every Addins\<version> folder so the
+#    user need not remember which Revit they deployed to.
+$addinsRoot = Join-Path $env:APPDATA 'Autodesk\Revit\Addins'
+$versions = if ($RevitVersion) {
+    @($RevitVersion)
+} elseif (Test-Path -LiteralPath $addinsRoot) {
+    Get-ChildItem -LiteralPath $addinsRoot -Directory | ForEach-Object { $_.Name }
+} else {
+    @()
+}
+foreach ($v in $versions) {
+    $dir = Join-Path $addinsRoot $v
+    Remove-IfExists (Join-Path $dir 'RevitBridge.addin') "Revit $v add-in manifest"
+    Remove-IfExists (Join-Path $dir 'RevitBridge')       "Revit $v add-in folder"
+}
+
+# 2. Global pi-revit command next to the user's permanent pi. When this script runs
+#    from an npx cache or a node_modules copy, PATH may lead Get-Command to a pi shim
+#    inside that ephemeral tree first (see setup-workspace.ps1) — the launcher was
+#    never installed there, so resolve the permanent pi the same way setup does.
+function Get-PermanentPiCommand {
+    # Long-form both sides of the prefix comparison: PATH entries may carry 8.3
+    # short names (SOMEUS~1.NAM) while $PSScriptRoot is normalized, and a form
+    # mismatch would silently defeat the own-tree exclusion.
+    function Resolve-LongPath([string]$p) {
+        try { (Get-Item -LiteralPath $p -ErrorAction Stop).FullName } catch { $p }
+    }
+    $ownTree = $null
+    $repoRoot = Resolve-LongPath (Split-Path $PSScriptRoot -Parent)
+    $idx = $repoRoot.LastIndexOf('\node_modules\', [StringComparison]::OrdinalIgnoreCase)
+    if ($idx -ge 0) { $ownTree = $repoRoot.Substring(0, $idx + '\node_modules\'.Length) }
+    Get-Command pi -All -ErrorAction SilentlyContinue | Where-Object {
+        if (-not $_.Source) { return $false }
+        $src = Resolve-LongPath $_.Source
+        ($src -notmatch '\\_npx\\') -and
+        (-not $ownTree -or -not $src.StartsWith($ownTree, [StringComparison]::OrdinalIgnoreCase))
+    } | Select-Object -First 1
+}
+
+$pi = Get-Command pi -ErrorAction SilentlyContinue
+$piPermanent = Get-PermanentPiCommand
+if ($piPermanent) {
+    $binDir = Split-Path $piPermanent.Source -Parent
+    Remove-IfExists (Join-Path $binDir 'pi-revit.cmd') 'global pi-revit command'
+} else {
+    Write-Host 'No permanent pi found on PATH; skipping the global pi-revit command.'
+}
+
+# 3. Bridge runtime folder (connection token; recreated on each Revit start).
+Remove-IfExists (Join-Path $env:APPDATA 'RevitBridge') 'bridge runtime folder'
+
+# 4. Pi package registration. Pi keys a package by its install source: the npm
+#    installer (npx.cmd -y pi-revit) registers `npm:pi-revit`, while an install
+#    from a clone of this repo (`pi install ./`) registers the repo path resolved
+#    from the repo root. Try both forms; each succeeds only for the source that
+#    is actually registered, so a machine with both gets both removed.
+if ($pi) {
+    $repoRoot = Split-Path $PSScriptRoot -Parent
+    # When this script runs from the npm-installed copy, `pi remove npm:pi-revit`
+    # deletes the very folder the script lives in — and Windows fails that delete
+    # (EBUSY) while any working directory sits inside it. Step our own process out
+    # if needed; the calling shell's location we can only warn about.
+    if ($repoRoot -match '\\node_modules\\' -and
+        (Get-Location).Path.StartsWith($repoRoot, [StringComparison]::OrdinalIgnoreCase)) {
+        Set-Location $env:SystemRoot
+        Write-Warning "This PowerShell was started inside $repoRoot. If the package removal below fails, run 'cd \' in your shell and re-run the uninstall."
+    }
+    try {
+        $removed = @()
+        # './' resolves against the repo root, so it runs from there — and first,
+        # while this folder is guaranteed to still exist. 'npm:pi-revit' then runs
+        # from a neutral directory so no working directory blocks the folder delete.
+        foreach ($source in @('./', 'npm:pi-revit')) {
+            Push-Location $(if ($source -eq './') { $repoRoot } else { $env:SystemRoot })
+            try {
+                $global:LASTEXITCODE = 0
+                & pi remove $source
+                if ($LASTEXITCODE -eq 0) {
+                    $removed += $source
+                }
+            } finally {
+                Pop-Location
+            }
+        }
+        if ($removed.Count -gt 0) {
+            Write-Host "Removed the pi-revit Pi package ($($removed -join ', '))." -ForegroundColor Green
+        } else {
+            Write-Warning "No pi-revit Pi package registration was found. If pi still lists it, run 'pi remove npm:pi-revit' (npm install) or 'pi remove ./' from this repo (install from source)."
+        }
+    } catch {
+        Write-Warning "Could not auto-remove the Pi package; run 'pi remove npm:pi-revit' (npm install) or 'pi remove ./' from this repo (install from source). ($_)"
+    }
+}
+
+# 5. Workspace (user data) — opt-in only.
+if ($RemoveWorkspace) {
+    Remove-IfExists $WorkspaceDir 'workspace'
+} else {
+    Write-Host ''
+    Write-Host "Workspace preserved (your notes + session history): $WorkspaceDir" -ForegroundColor Yellow
+    Write-Host 'Pass -RemoveWorkspace to delete it too.'
+}
+
+Write-Host ''
+Write-Host 'pi-revit uninstalled. Pi itself is untouched; remove it yourself if you want:' -ForegroundColor Green
+Write-Host '  npm uninstall -g @earendil-works/pi-coding-agent'

package/skills/pi-revit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pi-revit
-description: Work with the open Autodesk Revit model through the Revit bridge tools (ping, get_model_overview, get_elements, get_element_details, get_element_types, manage_selection, set_parameters, search_api_docs, execute_csharp, capture_view, export_documents, get_model_health). Use when the user asks about the Revit project, its elements, parameters, selection, or wants to change, script, capture, or export the model.
+description: Work with the open Autodesk Revit model through the Revit bridge tools (ping, get_model_overview, get_elements, get_element_details, get_element_types, manage_selection, open_view, set_parameters, search_api_docs, execute_csharp, capture_view, export_documents, get_model_health). Use when the user asks about the Revit project, its elements, parameters, selection, or wants to change, script, capture, or export the model.
 ---
 
 # Revit
@@ -17,6 +17,7 @@ Work with the live Revit model. The tools call a headless bridge add-in inside R
 | Read parameter VALUES, location, bounding box, materials of specific elements | `get_element_details` |
 | List element types / family symbols; "used vs merely loaded" | `get_element_types` |
 | Read or change the user's selection; zoom; temporary isolate | `manage_selection` |
+| Put a view or sheet on the user's screen (activate it) | `open_view` |
 | Write parameter values; rename anything (levels, views, sheets, types) | `set_parameters` |
 | Look up Revit API classes/members/signatures | `search_api_docs` |
 | Everything else (create, delete, move, views, sheets, tagging, ...) | `execute_csharp` |

package/src/Revit/BridgeServer.cs

@@ -1,3 +1,4 @@
+using System.Diagnostics;
 using System.IO;
 using System.Net;
 using System.Net.Sockets;
@@ -40,8 +41,13 @@ namespace RevitBridge
         private readonly string _revitVersion;
         private readonly Func<bool> _hasOpenDocument;
 
+        /// <summary>How often the bridge re-checks that bridge.json still points somewhere
+        /// live (see EnsureBridgeInfo). Cheap: one small file read per tick.</summary>
+        private static readonly TimeSpan InfoRefreshInterval = TimeSpan.FromSeconds(30);
+
         private TcpListener? _listener;
         private CancellationTokenSource? _cts;
+        private Timer? _infoTimer;
         private string _token = string.Empty;
         private int _port;
 
@@ -79,11 +85,16 @@ namespace RevitBridge
                 throw new InvalidOperationException($"Unable to start the Revit bridge on localhost ports {DefaultPort}-{MaxPort}.");
 
             WriteBridgeInfo();
+            _infoTimer = new Timer(_ => EnsureBridgeInfo(), null, InfoRefreshInterval, InfoRefreshInterval);
             _ = Task.Run(() => AcceptLoopAsync(_cts.Token));
         }
 
         public void Stop()
         {
+            // Dispose the refresh timer first: a tick that fired after the delete below
+            // would put the file back and advertise a bridge that is shutting down.
+            try { _infoTimer?.Dispose(); } catch { }
+            _infoTimer = null;
             try { _cts?.Cancel(); } catch { }
             try { _listener?.Stop(); } catch { }
             _listener = null;
@@ -119,6 +130,62 @@ namespace RevitBridge
             }, new JsonSerializerOptions { WriteIndented = true }));
         }
 
+        /// <summary>
+        /// Keeps bridge.json pointing at a bridge that actually answers. Only one file can
+        /// describe "the" bridge, so with two Revits open the newer one owns it (last
+        /// started wins) — but when that owner goes away, this one is still listening and
+        /// would otherwise be undiscoverable forever: closing the newer Revit deletes the
+        /// file, and killing it leaves a stale pid behind that pi cannot reach.
+        ///
+        /// So: rewrite the file when it is missing or names a process that is no longer
+        /// running. A file owned by a LIVE other process is never touched, so two running
+        /// instances cannot flap the file back and forth.
+        /// </summary>
+        private void EnsureBridgeInfo()
+        {
+            try
+            {
+                if (_listener is null)
+                    return; // stopped between the tick and here
+
+                string path = BridgeInfoPath();
+                if (File.Exists(path))
+                {
+                    using var doc = JsonDocument.Parse(File.ReadAllText(path));
+                    if (doc.RootElement.TryGetProperty("pid", out var pidElement) && pidElement.TryGetInt32(out int pid))
+                    {
+                        if (pid == Environment.ProcessId || IsProcessAlive(pid))
+                            return;
+                    }
+                    else
+                    {
+                        return; // no pid to judge by: leave whatever wrote it alone
+                    }
+                }
+
+                WriteBridgeInfo();
+            }
+            catch
+            {
+                // A corrupt or briefly locked file is retried on the next tick; this must
+                // never surface as an unhandled exception on a background thread.
+            }
+        }
+
+        private static bool IsProcessAlive(int pid)
+        {
+            try
+            {
+                using var process = Process.GetProcessById(pid);
+                return !process.HasExited;
+            }
+            catch
+            {
+                // GetProcessById throws when nothing runs under that id.
+                return false;
+            }
+        }
+
         private static void DeleteBridgeInfoIfOwned()
         {
             try

package/src/Revit/ToolRegistry.cs

@@ -71,6 +71,7 @@ namespace RevitBridge
             registry.Add(new GetElementTypes());
             registry.Add(new GetElementDetails());
             registry.Add(new ManageSelection());
+            registry.Add(new OpenView());
             registry.Add(new SetParameters());
             registry.Add(new CaptureView());
             registry.Add(new ExportDocuments());