@eyeauras/insight-cli 0.2.4 → 0.3.0

package/skill-bundle/insight-re/references/artifacts.md

@@ -1,7 +1,7 @@
 # Save ordinary research materials
 
 `insight-cli artifacts save <path> --json` saves a file or a settled directory tree in
-the selected profile's AppData. It needs Factory Update permission and does not require
+the selected profile's [analysis storage](storage.md), which defaults to AppData. It needs Factory Update permission and does not require
 Ghidra, Java, authentication, target/session selectors or evidence metadata. Relative input
 paths resolve against the caller's working directory. Use `--help` for generated syntax.
 

package/skill-bundle/insight-re/references/storage.md

@@ -0,0 +1,99 @@
+# Analysis storage and migration
+
+`storage show --json` reports effective profile storage, availability, active file/byte usage,
+exact included trees and retained migration. The default is Factory profile AppData. No
+checkout, environment or automatic disk fallback changes it. The non-secret setting is
+`analysisDirectory` in Factory's profile (`profile show` also displays it). Use storage commands
+to change it safely.
+
+```sh
+insight-cli permissions grant Update
+insight-cli storage show --json
+insight-cli storage configure --directory "/mnt/analysis volume" --json
+```
+
+`configure` requires no existing analysis entries. With existing data use `migrate`.
+The directory is a **base**: the effective root appends `insight-cli/<profile>`, preserving
+profile isolation. Choose an ordinary empty destination profile directory on a mounted local
+filesystem. Spaces and Unicode are supported. Factory restricts the dedicated destination root to the
+current user, including a Windows ACL; a filesystem that cannot apply this protection fails
+before copying.
+
+The complete `workspace`, `materials`, `temp` and `runtime` trees move: immutable inputs,
+artifact/candidate snapshots, workspace SQLite DB/WAL, native private project/context DBs,
+local Ghidra Server repositories, operation/publication/import journals, debugger traces,
+process captures, exports, native helper compilation and verification working data.
+**Runtime installations, acquisition caches, selections and process receipts move too**;
+installation staging and activation must share a filesystem. External tool installations and
+user-selected outputs outside these trees keep their locations.
+
+Factory keeps profiles, permissions, IPC election/socket, migration-control metadata and
+application logs in current-user AppData. Secrets stay in the OS keyring. Credential/profile
+identities do not change. Updating/installing npm never migrates a profile automatically.
+
+## Move an existing profile
+
+Finish changing commands, close native contexts, and stop this profile's owned server/tool
+processes through ordinary CLI commands. Inspect `tools processes --json`. Unverified lifetimes
+also block migration. Do not kill guessed PIDs or stop other profiles to make preflight pass.
+Factory retains IPC ownership and command admission; other profiles can keep working.
+
+```sh
+insight-cli storage migrate --directory "/mnt/analysis volume" --dry-run --json
+insight-cli storage migrate --directory "/mnt/analysis volume" --json
+insight-cli storage show --json
+```
+
+Dry-run checks separation, destination contents, access, conservative capacity and quiescence
+without reserving/copying a migration. Source/destination/configuration roots cannot be equal
+or nested. Destination symlink roots, escaping source links, special files, unresolved links
+and inventories above one million entries or 128 directory levels are rejected. Internal
+links retain their exact target strings. Preflight does not reserve space; concurrent disk use
+can still cause a copy failure.
+
+Migration durably reserves its journal, hashes stable source bytes, streams/syncs the copy,
+independently hashes destination bytes and rechecks the source. Only then does it replace source
+trees with permanent compatibility links and commit the Factory setting. Original trees are
+renamed into `.storage-retained/<migration>` on their original volume. Copy/activation never
+deletes them, including on failures. Existing IDs, requests, journals, candidate snapshots and
+receipts retain exact bytes. Compatibility paths preserve old absolute references: do not remove
+those links or their profile/source ancestors manually after migrating.
+
+## Interruptions, uncertainty and retention
+
+```sh
+insight-cli storage resume --json
+insight-cli storage rollback --json
+```
+
+Ordinary research freezes during incomplete copy/activation/rollback/cleanup. `show` and Factory
+profile inspection remain available. Resume verifies completed files, recopies an incomplete
+file, rechecks capacity and finishes the retained transaction. Source and destination filesystem
+anchor identities are bound durably. Missing/replaced volumes fail without creating a system-disk
+fallback; mount the original volume before resuming.
+
+Rollback restores retained source and the prior Factory setting. After activation it requires
+an unchanged destination and a verified retained source. Native reopening or later findings can
+make rollback unsafe, in which case it refuses and preserves both copies. Use forward migration
+to another empty base after using the new location. A rolled-back destination remains for manual
+inspection/removal and is never automatically adopted. Cleanup permanently disables rollback.
+
+Unknown script/publication effects do **not** need abandonment before migrating a stopped
+profile. Migration starts no worker, replays no script/check-in and marks no unknown outcome
+applied. Inspect the original request after migrating; existing [recovery](recovery.md)
+restrictions and independent readback requirements still apply.
+
+After independent native reopen and saved-file readback, free retained source explicitly:
+
+```sh
+insight-cli permissions grant Destructive
+insight-cli storage cleanup --json
+```
+
+Cleanup verifies retained bytes, records irreversible intent, then deletes only that owned
+backup. Interrupted cleanup continues through `storage resume`; rollback is already disabled.
+Compatibility links, receipts and manifests remain. Clean or roll back the current migration
+before starting another. This release provides no nonempty-destination adoption, reverse
+synchronization, live-DB snapshotting or network-filesystem guarantees. POSIX directory fsync
+is used. Windows has file fsync and rename/junction semantics; Node cannot fsync directories
+there, and internal symlinks can require OS privileges.

