@probelabs/visor 0.1.124 → 0.1.126

package/dist/docs/proposals/snapshot-scope-execution.md

@@ -1,7 +1,7 @@
 # Snapshot + Scope Execution Model — Plan & Tracker
 
-Status: In progress
-Last updated: 2025-10-20
+Status: Nearly Complete (Phases 0-4 done; Phase 5 pending)
+Last updated: 2025-11
 
 This document captures an incremental plan to simplify Visor’s execution model using snapshot isolation (MVCC‑style) and scope‑aware output resolution, while preserving today’s routing semantics and recently added `on_finish` behavior (PR #146).
 
@@ -13,7 +13,7 @@ It also lists a set of quick wins we can land immediately to polish PR #146 and
 
 Priority scale: P0 = must‑have next; P1 = important; P2 = nice‑to‑have.
 
-Overall progress: ~85% complete (Phases 0–3 done; Phases 2 and 4 now complete; Phase 5 pending).
+Overall progress: ~90% complete (Phases 0-4 done; Phase 5 pending).
 
 | Phase | Priority | Status | % Complete | Notes |
 |---|---|---:|---:|---|
@@ -176,10 +176,11 @@ Acceptance
 Target: by 2025-11-01
 
 Phase 4 — Remove Per‑Iteration Map Cloning
-- [ ] Delete special “override resultsMap per iteration” code; rely on `ContextView` unwrapping.
+- [x] Delete special "override resultsMap per iteration" code; rely on `ContextView` unwrapping.
+- [x] Refactored to state-machine-execution-engine.ts with ScopePath + snapshot-based visibility in foreach-processor.ts
 
 Acceptance
-- [ ] Unit: forEach dependent checks still see the correct per‑item output.
+- [x] Unit: forEach dependent checks still see the correct per‑item output (verified via snapshot-store tests and routing-integration tests).
 
 Target: by 2025-11-04
 

package/dist/docs/providers/git-checkout.md

@@ -40,10 +40,11 @@ steps:
     token: "{{ env.GITHUB_TOKEN }}"
 
     # Optional: Fetch configuration
-    fetch_depth: 1                    # Shallow clone depth (default: 1)
+    fetch_depth: 1                    # Shallow clone depth (default: full history)
     fetch_tags: false                 # Fetch tags (default: false)
     submodules: false                 # Checkout submodules (default: false)
                                       # Can be: true, false, or 'recursive'
+    clone_timeout_ms: 300000          # Clone timeout in milliseconds (default: 300000 = 5 min)
 
     # Optional: Working directory (auto-generated if not specified)
     working_directory: /tmp/my-checkout
@@ -80,6 +81,7 @@ The provider returns the following output structure:
   worktree_id: string,      // Unique worktree identifier
   repository: string,       // Repository that was checked out
   is_worktree: boolean,     // Whether this is a worktree
+  workspace_path?: string,  // Human-readable path within workspace (when workspace isolation is enabled)
   error?: string,           // Error message if failed
 }
 ```
@@ -367,20 +369,20 @@ export VISOR_WORKTREE_PATH=/custom/path/to/worktrees
 
 This takes precedence over the config file.
 
-### CLI Commands for Worktree Management
+### Automatic Worktree Cleanup
 
-```bash
-# List all worktrees
-visor worktree list
+Worktrees are automatically cleaned up in the following scenarios:
 
-# Cleanup stale worktrees
-visor worktree cleanup
+- **On process exit**: When the visor process terminates normally
+- **On SIGINT/SIGTERM**: When the process receives interrupt signals (Ctrl+C)
+- **Age-based cleanup**: Worktrees older than `max_age_hours` are removed on subsequent runs
+- **Stale process cleanup**: Worktrees from dead processes are automatically removed
 
-# Cleanup all worktrees for a repository
-visor worktree cleanup --repo=owner/repo
+To manually clean up worktrees, you can remove the `.visor/worktrees/` directory:
 
-# Cleanup all worktrees (careful!)
-visor worktree cleanup --all
+```bash
+# Remove all worktrees for current project
+rm -rf .visor/worktrees/
 ```
 
 ## Best Practices
@@ -580,10 +582,10 @@ Typical performance (example repository: 100MB):
 
 - Configure `max_age_hours` to prevent disk exhaustion
 - Use timeouts to prevent hanging checkouts
-- Monitor disk usage in `/tmp/visor-worktrees/`
+- Monitor disk usage in `.visor/worktrees/` (or custom `VISOR_WORKTREE_PATH`)
 
 ## Related Documentation
 
-- [Command Provider](./command.md) - Execute commands in checked out code
-- [Workflow Provider](./workflow.md) - Compose multi-step workflows
+- [Command Provider](../command-provider.md) - Execute commands in checked out code
+- [Workflows](../workflows.md) - Compose multi-step workflows
 - [Configuration Reference](../configuration.md) - Full configuration options