pi-revit 0.2.12 → 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,53 +1,53 @@
----
-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, 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
-
-Work with the live Revit model. The tools call a headless bridge add-in inside Revit (2025, 2026, or 2027); Revit must be running with a project open (only `ping` and `search_api_docs` work without a document).
-
-## Tool selection
-
-| Task | Tool |
-|------|------|
-| Bridge alive? Which Revit version? | `ping` |
-| Orientation: project info, units, levels, grids, category counts | `get_model_overview` |
-| List or count elements of ANY category (walls, doors, rooms, sheets, views, ...) | `get_elements` |
-| 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` |
-| PNG snapshot of a view (visual QA) | `capture_view` (advanced) |
-| PDF/DWG/PNG/IFC file export | `export_documents` (advanced) |
-| Warnings / model quality audit | `get_model_health` (advanced) |
-
-Workflow guidance:
-
-- Call `get_model_overview` first when starting work on an unfamiliar model — one call returns project metadata, units, levels, grids, and category counts.
-- `get_elements` is the listing/counting primitive (`count_only: true` for bare counts). It returns identity fields only (id, name, category, typeName, levelId); read parameter values with `get_element_details`. Prefer a `category` or `of_class` scope when filtering by a parameter's display name.
-- The selection pipeline is `get_elements` -> ids -> `manage_selection` (action `set`); there is no inline filter on selection.
-- `set_parameters` is the home for bulk parameter writes AND renames (the `Name` parameter covers levels, views, sheets, types). One transaction per batch; per-element failures are reported. Pass `expected_document` (the model title) when several models are open or the session is long — it makes the write fail cleanly instead of landing in a different active document.
-- Parameter display names are LOCALIZED: in a non-English Revit UI, `Mark` is `Kennzeichen` (German), `マーク` (Japanese), etc. When a display-name lookup or `parameter_names` filter finds nothing, or the document may be non-English, use the language-independent `BuiltInParameter` enum name instead (e.g. `ALL_MODEL_MARK` for Mark, `ALL_MODEL_INSTANCE_COMMENTS` for Comments) — `set_parameters`, `get_element_details.parameter_names`, and `get_elements` filter rules all accept them, and `get_element_details` reports each parameter's `builtInParameter` name for discovery.
-- Before writing `execute_csharp` code, verify unfamiliar classes/members with `search_api_docs` (works with no document open; first query builds the index and takes a few seconds). The top match carries its remarks, parameter docs, and returns inline, and every public API enum value is searchable — trust the result over guessing or web search; narrow the query to promote a different match into the top slot.
-- `export_documents` files its output under `Documents\pi-revit\Models\<model title>\exports` automatically when `output_dir` is omitted — keyed to the exported document, so it lands right even across many models. Pass `output_dir` only when the user names a different target.
-
-## execute_csharp playbook
-
-- Globals: `doc` (Document), `uidoc` (UIDocument), `uiapp` (UIApplication), and `Dump(value)` to record intermediates into the result's `dumps[]`.
-- The transaction is automatic: the whole script runs inside ONE backend-owned transaction — committed on success, rolled back on any exception. Do not open your own `Transaction` (sub-transactions are fine).
-- Scripts must be fully synchronous: `await`/`async` is rejected at compile time; never block on `Task.Result`/`.Wait()`.
-- Return primitives, strings, or anonymous objects/lists; raw Revit API objects are projected to compact shapes (Element -> `{id,name,category,typeName,levelId}`, ElementId -> number, XYZ -> `{x,y,z}`).
-- Lengths are internal units (decimal feet) — convert with `UnitUtils.ConvertToInternalUnits`/`ConvertFromInternalUnits`.
-- Common pitfalls: call `FamilySymbol.Activate()` before `NewFamilyInstance`; use collector-level filtering (`OfCategory`/`OfClass`/`WhereElementIsNotElementType`) and bounded loops — the budget is 120s and Revit cannot be interrupted mid-script; modal dialogs are auto-dismissed and reported in `suppressedDialogs`.
-- `capture_view` returns a `filePath` to a temp PNG, never image data — open it with the read tool to actually see it.
-
-## Failure modes
-
-- **Bridge not reachable** ("Revit bridge is not available" / "Could not reach the Revit bridge"): Revit is not running or the add-in did not load. Ask the user to start Revit, then retry `ping`.
-- **HTTP 409 / "No active Revit document is open."** (`hasActiveDocument: false`): Revit is running but no project is open. Ask the user to open a project, then retry. This fails immediately; do not wait or retry blindly.
-- **Timeout** ("Revit did not answer within Ns", 30s default / 120s for execute_csharp, capture_view, export_documents): Revit is busy or showing a modal dialog. An already-started tool still runs to completion in Revit — verify model state (e.g. `get_elements`) before re-issuing a write.
-- **Cancelled**: same caveat — the bridge cannot abort queued or running work, so verify model state before retrying a write tool.
+---
+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, 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
+
+Work with the live Revit model. The tools call a headless bridge add-in inside Revit (2025, 2026, or 2027); Revit must be running with a project open (only `ping` and `search_api_docs` work without a document).
+
+## Tool selection
+
+| Task | Tool |
+|------|------|
+| Bridge alive? Which Revit version? | `ping` |
+| Orientation: project info, units, levels, grids, category counts | `get_model_overview` |
+| List or count elements of ANY category (walls, doors, rooms, sheets, views, ...) | `get_elements` |
+| 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` |
+| PNG snapshot of a view (visual QA) | `capture_view` (advanced) |
+| PDF/DWG/PNG/IFC file export | `export_documents` (advanced) |
+| Warnings / model quality audit | `get_model_health` (advanced) |
+
+Workflow guidance:
+
+- Call `get_model_overview` first when starting work on an unfamiliar model — one call returns project metadata, units, levels, grids, and category counts.
+- `get_elements` is the listing/counting primitive (`count_only: true` for bare counts). It returns identity fields only (id, name, category, typeName, levelId); read parameter values with `get_element_details`. Prefer a `category` or `of_class` scope when filtering by a parameter's display name.
+- The selection pipeline is `get_elements` -> ids -> `manage_selection` (action `set`); there is no inline filter on selection.
+- `set_parameters` is the home for bulk parameter writes AND renames (the `Name` parameter covers levels, views, sheets, types). One transaction per batch; per-element failures are reported. Pass `expected_document` (the model title) when several models are open or the session is long — it makes the write fail cleanly instead of landing in a different active document.
+- Parameter display names are LOCALIZED: in a non-English Revit UI, `Mark` is `Kennzeichen` (German), `マーク` (Japanese), etc. When a display-name lookup or `parameter_names` filter finds nothing, or the document may be non-English, use the language-independent `BuiltInParameter` enum name instead (e.g. `ALL_MODEL_MARK` for Mark, `ALL_MODEL_INSTANCE_COMMENTS` for Comments) — `set_parameters`, `get_element_details.parameter_names`, and `get_elements` filter rules all accept them, and `get_element_details` reports each parameter's `builtInParameter` name for discovery.
+- Before writing `execute_csharp` code, verify unfamiliar classes/members with `search_api_docs` (works with no document open; first query builds the index and takes a few seconds). The top match carries its remarks, parameter docs, and returns inline, and every public API enum value is searchable — trust the result over guessing or web search; narrow the query to promote a different match into the top slot.
+- `export_documents` files its output under `Documents\pi-revit\Models\<model title>\exports` automatically when `output_dir` is omitted — keyed to the exported document, so it lands right even across many models. Pass `output_dir` only when the user names a different target.
+
+## execute_csharp playbook
+
+- Globals: `doc` (Document), `uidoc` (UIDocument), `uiapp` (UIApplication), and `Dump(value)` to record intermediates into the result's `dumps[]`.
+- The transaction is automatic: the whole script runs inside ONE backend-owned transaction — committed on success, rolled back on any exception. Do not open your own `Transaction` (sub-transactions are fine).
+- Scripts must be fully synchronous: `await`/`async` is rejected at compile time; never block on `Task.Result`/`.Wait()`.
+- Return primitives, strings, or anonymous objects/lists; raw Revit API objects are projected to compact shapes (Element -> `{id,name,category,typeName,levelId}`, ElementId -> number, XYZ -> `{x,y,z}`).
+- Lengths are internal units (decimal feet) — convert with `UnitUtils.ConvertToInternalUnits`/`ConvertFromInternalUnits`.
+- Common pitfalls: call `FamilySymbol.Activate()` before `NewFamilyInstance`; use collector-level filtering (`OfCategory`/`OfClass`/`WhereElementIsNotElementType`) and bounded loops — the budget is 120s and Revit cannot be interrupted mid-script; modal dialogs are auto-dismissed and reported in `suppressedDialogs`.
+- `capture_view` returns a `filePath` to a temp PNG, never image data — open it with the read tool to actually see it.
+
+## Failure modes
+
+- **Bridge not reachable** ("Revit bridge is not available" / "Could not reach the Revit bridge"): Revit is not running or the add-in did not load. Ask the user to start Revit, then retry `ping`.
+- **HTTP 409 / "No active Revit document is open."** (`hasActiveDocument: false`): Revit is running but no project is open. Ask the user to open a project, then retry. This fails immediately; do not wait or retry blindly.
+- **Timeout** ("Revit did not answer within Ns", 30s default / 120s for execute_csharp, capture_view, export_documents): Revit is busy or showing a modal dialog. An already-started tool still runs to completion in Revit — verify model state (e.g. `get_elements`) before re-issuing a write.
+- **Cancelled**: same caveat — the bridge cannot abort queued or running work, so verify model state before retrying a write tool.