package/skill-bundle/insight-sevenzip/SKILL.md

@@ -3,7 +3,7 @@ name: insight-sevenzip
 description: Inventory, integrity-check and recover files from archives and supported containers with insight-cli 7-Zip, then hand recovered binaries or configuration to the appropriate research tool.
 ---
 
-# Insight 7-Zip 0.2.4
+# Insight 7-Zip 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skill-bundle/insight-strace/SKILL.md

@@ -3,7 +3,7 @@ name: insight-strace
 description: Observe actual file reads, writes, process creation and network syscalls in an authorized owned native Linux launch using insight-cli strace. Use when static inference needs concrete operating-system interaction evidence.
 ---
 
-# Insight strace 0.2.4
+# Insight strace 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skill-bundle/insight-tshark/SKILL.md

@@ -3,7 +3,7 @@ name: insight-tshark
 description: Inspect an offline PCAP or PCAPNG with insight-cli tshark to identify protocols, HTTP/DNS/TLS fields, packet evidence and reconstructed TCP/UDP streams. Use for captured traffic questions; live acquisition and TLS decryption are separate tasks.
 ---
 
-# Insight TShark 0.2.4
+# Insight TShark 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skill-bundle/insight-windbg/SKILL.md

@@ -3,7 +3,7 @@ name: insight-windbg
 description: Investigate Windows native user-mode minidumps using bounded stacks, threads, registers, modules, memory and disassembly through insight-cli windbg. Use on Windows x64 when a captured runtime state needs native debugger evidence.
 ---
 
-# Insight WinDbg 0.2.4
+# Insight WinDbg 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skill-bundle/manifest.json

