CodeVetter · Repo Unpack · Behavior traces
vercel/turborepo
Three concrete flows were followed: CLI startup, task execution with cache persistence, and standard login with credential persistence. The traces retain branches that change execution, including local-binary selection, graph-only runs, cache hits, cache failures, and existing-token reuse. These are source-derived execution sequences, not runtime observations.
- Startup: binary main → turborepo_cli::main → raise_open_file_limit → shim::run; internal LSP requests return before this ordinary path.
- Startup continues: normalize_config_dir_env_vars → ShimArgs::parse → TurboSubscriber construction → ShimRuntime::new → run_with_args; TurboCliRunner then delegates to cli::run.
- CLI startup: Args::new → init_rayon_pool → Tokio runtime → run_main → deferred telemetry initialization → get_command → inference flags and repository root → agent guidance maintenance.
- Run setup: commands::run creates signals and log sinks → RunBuilder::new → execute_run → run_with_ui → RunBuilder::build → start_ui → Run::run.
- Run execution: Run::run starts proxy/shutdown services; graph mode writes the graph and returns 0, otherwise execute_visitor constructs Visitor, enables dry-run when requested, visits the engine, and derives the exit code.
- Task branch: execute_inner → restore_outputs; a hit updates the hash tracker and skips spawning, while a miss or logged fetch error proceeds through serial-group locking to ProcessManager::spawn.
- Persistence branch: execute flushes output and sends the completion callback before save_outputs; only a successful Run outcome is eligible, and FSCache writes archive entries, atomically finishes the archive, then writes sidecars.
- Standard login: login → login_no_sso → auth_login; reusable credentials return without writing, otherwise Vercel device login performs discover → authorization request → poll_for_token → get_user, then write_token persists the returned credentials.