📦 deps(thirdparty): update snapshots

antigravity-awesome-skills/skills/debugging-code/references/advanced-techniques.md

@@ -0,0 +1,50 @@
+# Advanced Debugging Techniques
+
+## When the Program Hangs
+
+When a program runs but never returns, that *is* information — something is stuck. Don't guess; interrupt
+and observe.
+
+```
+Bug: program hangs (infinite loop or deadlock)
+
+→ dap pause                         ← interrupt wherever it is (returns OK immediately)
+  [the already-blocking debug/continue/step call returns auto-context: location + locals]
+  Stopped at process() · worker.py:55, locals: i=99999
+→ dap threads                       ← are other threads blocked too?
+→ dap eval "lock.locked()"          ← test deadlock hypothesis
+Root cause: lock never released. Fix → dap stop.
+```
+
+Check: is it one thread stuck (infinite loop, blocking I/O), or are multiple threads waiting on each
+other (deadlock)? The location where `pause` stops is your first clue.
+
+## Digging Into Complex State
+
+When a variable is opaque or deeply nested, expand it: `dap inspect data --depth 2`.
+
+## Concurrency Bugs
+
+If state is wrong but the code path looks correct, consider: is another thread modifying state
+concurrently?
+
+**First move at any concurrent crash or hang:** run `dap threads`, then inspect every thread's stack with
+`dap thread <id>` — the thread causing the problem is often not the one currently stopped.
+
+- **Deadlock pattern**: two or more threads each waiting for a resource the other holds. Check thread
+  states to confirm.
+- **Race condition**: unexpected values that change between stops. Look for shared mutable state
+  accessed without synchronization.
+
+## Bisecting Loops (Wolf Fence)
+
+A loop goes wrong at an unknown iteration. Binary search it:
+
+```
+dap debug app.py --break "app.py:45:i == 500"   # midpoint of 1000
+→ dap eval "is_valid(result)"                    # True → bug is after 500
+→ dap break add "app.py:45:i == 750"             # update the condition
+→ dap restart                                    # restart preserving new breakpoint
+```
+
+~10 iterations to find the bug in 1000. Not 1000 step commands.

antigravity-awesome-skills/skills/debugging-code/references/installing-debuggers.md

@@ -0,0 +1,67 @@
+# Installing Debug Adapters
+
+`dap` relies on language-specific debug adapters (backends). Many IDEs already ship them — **check before installing**.
+
+---
+
+## Python — debugpy
+
+**Check:** `python3 -m debugpy --version`
+
+**Install:** `pip install debugpy`
+
+**Virtualenv:** `dap` picks up the active venv automatically via `$VIRTUAL_ENV`.
+Activate the venv (`source .venv/bin/activate`) before running `dap debug`, or pass
+`--python /path/to/venv/bin/python` to override. Without either, `dap` falls back
+to `python3` on PATH — which may not have `debugpy` installed or may be the wrong
+interpreter version.
+
+---
+
+## Go — Delve
+
+**Check:** `dlv version`
+
+**Install:**
+- macOS: `brew install delve` (or `go install github.com/go-delve/delve/cmd/dlv@latest`)
+- Linux: `go install github.com/go-delve/delve/cmd/dlv@latest`
+
+macOS note: you may need `sudo DevToolsSecurity -enable` for debugging permissions.
+
+---
+
+## Node.js/TypeScript — js-debug
+
+`dap` auto-discovers js-debug from common locations:
+- VS Code extensions (`~/.vscode/extensions/`)
+- Cursor extensions (`~/.cursor/extensions/`)
+- Standalone install (`~/.dap-cli/js-debug/`)
+
+**Check:** Look for js-debug in the paths above, or run `dap debug --backend js-debug script.js` — if it fails, install below.
+
+**Standalone install** (only if not found above):
+```bash
+DAP_VER=$(curl -fsSL https://api.github.com/repos/microsoft/vscode-js-debug/releases/latest | grep -o '"tag_name":"[^"]*"' | cut -d'"' -f4) && \
+mkdir -p ~/.dap-cli/js-debug && \
+curl -fsSL "https://github.com/microsoft/vscode-js-debug/releases/download/${DAP_VER}/js-debug-dap-${DAP_VER}.tar.gz" | tar -xz -C ~/.dap-cli/js-debug
+```
+
+Also supports **Chrome DevTools debugging** for browser-side JavaScript.
+
+---
+
+## Rust/C/C++ — lldb-dap
+
+**Check:** `lldb-dap --version`
+
+**Install:**
+- macOS: `brew install llvm` (v18+ required)
+- Linux: `apt install lldb` (or equivalent for your distro)
+
+After Homebrew install, ensure the Homebrew `llvm` bin is on your PATH (e.g. `export PATH="$(brew --prefix llvm)/bin:$PATH"`).
+
+---
+
+## Known Gotchas
+
+- **lldb-dap on macOS**: The version bundled with Xcode Command Line Tools (v17) lacks the `--connection` flag that `dap` requires. Use the Homebrew `llvm` package (v18+) instead.