@@ -1,7 +1,7 @@
 {
   "schema": 1,
   "package": "@eyeauras/insight-cli",
-  "version": "0.2.4",
+  "version": "0.3.0",
   "skills": [
     "insight-cli",
     "insight-re",

package/skills/insight-artifacts/SKILL.md

@@ -3,7 +3,7 @@ name: insight-artifacts
 description: Retain a completed reverse-engineering evidence file or directory as an ordinary checkpoint using insight-cli artifacts save. Use after Ghidra or any external tool; preserve existing project formats and source of truth.
 ---
 
-# Insight Artifacts 0.2.4
+# Insight Artifacts 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-artifacts/references/artifacts.md

@@ -1,7 +1,7 @@
 # Save ordinary research materials
 
 `insight-cli artifacts save <path> --json` saves a file or a settled directory tree in
-the selected profile's AppData. It needs Factory Update permission and does not require
+the selected profile's [analysis storage](storage.md), which defaults to AppData. It needs Factory Update permission and does not require
 Ghidra, Java, authentication, target/session selectors or evidence metadata. Relative input
 paths resolve against the caller's working directory. Use `--help` for generated syntax.
 

package/skills/insight-artifacts/references/recovery.md

@@ -0,0 +1,79 @@
+# Continue saved work
+
+Retain the session/target returned by initial open. Continue the tuple through
+`insight-cli ghidra open --session <id> --target <id> --json`. Saved private snapshots and
+pending scalar comparisons persist independently of a backend process. Reopening preserves
+private work; it does not silently receive a newer shared version.
+
+First-import recovery uses the same scoped `ghidra open` or the original request ID/input.
+Import/analysis writes a private snapshot and completion receipt before any initial publication.
+If its worker is still running, continuation reports busy; wait and continue the same scope.
+If that worker stopped before completing its receipt, continuation can repeat private analysis
+from the immutable input while retaining previous attempts. A completed snapshot is reused.
+Initial publication first creates a uniquely named staging object. A separate read-only process
+verifies its complete saved DB buffers before a conditional server move to the absent canonical
+path. It never checks in a new version of an existing canonical item. Lost promotion replies
+are reconciled against the retained identity, one-version history and complete saved buffers.
+Interrupted staging objects remain retained and can be replaced by another private stage;
+they are not adopted as the canonical model. Foreign or mismatched canonical state stays blocked.
+An older direct create that is provably owned and left only an incomplete `<Recovered>` entry
+can be moved aside without deletion; its bytes and original receipt remain preserved.
+
+Legacy first-import failures are also recoverable in the original profile. Continuation first
+establishes that the old owned bootstrap worker has ended, then uses an authoritative repository
+probe. An absent canonical item permits private preparation; an existing first version requires
+independent readback. The old project, intent and original session/target remain preserved.
+
+If a response was lost, inspect `sessions status <session> --target <target>`. Never infer
+`applied` from a connection failure. A changing command's optional request ID binds one effective
+intent inside the profile. Repeating the same ID/input retrieves its recorded outcome or
+unresolved state; changing input under that ID fails. Without an ID, calls are new intentions.
+
+An unknown or partial effect retains its request intent, snapshots and native stage. Open the
+same tuple to reconcile supported outcomes. A committed merge is verified against its recorded
+server version and complete saved buffers through independent read authority; it is never
+checked in again merely because its response was lost. Until verification succeeds, publication
+for this shared target is blocked across sessions. Saved private work remains retained.
+
+Scalar reconciliation observes and saves an already present effect; it does not execute the
+setter again. Supported structural/function edits retain a candidate snapshot after an incomplete
+response; continuation can verify every requested effect in that immutable snapshot and adopt it
+without replay. If the complete result cannot be established, the candidate and previous saved
+private view remain retained. An unproved program/script/external outcome remains unresolved. Preserve the profile
+storage and credential store. Do not delete another session's project, stop a process by guessed
+PID/port, or blindly repeat a script/external action to turn uncertainty into success.
+
+The older prototype's `workers`, `findings`, `integrate` and batch `recover` commands are not the
+public facade API. Its coordinator journals remain separate and are never silently migrated.
+
+A lost UI navigation response can be verified from the live authenticated cursor without another
+goto. If its original owned GUI process has exited, continuation reports the uncertain UI action
+as disconnected and retains saved program work. It does not recreate the old cursor or re-enable
+a previous prompt policy. Other unproved live UI effects remain retained until their outcome is
+established or the original process is known to have ended.
+
+## Abandon an uncertain private program attempt
+
+A post-mutation save timeout does not repeat the script or issue another save in the
+error handler. Status exposes the original request identity and retained phase/budget.
+Arbitrary script effects are never inferred from metadata or from an unverified DB.
+After inspecting the retained attempt, explicitly stop only its verified owned worker
+(`tools processes`, then `tools processes kill <process>` if required). Resume the
+last acknowledged private snapshot with:
+
+```sh
+insight-cli permissions grant Destructive
+insight-cli ghidra abandon --session <session> --target <target> \
+  --request-id <original-request> --acknowledge-unknown-effects --json
+insight-cli ghidra open --session <session> --target <target> --json
+```
+
+Abandon requires exactly one unresolved private program operation, an unchanged verified
+previous snapshot/generation, a stopped original worker and no active publication or live
+debugger. It retains the native project, candidate artifacts, original intent/execution and
+previous diagnostic result. Its terminal request is `failed` / `state: abandoned` with
+`outcome: unknown`; no effect is marked applied. Repeating abandonment retrieves the same
+result. Earlier saved private edits remain pending. The original changing request ID cannot
+execute again. Abandoning never undoes external effects or establishes what an arbitrary
+script did; the acknowledgement explicitly accepts that uncertainty. Publication recovery,
+initial import, UI and debugger attempts use their own protocols and cannot use this command.

package/skills/insight-artifacts/references/storage.md

@@ -0,0 +1,99 @@
+# Analysis storage and migration
+
+`storage show --json` reports effective profile storage, availability, active file/byte usage,
+exact included trees and retained migration. The default is Factory profile AppData. No
+checkout, environment or automatic disk fallback changes it. The non-secret setting is
+`analysisDirectory` in Factory's profile (`profile show` also displays it). Use storage commands
+to change it safely.
+
+```sh
+insight-cli permissions grant Update
+insight-cli storage show --json
+insight-cli storage configure --directory "/mnt/analysis volume" --json
+```
+
+`configure` requires no existing analysis entries. With existing data use `migrate`.
+The directory is a **base**: the effective root appends `insight-cli/<profile>`, preserving
+profile isolation. Choose an ordinary empty destination profile directory on a mounted local
+filesystem. Spaces and Unicode are supported. Factory restricts the dedicated destination root to the
+current user, including a Windows ACL; a filesystem that cannot apply this protection fails
+before copying.
+
+The complete `workspace`, `materials`, `temp` and `runtime` trees move: immutable inputs,
+artifact/candidate snapshots, workspace SQLite DB/WAL, native private project/context DBs,
+local Ghidra Server repositories, operation/publication/import journals, debugger traces,
+process captures, exports, native helper compilation and verification working data.
+**Runtime installations, acquisition caches, selections and process receipts move too**;
+installation staging and activation must share a filesystem. External tool installations and
+user-selected outputs outside these trees keep their locations.
+
+Factory keeps profiles, permissions, IPC election/socket, migration-control metadata and
+application logs in current-user AppData. Secrets stay in the OS keyring. Credential/profile
+identities do not change. Updating/installing npm never migrates a profile automatically.
+
+## Move an existing profile
+
+Finish changing commands, close native contexts, and stop this profile's owned server/tool
+processes through ordinary CLI commands. Inspect `tools processes --json`. Unverified lifetimes
+also block migration. Do not kill guessed PIDs or stop other profiles to make preflight pass.
+Factory retains IPC ownership and command admission; other profiles can keep working.
+
+```sh
+insight-cli storage migrate --directory "/mnt/analysis volume" --dry-run --json
+insight-cli storage migrate --directory "/mnt/analysis volume" --json
+insight-cli storage show --json
+```
+
+Dry-run checks separation, destination contents, access, conservative capacity and quiescence
+without reserving/copying a migration. Source/destination/configuration roots cannot be equal
+or nested. Destination symlink roots, escaping source links, special files, unresolved links
+and inventories above one million entries or 128 directory levels are rejected. Internal
+links retain their exact target strings. Preflight does not reserve space; concurrent disk use
+can still cause a copy failure.
+
+Migration durably reserves its journal, hashes stable source bytes, streams/syncs the copy,
+independently hashes destination bytes and rechecks the source. Only then does it replace source
+trees with permanent compatibility links and commit the Factory setting. Original trees are
+renamed into `.storage-retained/<migration>` on their original volume. Copy/activation never
+deletes them, including on failures. Existing IDs, requests, journals, candidate snapshots and
+receipts retain exact bytes. Compatibility paths preserve old absolute references: do not remove
+those links or their profile/source ancestors manually after migrating.
+
+## Interruptions, uncertainty and retention
+
+```sh
+insight-cli storage resume --json
+insight-cli storage rollback --json
+```
+
+Ordinary research freezes during incomplete copy/activation/rollback/cleanup. `show` and Factory
+profile inspection remain available. Resume verifies completed files, recopies an incomplete
+file, rechecks capacity and finishes the retained transaction. Source and destination filesystem
+anchor identities are bound durably. Missing/replaced volumes fail without creating a system-disk
+fallback; mount the original volume before resuming.
+
+Rollback restores retained source and the prior Factory setting. After activation it requires
+an unchanged destination and a verified retained source. Native reopening or later findings can
+make rollback unsafe, in which case it refuses and preserves both copies. Use forward migration
+to another empty base after using the new location. A rolled-back destination remains for manual
+inspection/removal and is never automatically adopted. Cleanup permanently disables rollback.
+
+Unknown script/publication effects do **not** need abandonment before migrating a stopped
+profile. Migration starts no worker, replays no script/check-in and marks no unknown outcome
+applied. Inspect the original request after migrating; existing [recovery](recovery.md)
+restrictions and independent readback requirements still apply.
+
+After independent native reopen and saved-file readback, free retained source explicitly:
+
+```sh
+insight-cli permissions grant Destructive
+insight-cli storage cleanup --json
+```
+
+Cleanup verifies retained bytes, records irreversible intent, then deletes only that owned
+backup. Interrupted cleanup continues through `storage resume`; rollback is already disabled.
+Compatibility links, receipts and manifests remain. Clean or roll back the current migration
+before starting another. This release provides no nonempty-destination adoption, reverse
+synchronization, live-DB snapshotting or network-filesystem guarantees. POSIX directory fsync
+is used. Windows has file fsync and rename/junction semantics; Node cannot fsync directories
+there, and internal symlinks can require OS privileges.

package/skills/insight-binary/SKILL.md

@@ -3,7 +3,7 @@ name: insight-binary
 description: Query structured PE, ELF and thin Mach-O headers, sections, imports and exports, or make an explicitly guarded new PE subsystem copy through insight-cli binary. Use for scoped binary structure, linkage and copy-only header edits without target execution.
 ---
 
-# Insight Binary 0.2.4
+# Insight Binary 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-capture/SKILL.md

@@ -3,7 +3,7 @@ name: insight-capture
 description: Capture one explicitly authorized native program run, exact stdout/stderr and declared file snapshots through insight-cli capture, then inspect or compare retained reports without replay. Use for controlled input/output research, preserving original files and interrupted or unknown outcomes.
 ---
 
-# Insight Capture 0.2.4
+# Insight Capture 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-die/SKILL.md

@@ -3,7 +3,7 @@ name: insight-die
 description: Classify unknown executable or container inputs by format, architecture and compiler/runtime/packer signatures with Detect It Easy before choosing managed or native analysis. Use insight-cli die for static triage and preserve scan uncertainty.
 ---
 
-# Insight Detect It Easy 0.2.4
+# Insight Detect It Easy 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-dnspy/SKILL.md

@@ -3,7 +3,7 @@ name: insight-dnspy
 description: Debug a managed Windows EXE at an IL breakpoint and read primitive arguments, or change one expected IL Int32 constant in a new assembly copy through insight-cli dnspy. Use when C# decompilation needs observed execution or a controlled binary edit.
 ---
 
-# Insight dnSpyEx 0.2.4
+# Insight dnSpyEx 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-dotnet-dump/SKILL.md

@@ -3,7 +3,7 @@ name: insight-dotnet-dump
 description: Capture a managed heap dump or inspect compatible .NET dumps with SOS to recover waiting stacks, objects, fields and retention evidence.
 ---
 
-# Insight .NET Dump 0.2.4
+# Insight .NET Dump 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-dotnet-stack/SKILL.md

@@ -3,7 +3,7 @@ name: insight-dotnet-stack
 description: Inspect live managed thread stacks to identify active or waiting work in an explicitly selected .NET process without taking a dump.
 ---
 
-# Insight .NET Stack 0.2.4
+# Insight .NET Stack 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-dotnet-trace/SKILL.md

@@ -3,7 +3,7 @@ name: insight-dotnet-trace
 description: Collect and inspect bounded .NET EventPipe traces to identify sampled thread work, waits or runtime activity; distinguish wall-clock samples from CPU consumption.
 ---
 
-# Insight .NET Trace 0.2.4
+# Insight .NET Trace 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-frida/SKILL.md

@@ -3,7 +3,7 @@ name: insight-frida
 description: Observe native call arguments/results or inspect runtime modules and exports in an explicitly selected authorized process with bounded Frida scripts. Use insight-cli frida to corroborate static findings with actual execution on macOS ARM64.
 ---
 
-# Insight Frida 0.2.4
+# Insight Frida 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-ghidra/SKILL.md

@@ -3,7 +3,7 @@ name: insight-ghidra
 description: Inspect or edit native binaries with Ghidra through insight-cli; use isolated contexts, multi-agent merge/refresh, server, GUI or debugger workflows. Choose this for static native behavior and references, not C# recovery from managed IL.
 ---
 
-# Insight Ghidra 0.2.4
+# Insight Ghidra 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-ghidra/references/artifacts.md

@@ -1,7 +1,7 @@
 # Save ordinary research materials
 
 `insight-cli artifacts save <path> --json` saves a file or a settled directory tree in
-the selected profile's AppData. It needs Factory Update permission and does not require
+the selected profile's [analysis storage](storage.md), which defaults to AppData. It needs Factory Update permission and does not require
 Ghidra, Java, authentication, target/session selectors or evidence metadata. Relative input
 paths resolve against the caller's working directory. Use `--help` for generated syntax.
 

package/skills/insight-ghidra/references/managed-runtime.md

@@ -79,7 +79,7 @@ operations until `connect`/`start`. `server connect/disconnect` retain their con
 An external server remains configured through profile server/repository/account fields and Factory
 secrets; `server stop` cannot stop that external service.
 
-Code/cache/installation receipts live under profile AppData `runtime/`; research remains under
+Code/cache/installation receipts live under configured [analysis storage](storage.md) `runtime/`; research remains under
 `workspace/`, and saved files under `materials/`. One selected immutable installation serves many
 isolated JVM contexts; each has its own projects, home, settings, cache/temp and authenticated
 endpoint. No per-agent copy of the Ghidra code distribution is required. This is process and data

package/skills/insight-ghidra/references/setup.md

@@ -1,5 +1,9 @@
 # Setup
 
+Inspect `storage show --json` and read [analysis storage](storage.md) before moving databases.
+Use `storage configure` for an empty profile or `storage migrate` for existing work. Factory
+control metadata and keyring identity stay in their original locations.
+
 Use Node 24+ and `ghidra install` to deliver Ghidra 12.1.2, JDK 21, native components and
 server support. See [managed runtime](managed-runtime.md) for download/install/offline archives,
 external executable paths, status/doctor and safe removal. Existing Factory profile `java` and

package/skills/insight-ghidra/references/storage.md

@@ -0,0 +1,99 @@
+# Analysis storage and migration
+
+`storage show --json` reports effective profile storage, availability, active file/byte usage,
+exact included trees and retained migration. The default is Factory profile AppData. No
+checkout, environment or automatic disk fallback changes it. The non-secret setting is
+`analysisDirectory` in Factory's profile (`profile show` also displays it). Use storage commands
+to change it safely.
+
+```sh
+insight-cli permissions grant Update
+insight-cli storage show --json
+insight-cli storage configure --directory "/mnt/analysis volume" --json
+```
+
+`configure` requires no existing analysis entries. With existing data use `migrate`.
+The directory is a **base**: the effective root appends `insight-cli/<profile>`, preserving
+profile isolation. Choose an ordinary empty destination profile directory on a mounted local
+filesystem. Spaces and Unicode are supported. Factory restricts the dedicated destination root to the
+current user, including a Windows ACL; a filesystem that cannot apply this protection fails
+before copying.
+
+The complete `workspace`, `materials`, `temp` and `runtime` trees move: immutable inputs,
+artifact/candidate snapshots, workspace SQLite DB/WAL, native private project/context DBs,
+local Ghidra Server repositories, operation/publication/import journals, debugger traces,
+process captures, exports, native helper compilation and verification working data.
+**Runtime installations, acquisition caches, selections and process receipts move too**;
+installation staging and activation must share a filesystem. External tool installations and
+user-selected outputs outside these trees keep their locations.
+
+Factory keeps profiles, permissions, IPC election/socket, migration-control metadata and
+application logs in current-user AppData. Secrets stay in the OS keyring. Credential/profile
+identities do not change. Updating/installing npm never migrates a profile automatically.
+
+## Move an existing profile
+
+Finish changing commands, close native contexts, and stop this profile's owned server/tool
+processes through ordinary CLI commands. Inspect `tools processes --json`. Unverified lifetimes
+also block migration. Do not kill guessed PIDs or stop other profiles to make preflight pass.
+Factory retains IPC ownership and command admission; other profiles can keep working.
+
+```sh
+insight-cli storage migrate --directory "/mnt/analysis volume" --dry-run --json
+insight-cli storage migrate --directory "/mnt/analysis volume" --json
+insight-cli storage show --json
+```
+
+Dry-run checks separation, destination contents, access, conservative capacity and quiescence
+without reserving/copying a migration. Source/destination/configuration roots cannot be equal
+or nested. Destination symlink roots, escaping source links, special files, unresolved links
+and inventories above one million entries or 128 directory levels are rejected. Internal
+links retain their exact target strings. Preflight does not reserve space; concurrent disk use
+can still cause a copy failure.
+
+Migration durably reserves its journal, hashes stable source bytes, streams/syncs the copy,
+independently hashes destination bytes and rechecks the source. Only then does it replace source
+trees with permanent compatibility links and commit the Factory setting. Original trees are
+renamed into `.storage-retained/<migration>` on their original volume. Copy/activation never
+deletes them, including on failures. Existing IDs, requests, journals, candidate snapshots and
+receipts retain exact bytes. Compatibility paths preserve old absolute references: do not remove
+those links or their profile/source ancestors manually after migrating.
+
+## Interruptions, uncertainty and retention
+
+```sh
+insight-cli storage resume --json
+insight-cli storage rollback --json
+```
+
+Ordinary research freezes during incomplete copy/activation/rollback/cleanup. `show` and Factory
+profile inspection remain available. Resume verifies completed files, recopies an incomplete
+file, rechecks capacity and finishes the retained transaction. Source and destination filesystem
+anchor identities are bound durably. Missing/replaced volumes fail without creating a system-disk
+fallback; mount the original volume before resuming.
+
+Rollback restores retained source and the prior Factory setting. After activation it requires
+an unchanged destination and a verified retained source. Native reopening or later findings can
+make rollback unsafe, in which case it refuses and preserves both copies. Use forward migration
+to another empty base after using the new location. A rolled-back destination remains for manual
+inspection/removal and is never automatically adopted. Cleanup permanently disables rollback.
+
+Unknown script/publication effects do **not** need abandonment before migrating a stopped
+profile. Migration starts no worker, replays no script/check-in and marks no unknown outcome
+applied. Inspect the original request after migrating; existing [recovery](recovery.md)
+restrictions and independent readback requirements still apply.
+
+After independent native reopen and saved-file readback, free retained source explicitly:
+
+```sh
+insight-cli permissions grant Destructive
+insight-cli storage cleanup --json
+```
+
+Cleanup verifies retained bytes, records irreversible intent, then deletes only that owned
+backup. Interrupted cleanup continues through `storage resume`; rollback is already disabled.
+Compatibility links, receipts and manifests remain. Clean or roll back the current migration
+before starting another. This release provides no nonempty-destination adoption, reverse
+synchronization, live-DB snapshotting or network-filesystem guarantees. POSIX directory fsync
+is used. Windows has file fsync and rename/junction semantics; Node cannot fsync directories
+there, and internal symlinks can require OS privileges.

package/skills/insight-ilspy/SKILL.md

@@ -3,7 +3,7 @@ name: insight-ilspy
 description: Recover C#, inspect IL/types/metadata, extract resources or export projects from managed .NET assemblies through insight-cli ILSpy. Choose native analysis for NativeAOT or ordinary PE machine code.
 ---
 
-# Insight ILSpy 0.2.4
+# Insight ILSpy 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-interop/SKILL.md

@@ -3,7 +3,7 @@ name: insight-interop
 description: Trace a .NET P/Invoke declaration to an explicitly supplied native library export and Ghidra function through insight-cli ilspy query, binary query and scoped ghidra APIs. Use for managed/native linkage evidence while keeping static correspondence separate from observed loading or execution.
 ---
 
-# Insight Interop 0.2.4
+# Insight Interop 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-lldb/SKILL.md

@@ -3,7 +3,7 @@ name: insight-lldb
 description: Observe native runtime arguments, return values, registers, stacks and bounded memory at a selected breakpoint using an owned LLDB launch. Use insight-cli lldb on macOS ARM64 when static findings need a concrete execution check.
 ---
 
-# Insight LLDB 0.2.4
+# Insight LLDB 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized

package/skills/insight-llvm/SKILL.md

@@ -3,7 +3,7 @@ name: insight-llvm
 description: Inspect PE, ELF and Mach-O headers, dependencies, exports and symbols; query PDB debug information or a small instruction window with insight-cli LLVM utilities before opening a full analysis project.
 ---
 
-# Insight LLVM 0.2.4
+# Insight LLVM 0.3.0
 
 If local help/status reports AppData or IPC access denied, retry that **read-only probe**
 with the agent host's normal permission escalation, then use that route for later authorized