@htekdev/actions-debugger 1.0.20 → 1.0.22

package/errors/known-unsolved/homebrew-transitive-dependency-not-guaranteed.yml

@@ -0,0 +1,133 @@
+id: known-unsolved-020
+title: "Homebrew Transitive Dependency Silently Removed — Only Documented Formulas Are Guaranteed"
+category: known-unsolved
+severity: limitation
+tags:
+  - macos
+  - homebrew
+  - transitive-dependency
+  - runner-image
+  - brew
+  - silent-removal
+  - limitation
+patterns:
+  - regex: "No such file or directory.*homebrew.*opt.*\\b(libevent|libiconv|libffi|gettext)\\b"
+    flags: "i"
+  - regex: "Library not loaded.*homebrew.*opt.*\\.dylib.*image not found"
+    flags: "i"
+  - regex: "brew.*error.*([a-z0-9_-]+): No available formula"
+    flags: "i"
+  - regex: "dyld.*Library not loaded.*/opt/homebrew/opt/[a-z0-9_-]+/lib"
+    flags: "i"
+error_messages:
+  - "Error: No such file or directory - /opt/homebrew/opt/libevent/lib/libevent.dylib"
+  - "dyld[80]: Library not loaded: /opt/homebrew/opt/libevent/lib/libevent.dylib"
+  - "pkg-config: Package 'libevent', required by 'virtual:world', not found"
+  - "CMake Error: Could not find a package configuration file provided by 'libevent'"
+root_cause: |
+  GitHub-hosted macOS runner images include a curated list of Homebrew formulae that are
+  **officially documented and guaranteed** (listed in the image README, e.g.
+  `images/macos/macos-15-Readme.md`). Any Homebrew package that is present on the image
+  only as a **transitive dependency** of another formula — not explicitly documented — can
+  silently disappear between image updates when the parent formula's dependency chain changes.
+
+  **What happens:**
+  When a documented formula is upgraded (e.g., `tmux`, `openssl@3`, `ffmpeg`), its new
+  version may no longer depend on the same set of transitive packages as the previous
+  version. The transitive dependency is removed from the image automatically in the next
+  image release, with no announcement, no deprecation notice, and no entry in the image
+  changelog.
+
+  **Real example:** `libevent` was present on `macos-15` images as a transitive dependency
+  of another documented formula. When that formula's dependency chain changed in the
+  `20260525.0142.1` image, `libevent` was removed. Workflows depending on `libevent`
+  (for building tmux from source, libevent-based C++ servers, etc.) began failing with
+  "No such file or directory" errors without any changes to the workflow itself.
+
+  GitHub's response (confirmed in runner-images#14170):
+  > "libevent has never been part of the documented Homebrew Formulae list. It was only
+  > present incidentally as a transitive dependency of another formula, and that
+  > dependency chain has changed in the newer image. Since libevent is not an officially
+  > preinstalled tool on the image, its presence is not guaranteed across image versions
+  > and we don't plan to pin it."
+
+  **This is by design and will not be fixed.** The GitHub runner-images team will not
+  guarantee transitive dependencies — only the explicitly documented formula list is stable.
+
+  Source: actions/runner-images#14170 (closed as `wontfix / not_planned`, May 2026).
+fix: |
+  The only reliable fix is to **explicitly install every library your workflow needs**,
+  regardless of whether it "happens to be there" on the current image.
+
+  **Immediate fix:** Add `brew install <missing-package>` as a workflow step before
+  any step that requires the package:
+
+  **Long-term fix:** Audit ALL your workflow's Homebrew dependencies and cross-reference
+  each one against the official runner image README. Any package NOT listed there must be
+  explicitly installed in your workflow.
+
+  **Finding the image README:**
+  - macOS 15: https://github.com/actions/runner-images/blob/main/images/macos/macos-15-Readme.md
+  - macOS 26: https://github.com/actions/runner-images/blob/main/images/macos/macos-26-Readme.md
+  If your package isn't in the "Homebrew Packages" section of the README, install it
+  explicitly — it's not guaranteed.
+fix_code:
+  - language: yaml
+    label: "Explicitly install transitive dependencies before use"
+    code: |
+      jobs:
+        build:
+          runs-on: macos-latest
+          steps:
+            - uses: actions/checkout@v4
+
+            # Explicitly install ALL required libraries — even ones that "used to be there"
+            - name: Install dependencies
+              run: |
+                brew install libevent libffi gettext
+                # Do NOT rely on transitive deps from other formulae
+
+            - name: Build
+              run: make
+  - language: yaml
+    label: "Audit step — verify dependencies are explicitly documented"
+    code: |
+      # Check if your dependency is in the official image README:
+      # curl -s https://raw.githubusercontent.com/actions/runner-images/main/images/macos/macos-15-Readme.md \
+      #   | grep -i "libevent"
+      # If no output → the package is NOT guaranteed → add brew install
+
+      - name: Ensure all dependencies are installed
+        run: |
+          # Install everything your build actually needs
+          brew install libevent tmux pkg-config
+  - language: yaml
+    label: "Cache explicit brew installs to reduce per-job overhead"
+    code: |
+      - name: Cache Homebrew packages
+        uses: actions/cache@v4
+        with:
+          path: |
+            ~/Library/Caches/Homebrew
+            /opt/homebrew/Cellar
+          key: ${{ runner.os }}-brew-${{ hashFiles('Brewfile') }}
+          restore-keys: |
+            ${{ runner.os }}-brew-
+
+      - name: Install dependencies from Brewfile
+        run: brew bundle
+prevention:
+  - "Never rely on a Homebrew package being preinstalled unless it is explicitly listed in the runner image's official README (linked below)."
+  - "Maintain a `Brewfile` in your repository and use `brew bundle` to install all macOS dependencies explicitly — this documents and enforces your true dependency set."
+  - "When a workflow starts failing on macOS runners after an image update, check the runner-images release notes for formula removals and cross-reference against the image README."
+  - "Subscribe to runner-images releases (GitHub → Watch → Releases) to get notified when the image README changes and transitive deps may be affected."
+  - "Run `brew deps --tree <your-installed-formula>` locally to identify which transitive deps your workflow relies on, then add explicit `brew install` calls for each."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/14170"
+    label: "runner-images#14170: macos-15 libevent removed as transitive dep (closed wontfix)"
+  - url: "https://github.com/actions/runner-images/blob/main/images/macos/macos-15-Readme.md"
+    label: "macOS 15 runner image README — official guaranteed software list"
+  - url: "https://github.com/actions/runner-images/blob/main/images/macos/macos-26-Readme.md"
+    label: "macOS 26 runner image README — official guaranteed software list"
+  - url: "https://docs.brew.sh/Manpage#bundle-subcommand"
+    label: "Homebrew Bundle subcommand — manage dependencies via Brewfile"

package/errors/runner-environment/android-sdk-api37-hash-mismatch.yml

@@ -0,0 +1,97 @@
+id: runner-environment-055
+title: "Android SDK Platform 37 Installed as 'android-37.0' — Builds Fail Looking for 'android-37'"
+category: runner-environment
+severity: error
+tags:
+  - android
+  - android-sdk
+  - gradle
+  - ubuntu-2404
+  - sdk-platform
+  - hash-string
+patterns:
+  - regex: "Failed to find target with hash string 'android-37'"
+    flags: "i"
+  - regex: "Failed to find target.*android-37[^\\d]"
+    flags: "i"
+  - regex: "Could not determine.*dependencies.*android-37[^\\d]"
+    flags: "i"
+  - regex: "platforms/android-37\\.0.*android-37[^\\.]"
+    flags: "i"
+error_messages:
+  - "Failed to find target with hash string 'android-37' in: /usr/local/lib/android/sdk"
+  - "Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'."
+  - "> Failed to find target with hash string 'android-37'"
+root_cause: |
+  On the Ubuntu 24.04 runner image (from approximately image version 20260323), the
+  Android SDK Platform 37 is installed under the directory name `android-37.0` rather
+  than the expected `android-37`. Gradle and the Android Gradle Plugin (AGP) look up
+  platform targets by their hash string (`android-37`), which must exactly match the
+  subdirectory name inside `$ANDROID_SDK_ROOT/platforms/`.
+
+  When `sdkmanager` installs `platforms;android-37.0`, it creates:
+    `/usr/local/lib/android/sdk/platforms/android-37.0/`
+
+  But AGP resolves `compileSdk = 37` (or `compileSdkVersion 37`) to hash string
+  `android-37`, not `android-37.0`. The lookup fails even though the SDK is physically
+  present on the runner (runner-images#13859).
+
+  Root cause in the runner image: the `platforms;android-37.0` package name was published
+  by Google with a `.0` version suffix in the SDK package path, causing a naming
+  inconsistency between the package identifier and the installed directory name expected
+  by build tools.
+fix: |
+  Add a workaround step that creates a symlink from `android-37` → `android-37.0` before
+  the Gradle build. This resolves the hash lookup without any source code changes.
+
+  Alternatively, pin `compileSdk` to 36 (which is installed normally) until the runner
+  image is fixed, or install `platforms;android-37` explicitly via sdkmanager — but note
+  that as of the time of writing the `android-37` (non-.0) package may not yet be
+  published to the official SDK registry.
+fix_code:
+  - language: yaml
+    label: "Symlink workaround — link android-37 to android-37.0 before build"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+
+        - name: Fix Android SDK 37 directory name mismatch
+          run: |
+            SDK_PLATFORMS="$ANDROID_SDK_ROOT/platforms"
+            if [ -d "$SDK_PLATFORMS/android-37.0" ] && [ ! -d "$SDK_PLATFORMS/android-37" ]; then
+              ln -s "$SDK_PLATFORMS/android-37.0" "$SDK_PLATFORMS/android-37"
+              echo "Symlinked android-37 -> android-37.0"
+            fi
+
+        - name: Build APK
+          run: ./gradlew assembleDebug
+  - language: yaml
+    label: "Pin compileSdk to 36 as temporary workaround"
+    code: |
+      # In app/build.gradle or build.gradle.kts:
+      android {
+          compileSdk = 36   # Use 36 until android-37 symlink issue is resolved
+          # compileSdk = 37  # <- caused 'android-37' hash mismatch
+      }
+  - language: yaml
+    label: "Install android-37 explicitly via sdkmanager"
+    code: |
+      steps:
+        - name: Install Android SDK Platform 37
+          run: |
+            echo "y" | $ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager \
+              "platforms;android-37" \
+              "build-tools;37.0.0"
+        - name: Build
+          run: ./gradlew assembleDebug
+prevention:
+  - "When upgrading `compileSdk` to a newly released Android API level, test against ubuntu-24.04 runners in a feature branch first before rolling out to all jobs."
+  - "Subscribe to runner-images releases for `ubuntu-24.04` to catch SDK directory naming changes early."
+  - "Add an explicit `sdkmanager` install step for the exact platform and build-tools version your project requires instead of relying on pre-installed SDKs."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/13859"
+    label: "runner-images#13859 — Ubuntu 24.04 installs API 37 as android-37.0; builds fail looking for android-37"
+  - url: "https://developer.android.com/studio/releases/platforms"
+    label: "Android SDK Platform releases — official platform package naming"
+  - url: "https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources"
+    label: "GitHub Docs — GitHub-hosted runner software"

package/errors/runner-environment/android-sdk-platforms-v33-removed.yml

@@ -0,0 +1,120 @@
+id: runner-environment-056
+title: "Android SDK Platforms and Build Tools < v34 Removed from Runner Images (Jan 2026)"
+category: runner-environment
+severity: error
+tags:
+  - android
+  - android-sdk
+  - gradle
+  - runner-images
+  - ubuntu-2204
+  - macos-14
+  - windows-2022
+  - compile-sdk
+patterns:
+  - regex: "Failed to find target with hash string 'android-3[0-3]'"
+    flags: "i"
+  - regex: "Failed to find Build Tools revision 3[0-3]\\."
+    flags: "i"
+  - regex: "Build Tools revision.*not installed|not installed.*Build Tools"
+    flags: "i"
+  - regex: "compileSdkVersion.*3[0-3].*not found|SDK Platform.*3[0-3].*not installed"
+    flags: "i"
+error_messages:
+  - "Failed to find target with hash string 'android-33' in: /usr/local/lib/android/sdk"
+  - "Failed to find Build Tools revision 33.0.2"
+  - "SDK Platform '33' is not installed."
+  - "Failed to find target with hash string 'android-32'"
+root_cause: |
+  Starting January 12, 2026, GitHub removed pre-installed Android SDK platforms and build
+  tools older than version 34 from the following runner images (runner-images#13469):
+
+  - Ubuntu 22.04
+  - macOS 14 (and macOS 14 Arm64)
+  - Windows Server 2022
+
+  Affected toolchain components:
+  - SDK Platforms: android-33 and older (Android 13 / API 33, API 32, etc.)
+  - Build Tools: versions older than 34.0.0
+
+  The removal was motivated by freeing up disk space. Projects that reference
+  `compileSdkVersion 33` (or lower) in their Gradle configuration, or that install
+  specific old build-tools versions, fail immediately because the expected directories are
+  absent from `$ANDROID_SDK_ROOT/platforms/` and `$ANDROID_SDK_ROOT/build-tools/`.
+
+  Note: Ubuntu 24.04, macOS 15, and Windows Server 2025 images were not affected because
+  they never carried the older SDK platforms.
+fix: |
+  Option A — Upgrade compileSdk and targetSdk to 34 or higher (recommended):
+    Updating to a supported API level removes the dependency on removed SDK packages.
+    API 34 (Android 14) is widely available and well-tested.
+
+  Option B — Install the required SDK platform at runtime:
+    Use `sdkmanager` in a workflow step to download and install the exact platform and
+    build tools version before the Gradle build runs. This adds ~30-60 seconds to the job.
+fix_code:
+  - language: yaml
+    label: "Upgrade compileSdk to 35 (recommended long-term fix)"
+    code: |
+      # In app/build.gradle.kts:
+      android {
+          compileSdk = 35        # upgraded from 33 — no SDK install step needed
+          targetSdk = 35
+          minSdk = 21
+      }
+  - language: yaml
+    label: "Install removed SDK platform at runtime (keeps compileSdk 33)"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+
+        - name: Install Android SDK Platform 33 and Build Tools 33.0.2
+          run: |
+            echo "y" | $ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager \
+              "platforms;android-33" \
+              "build-tools;33.0.2"
+
+        - name: Build
+          run: ./gradlew assembleDebug
+  - language: yaml
+    label: "Install SDK using android-actions/setup-android"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+        - uses: android-actions/setup-android@v3
+          with:
+            packages: >
+              platforms;android-33
+              build-tools;33.0.2
+        - run: ./gradlew assembleRelease
+  - language: yaml
+    label: "Matrix build: validate migration to newer API level"
+    code: |
+      jobs:
+        build:
+          strategy:
+            matrix:
+              compile-sdk: [33, 34, 35]
+          runs-on: ubuntu-22.04
+          steps:
+            - uses: actions/checkout@v4
+            - name: Install required SDK (only needed for API < 34)
+              if: matrix.compile-sdk < 34
+              run: |
+                echo "y" | $ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager \
+                  "platforms;android-${{ matrix.compile-sdk }}"
+            - run: ./gradlew assembleDebug
+              env:
+                COMPILE_SDK_VERSION: ${{ matrix.compile-sdk }}
+prevention:
+  - "Target `compileSdk` and `targetSdk` at API 34 or higher; Google Play requires API 35+ for new app submissions as of August 2025."
+  - "Audit your `build.gradle` files for hard-coded old `compileSdkVersion` values and migrate proactively during the announcement window."
+  - "Subscribe to runner-images GitHub Issues to see SDK removal announcements before they hit production workflows."
+  - "Add an explicit `sdkmanager` install step for any SDK version your build requires so the workflow is portable regardless of what's pre-installed."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/13469"
+    label: "runner-images#13469 — Android SDK platforms and build tools < v34 removed on Jan 12, 2026"
+  - url: "https://developer.android.com/tools/sdkmanager"
+    label: "Android Docs — sdkmanager command-line tool"
+  - url: "https://developer.android.com/google/play/requirements/target-sdk"
+    label: "Google Play — target API level requirements"

package/errors/runner-environment/force-node24-env-persistent-node20-annotation.yml

@@ -0,0 +1,127 @@
+id: runner-environment-057
+title: "FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 Still Emits Node 20 Deprecation Annotation"
+category: runner-environment
+severity: warning
+tags:
+  - node20
+  - node24
+  - deprecation
+  - annotation
+  - force-node24
+  - javascript-actions
+patterns:
+  - regex: "Node\\.js 20 is deprecated.*following actions target Node\\.js 20 but are being forced to run on Node\\.js 24"
+    flags: "i"
+  - regex: "The following actions target Node\\.?20 but are being forced to run on Node\\.?24"
+    flags: "i"
+  - regex: "following actions are running on Node\\.js 20 and may not work as expected"
+    flags: "i"
+error_messages:
+  - "Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: some-action@v1"
+  - "The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, custom-org/deploy@v2"
+  - "Node.js 20 actions are deprecated. The following actions are running on Node.js 20"
+root_cause: |
+  Setting `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"` in a workflow's `env:` section
+  successfully redirects JavaScript actions that declare `using: node20` to execute on
+  Node.js 24 at runtime. However, the runner still emits a deprecation annotation at
+  the end of every job listing those actions.
+
+  **Two distinct annotation messages depending on runner version:**
+
+  - **Pre-runner v2.326 (before PR#4303):** Inaccurate message — "The following actions
+    are **running on** Node.js 20 and may not work as expected" — even though they are
+    actually executing on Node 24. This is a bug in the runner's deprecation tracking
+    which recorded actions before the `FORCE_` env var was resolved.
+
+  - **Post-runner v2.326 (after PR#4303 fix):** Accurate but still present message —
+    "Node.js 20 is deprecated. The following actions **target** Node.js 20 but are
+    being forced to run on Node.js 24" — this annotation correctly describes the
+    situation but continues to appear as long as any action declares `using: node20`.
+
+  **Why this matters:** The annotation appears as a warning in GitHub's UI, turning
+  affected jobs "yellow" or showing red annotation badges, causing developer confusion
+  about whether `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24` is working. CI dashboards that
+  treat any annotation as a failure (strict mode) will block PRs.
+
+  **Root cause of persistence:** The annotation fires based on the action's *declared*
+  `using` field in `action.yml` (`node20`), not the *actual runtime* used. Even with
+  the force env var, the declaration still exists until the action author updates and
+  publishes a new release with `using: node24`.
+
+  Source: actions/runner#4295 (9 reactions, April 2026), fixed partially in runner PR#4303.
+fix: |
+  The only permanent fix is to eliminate the `using: node20` declaration from every
+  action listed in the annotation.
+
+  **If you control the action:**
+  Update `action.yml` to declare `runs.using: 'node24'`, recompile with Node 24, and
+  publish a new release. Downstream consumers must update their `uses:` pin.
+
+  **If you use a third-party action:**
+  Update to a newer version of the action that already ships `using: node24`. Check the
+  action's GitHub releases or `action.yml` on the latest tag.
+
+  **Temporary suppression (not recommended for long-term):**
+  Continue using `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"` — the action *does* run
+  on Node 24 despite the annotation. The annotation is informational. If you need
+  annotation-clean builds, the only path is action upgrades.
+
+  **Audit all actions in your workflow:**
+  Run this to find actions still declaring node20 in their action.yml:
+  ```bash
+  find . -name 'action.yml' -o -name 'action.yaml' | xargs grep -l 'using.*node20'
+  ```
+fix_code:
+  - language: yaml
+    label: "Upgrade pinned actions to node24-compatible major versions"
+    code: |
+      # Before: actions declaring using: node20 → emits annotation even with FORCE_ var
+      steps:
+        - uses: actions/checkout@v3          # node20 → upgrade to @v4
+        - uses: actions/cache@v3             # node20 → upgrade to @v4
+        - uses: actions/upload-artifact@v3   # node20 → upgrade to @v4
+
+      # After: actions declaring using: node24 → no annotation
+      steps:
+        - uses: actions/checkout@v4          # node24 ✅
+        - uses: actions/cache@v4             # node24 ✅
+        - uses: actions/upload-artifact@v4   # node24 ✅
+  - language: yaml
+    label: "For your own action.yml — update to node24"
+    code: |
+      # action.yml — before
+      runs:
+        using: 'node20'
+        main: 'dist/index.js'
+
+      # action.yml — after
+      runs:
+        using: 'node24'
+        main: 'dist/index.js'
+      # Also recompile: ncc build src/index.ts --license licenses.txt
+  - language: yaml
+    label: "Temporary escape hatch — FORCE env var (annotation still appears)"
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          env:
+            # Actions run on Node 24 but annotation still fires for node20 declarations
+            FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: 'true'
+          steps:
+            - uses: actions/checkout@v4
+prevention:
+  - "Pin to the latest major version of all official `actions/*` actions — they already ship `using: node24` in current releases."
+  - "Search your workflow files for `uses:` pins older than the current major version and update them in batch before Node 20 enforcement completes."
+  - "For private/internal actions, add a CI check that fails if any `action.yml` in the monorepo still declares `using: node20`."
+  - "Use `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true` only as a bridge, not a permanent solution — the annotation is a reminder that action.yml still needs updating."
+  - "Run periodic audits: `gh api /repos/ORG/REPO/contents/action.yml | jq .content | base64 -d | grep using`."
+docs:
+  - url: "https://github.com/actions/runner/issues/4295"
+    label: "actions/runner#4295: Node 20 deprecation warning fires even with FORCE_JAVASCRIPT_ACTIONS_TO_NODE24"
+  - url: "https://github.com/actions/runner/pull/4303"
+    label: "actions/runner#4303: Node 24 enforcement + Linux ARM32 deprecation support (fix)"
+  - url: "https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/"
+    label: "GitHub Changelog: Deprecation of Node 20 on GitHub Actions runners"
+  - url: "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions"
+    label: "Metadata syntax: runs.using for JavaScript actions"

package/errors/runner-environment/macos-26-homebrew-llvm-version-hardcoded.yml

@@ -0,0 +1,158 @@
+id: runner-environment-058
+title: "macOS 26 Homebrew LLVM Jumps 18 → 20 — Hardcoded llvm@18 Paths Fail"
+category: runner-environment
+severity: error
+tags:
+  - macos-26
+  - macos-latest
+  - llvm
+  - clang
+  - homebrew
+  - runner-image
+  - breaking-change
+  - cpp
+  - cmake
+patterns:
+  - regex: "no such file or directory.*homebrew.*opt.*llvm@(17|18)/bin"
+    flags: "i"
+  - regex: "clang(\\+\\+)?-(17|18).*command not found|No such file.*clang-(17|18)"
+    flags: "i"
+  - regex: "brew.*prefix.*llvm@(17|18).*Error.*no such keg"
+    flags: "i"
+  - regex: "Could not find.*LLVM (17|18).*Config\\.cmake"
+    flags: "i"
+  - regex: "llvm-config-(17|18).*not found"
+    flags: "i"
+error_messages:
+  - "zsh: no such file or directory: /opt/homebrew/opt/llvm@18/bin/clang++"
+  - "Error: clang-18: command not found"
+  - "Error: No such keg: /opt/homebrew/Cellar/llvm@18"
+  - "CMake Error at /opt/homebrew/lib/cmake/llvm/LLVMConfig.cmake: LLVM 18.1 required but 20.1 found"
+  - "llvm-config-18: not found"
+root_cause: |
+  When the `macos-latest` label migrated to macOS 26 Tahoe (beginning June 15, 2026),
+  the Homebrew-installed LLVM major version changed from **18.1.8** (on macOS 15) to
+  **20.1.8** (on macOS 26). This is a two-major-version jump that silently breaks any
+  workflow that hardcodes LLVM version numbers in paths, environment variables, or
+  CMake configuration.
+
+  **Affected patterns:**
+  - Shell scripts using `$(brew --prefix llvm@18)/bin/clang++` — the `llvm@18` keg no
+    longer exists on macOS 26; Homebrew returns "Error: No such keg"
+  - Workflows setting `CC=clang-18` or `CXX=clang++-18` — these binaries aren't
+    installed; the available binaries are `clang-20` and `clang++-20`
+  - CMake `find_package(LLVM 18 REQUIRED)` — succeeds on macOS 15 because Homebrew
+    LLVM 18 is present; fails on macOS 26 because only LLVM 20 is available
+  - `llvm-config-18 --version` in build scripts — the versioned binary doesn't exist
+  - `pkg-config --libs llvm-18` — the pkg-config file for llvm-18 is absent
+
+  **macOS 26 image ships with:**
+  - `llvm` formula → installs LLVM 20.x (unversioned `llvm` formula always tracks latest)
+  - `llvm@20` → available for explicit `brew install llvm@20`
+  - No `llvm@18` keg in the default image
+
+  Note: Workflows using the *unversioned* `llvm` or `clang` commands (e.g., `CC=clang`,
+  `$(brew --prefix llvm)/bin/clang++`) are NOT affected — they pick up the default
+  LLVM version on each image automatically.
+
+  Source: runner-images#14167 release diff table (Clang/LLVM 18.1.8 → 20.1.8);
+  community migration example: POCO C++ Libraries commit ff8174d (April 2026).
+fix: |
+  Replace all hardcoded `llvm@18` / `clang-18` references with either the unversioned
+  `llvm` formula path or the explicit `llvm@20` path on macOS 26.
+
+  **Option 1 — Use the unversioned Homebrew prefix (recommended):**
+  Replace `$(brew --prefix llvm@18)` with `$(brew --prefix llvm)` — this always resolves
+  to the current default LLVM, making the workflow future-proof.
+
+  **Option 2 — Explicit llvm@20 for reproducibility:**
+  Install `llvm@20` explicitly and reference it by version. This avoids future surprises
+  when `llvm` bumps to 21+.
+
+  **Option 3 — Pin to macos-15 temporarily:**
+  If the migration is not immediately feasible, pin to `macos-15` while updating your
+  build system to use the unversioned LLVM path.
+
+  **For CMake projects:** Remove the version constraint from `find_package(LLVM X REQUIRED)`
+  or use `find_package(LLVM REQUIRED)` and check the found version at configure time.
+fix_code:
+  - language: yaml
+    label: "Use unversioned llvm prefix — works across all macOS runner versions"
+    code: |
+      jobs:
+        build:
+          runs-on: macos-latest
+          steps:
+            - uses: actions/checkout@v4
+
+            - name: Install LLVM
+              run: brew install llvm  # installs current default (llvm@20 on macOS 26)
+
+            - name: Build
+              run: |
+                # Use unversioned prefix — future-proof across LLVM major bumps
+                LLVM_PREFIX=$(brew --prefix llvm)
+                export CC="$LLVM_PREFIX/bin/clang"
+                export CXX="$LLVM_PREFIX/bin/clang++"
+                export LDFLAGS="-L$LLVM_PREFIX/lib"
+                export CPPFLAGS="-I$LLVM_PREFIX/include"
+                make -j$(sysctl -n hw.logicalcpu)
+  - language: yaml
+    label: "Explicit llvm@20 for reproducible macOS 26 builds"
+    code: |
+      jobs:
+        build:
+          runs-on: macos-latest  # macOS 26
+          steps:
+            - uses: actions/checkout@v4
+
+            - name: Install LLVM 20
+              run: brew install llvm@20
+
+            - name: Configure and build
+              run: |
+                export CC="$(brew --prefix llvm@20)/bin/clang"
+                export CXX="$(brew --prefix llvm@20)/bin/clang++"
+                cmake -B build \
+                  -DCMAKE_C_COMPILER="$CC" \
+                  -DCMAKE_CXX_COMPILER="$CXX" \
+                  -DLLVM_DIR="$(brew --prefix llvm@20)/lib/cmake/llvm"
+                cmake --build build --parallel
+  - language: yaml
+    label: "CMake: remove version constraint from find_package(LLVM)"
+    code: |
+      # CMakeLists.txt — before
+      find_package(LLVM 18 REQUIRED CONFIG)
+
+      # CMakeLists.txt — after (accepts any version)
+      find_package(LLVM REQUIRED CONFIG)
+      message(STATUS "Found LLVM ${LLVM_PACKAGE_VERSION}")
+      # Optionally enforce a minimum version:
+      if(LLVM_VERSION_MAJOR LESS 18)
+        message(FATAL_ERROR "LLVM >= 18 required, got ${LLVM_PACKAGE_VERSION}")
+      endif()
+  - language: yaml
+    label: "Pin to macos-15 as temporary rollback while migrating"
+    code: |
+      jobs:
+        build:
+          # Temporary: macOS 15 still has llvm@18 via Homebrew
+          # TODO: migrate to unversioned llvm and switch back to macos-latest
+          runs-on: macos-15
+          steps:
+            - uses: actions/checkout@v4
+prevention:
+  - "Never hardcode LLVM version numbers in Homebrew prefix paths. Use `$(brew --prefix llvm)` for the current default or `$(brew --prefix llvm@XX)` with an explicit install step for reproducibility."
+  - "In CMakeLists.txt, use `find_package(LLVM REQUIRED CONFIG)` without a version constraint, and validate the found version at configure time instead."
+  - "Test your macOS CI against `macos-26` (or `macos-latest` after it transitions) before the migration completes — use a matrix build to run both images in parallel."
+  - "Audit all workflow files for hardcoded `clang-XX`, `llvm@XX`, or `llvm-config-XX` strings when macOS runner images announce major tool version changes."
+  - "Subscribe to runner-images releases to monitor Homebrew LLVM version changes in the release diff tables."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/14167"
+    label: "runner-images#14167: macos-latest will use macos-26 in June 2026 (diff table shows LLVM 18 → 20)"
+  - url: "https://github.com/actions/runner-images/blob/main/images/macos/macos-26-arm64-Readme.md"
+    label: "macOS 26 arm64 image README — full software list including LLVM version"
+  - url: "https://docs.brew.sh/Versions"
+    label: "Homebrew Docs: Versioned formulae (llvm@18, llvm@20, etc.)"
+  - url: "https://cmake.org/cmake/help/latest/command/find_package.html"
+    label: "CMake find_package documentation"

package/errors/runner-environment/node24-action-self-hosted-runner-too-old.yml

@@ -0,0 +1,93 @@
+id: runner-environment-053
+title: "Node 24 Action Fails on Self-Hosted Runner — 'using: node24 is not supported'"
+category: runner-environment
+severity: error
+tags:
+  - node24
+  - self-hosted-runner
+  - runner-version
+  - node-runtime
+  - actions-checkout
+  - actions-cache
+patterns:
+  - regex: "'using: node24' is not supported"
+    flags: "i"
+  - regex: "Parameter.*using.*node24.*is not supported"
+    flags: "i"
+  - regex: "node24.*not supported.*use.*node12.*node16.*node20"
+    flags: "i"
+  - regex: "This version of the Actions runner is too old to run node24"
+    flags: "i"
+error_messages:
+  - "Specified argument was out of the range of valid values. (Parameter ''using: node24' is not supported, use 'docker', 'node12', 'node16' or 'node20' instead.')"
+  - "'using: node24' is not supported, use 'docker', 'node12', 'node16' or 'node20' instead."
+root_cause: |
+  GitHub Actions runner v2.327.1 (released July 25, 2025) was the first version to add
+  support for the `node24` runtime. Actions that bumped their major version to run on
+  Node.js 24 (including `actions/checkout@v5`, `actions/cache@v5`,
+  `actions/upload-artifact@v6`, and `actions/setup-node@v5`) specify `using: node24` in
+  their `action.yml`. When one of these actions runs on a self-hosted runner older than
+  v2.327.1, the runner's `ActionManifestManager` throws a `System.ArgumentOutOfRangeException`
+  because it does not recognise `node24` as a valid runtime identifier — it only knows
+  `docker`, `node12`, `node16`, and `node20`.
+
+  Common scenarios:
+  - Bumping a pinned `actions/checkout@v4` → `actions/checkout@v5` without first updating
+    the self-hosted runner.
+  - Relying on automatic runner self-update: runners sometimes auto-update the agent binary
+    but the worker process still runs under the old version, causing a mismatch
+    (actions/runner#4064).
+  - Using Dependabot or Renovate to auto-bump action versions across a repo.
+fix: |
+  Update all self-hosted runners to version 2.327.1 or later before upgrading any action
+  to a version that requires `node24`. Steps:
+
+  1. Download and install the latest runner from:
+     https://github.com/actions/runner/releases/latest
+  2. Verify the version with: `./run.sh --version` (Linux/macOS) or `.\run.cmd --version`
+     (Windows).
+  3. If automatic self-update is enabled but stuck, stop the runner service, delete the
+     cached `_work/_update` directory, and restart — or manually install the new version.
+  4. For containerised runners (ARC, summerwind/actions-runner-dind), update the base image
+     tag to a version that ships runner ≥ 2.327.1.
+
+  If you cannot update the runner immediately, pin the actions back to the last v4/v5
+  compatible release and schedule the runner upgrade.
+fix_code:
+  - language: yaml
+    label: "Pin to node24-compatible action versions — requires runner ≥ 2.327.1"
+    code: |
+      steps:
+        - uses: actions/checkout@v5         # node24 — runner must be ≥ 2.327.1
+        - uses: actions/cache@v5            # node24 — runner must be ≥ 2.327.1
+        - uses: actions/upload-artifact@v6  # node24 — runner must be ≥ 2.327.1
+        - uses: actions/setup-node@v5       # node24 — runner must be ≥ 2.327.1
+  - language: yaml
+    label: "Temporary pin to node20 versions while runner is being updated"
+    code: |
+      steps:
+        - uses: actions/checkout@v4         # still node20, compatible with older runners
+        - uses: actions/cache@v4            # still node20
+        - uses: actions/upload-artifact@v4  # still node20
+        - uses: actions/setup-node@v4       # still node20
+  - language: yaml
+    label: "Verify runner version in workflow (diagnostic)"
+    code: |
+      steps:
+        - name: Print runner version
+          run: echo "Runner version ${{ runner.version }}"
+        # runner.version must be >= 2.327.1 for node24 actions
+prevention:
+  - "Before bumping any action to a node24 major version, check all self-hosted runner versions and update them first."
+  - "Add a minimum runner version check step or GitHub Actions required runner version policy for your organisation."
+  - "Subscribe to runner-images and actions/runner release announcements to learn about node runtime changes in advance."
+  - "For Dependabot/Renovate auto-bumps, add a CI gate that blocks merging action version upgrades until runner compatibility is confirmed."
+docs:
+  - url: "https://github.com/actions/checkout/issues/2240"
+    label: "actions/checkout#2240 — Breaking change with v5: 'using: node24 is not supported' (27 reactions)"
+  - url: "https://github.com/actions/runner/releases/tag/v2.327.1"
+    label: "actions/runner v2.327.1 — First release with Node.js 24 support"
+  - url: "https://github.com/actions/runner/issues/4064"
+    label: "actions/runner#4064 — Auto-update doesn't take node20 → node24 into account, cascading failures"
+  - url: "https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/"
+    label: "GitHub Changelog — Deprecation of Node 20 on GitHub Actions runners"

package/errors/runner-environment/python39-removed-runner-images.yml

@@ -0,0 +1,97 @@
+id: runner-environment-054
+title: "Python 3.9 Removed from Runner Images — Version Not Found in Local Cache"
+category: runner-environment
+severity: error
+tags:
+  - python
+  - python-39
+  - runner-images
+  - toolcache
+  - setup-python
+  - eol
+patterns:
+  - regex: "Version '3\\.9[^']*' was not found in the local cache"
+    flags: "i"
+  - regex: "python.*3\\.9.*not found.*cache|not found.*python.*3\\.9"
+    flags: "i"
+  - regex: "Unable to find python version.*3\\.9"
+    flags: "i"
+  - regex: "Couldn't find a version that satisfies.*python.*3\\.9"
+    flags: "i"
+error_messages:
+  - "Version '3.9.x' was not found in the local cache"
+  - "Unable to find the requested Python version (3.9.x) in the local tool cache"
+  - "Error: Version 3.9 with arch x64 not found"
+root_cause: |
+  Python 3.9 reached end-of-life on October 5, 2025. Starting January 12, 2026, GitHub
+  removed the pre-cached Python 3.9 toolchain from all runner images (ubuntu-22.04,
+  ubuntu-24.04, macOS-14, macOS-15, Windows Server 2022/2025). Additionally, on
+  Windows-based images Python 3.12 replaced 3.9 as the default version
+  (runner-images#13468).
+
+  Workflows are affected when:
+  1. `actions/setup-python` is used with `python-version: '3.9'` without a fallback —
+     the action tries the local toolcache first and fails when the pre-cached entry is gone.
+  2. A workflow assumes the system `python` or `python3` binary is 3.9 on Windows
+     (where it was the previous default).
+  3. A workflow calls `python3.9` directly (e.g. `python3.9 manage.py …`) without
+     installing it first.
+fix: |
+  Option A — Install Python 3.9 at runtime via actions/setup-python (recommended):
+    Add `actions/setup-python` with a specific version. The action will download and
+    install Python 3.9 from the GitHub-managed toolcache CDN even though it is no longer
+    pre-cached on the image.
+
+  Option B — Migrate to a supported Python version:
+    Python 3.9 is EOL. Migrate to Python 3.11, 3.12, or 3.13 to benefit from active
+    security patches. Test your dependency set against the newer version.
+
+  Option C — Pin a newer default for Windows:
+    If you relied on the system default `python` being 3.9 on Windows, add an explicit
+    `actions/setup-python` step to pin the exact version you need.
+fix_code:
+  - language: yaml
+    label: "Install Python 3.9 at runtime (works despite toolcache removal)"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+        - uses: actions/setup-python@v5
+          with:
+            python-version: '3.9'   # downloaded from CDN — no longer pre-cached
+        - run: python --version
+  - language: yaml
+    label: "Migrate to Python 3.12 (recommended — actively supported)"
+    code: |
+      steps:
+        - uses: actions/checkout@v4
+        - uses: actions/setup-python@v5
+          with:
+            python-version: '3.12'
+        - run: pip install -r requirements.txt
+  - language: yaml
+    label: "Matrix across multiple Python versions"
+    code: |
+      jobs:
+        test:
+          strategy:
+            matrix:
+              python-version: ['3.11', '3.12', '3.13']
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - uses: actions/setup-python@v5
+              with:
+                python-version: ${{ matrix.python-version }}
+            - run: pip install -r requirements.txt && pytest
+prevention:
+  - "Always use `actions/setup-python` with an explicit `python-version` — never rely on the system pre-cached version."
+  - "Subscribe to runner-images EOL announcements to plan Python version migrations before removal dates."
+  - "Add Python version to `.python-version` or `pyproject.toml` and let `actions/setup-python` read it via `python-version-file`."
+  - "Avoid hard-coding EOL Python versions; use `~3.12` or `>=3.11` range specifiers where the toolchain supports them."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/13468"
+    label: "runner-images#13468 — Python 3.9 removed; Python 3.12 becomes default on Windows (Jan 12, 2026)"
+  - url: "https://github.com/actions/setup-python"
+    label: "actions/setup-python — installs any Python version at runtime from CDN"
+  - url: "https://devguide.python.org/versions/"
+    label: "Python Developer's Guide — supported versions and EOL dates"

package/errors/silent-failures/setup-python-pip-cache-macos26-annotation.yml

@@ -0,0 +1,110 @@
+id: silent-failures-027
+title: "actions/setup-python pip Cache on macOS 26 Emits False Error Annotation"
+category: silent-failures
+severity: warning
+tags:
+  - setup-python
+  - pip
+  - cache
+  - macos-26
+  - annotation
+  - false-positive
+  - python310
+patterns:
+  - regex: "ERROR.*WARNING.*Cache entry deserialization failed.*entry ignored"
+    flags: "i"
+  - regex: "Cache entry deserialization failed.*entry ignored"
+    flags: "i"
+  - regex: "Error: WARNING:.*cache.*deserialization"
+    flags: "i"
+error_messages:
+  - "Error: WARNING: Cache entry deserialization failed, entry ignored."
+  - "WARNING: Cache entry deserialization failed, entry ignored"
+root_cause: |
+  When using `actions/setup-python@v6` with `cache: 'pip'` and an older Python version
+  (notably Python 3.10) on `macos-26` runners, the action succeeds but emits a false
+  error annotation in the GitHub Actions UI, turning the job "yellow" or showing a red
+  annotation badge.
+
+  **What happens:**
+  1. `setup-python@v6` restores the pip cache from a previous run.
+  2. pip on the current macOS 26 runner (with a newer pip version) encounters a pip
+     wheel cache entry written by an older pip version using a different serialization
+     format or metadata schema.
+  3. pip emits: `WARNING: Cache entry deserialization failed, entry ignored` to stderr.
+  4. The GitHub Actions runner's annotation parser sees the word "Error" at the start
+     of the output (because the line is rendered as `Error: WARNING: ...` in GitHub's
+     log viewer) and creates an annotation treating it as a job error.
+  5. The job itself succeeds — the dependency install works fine — but the annotation
+     makes the job appear failed or degraded in the GitHub UI.
+
+  **Platform specificity:** This is reproducible specifically on `macos-26` (ARM), not
+  on Ubuntu, Windows, or `macos-15`. The combination of macOS 26's newer system Python
+  environment and the `macos-26` Arm64 pip wheel cache schema causes the deserialization
+  mismatch.
+
+  Source: actions/setup-python#1317 (open bug, May 20 2026 — under investigation by
+  actions/setup-python maintainers).
+fix: |
+  **Option 1 — Clear the stale pip cache (immediate fix):**
+  Purge the GitHub Actions cache for the affected key via the UI or API, forcing a cache
+  rebuild on the next run. The fresh cache will be written by the current pip version on
+  macOS 26 and will deserialize cleanly on subsequent runs.
+
+  **Option 2 — Disable pip caching for macOS 26 until resolved:**
+  Use a conditional `cache` input based on the runner OS:
+
+  **Option 3 — Pin to a Python version not affected:**
+  Python 3.12 and 3.14 have not been reported to exhibit this issue on macOS 26 — only
+  3.10 is confirmed. Test whether upgrading your target Python version resolves the annotation.
+
+  **Option 4 — Wait for the upstream fix:**
+  This is an open bug in `actions/setup-python` being investigated (issue #1317). A fix
+  in `setup-python@v6` will resolve this without workflow changes.
+fix_code:
+  - language: yaml
+    label: "Disable pip cache on macOS to avoid false error annotation"
+    code: |
+      - name: Set up Python
+        uses: actions/setup-python@v6
+        with:
+          python-version: "3.10"
+          # Disable cache on macOS 26 until setup-python#1317 is resolved
+          cache: ${{ runner.os != 'macOS' && 'pip' || '' }}
+  - language: yaml
+    label: "Clear the stale cache via GitHub API (one-time fix)"
+    code: |
+      # Delete the stale pip cache key via gh CLI (run once)
+      gh cache list --repo owner/repo --key 'setup-python-*macos-26*'
+      gh cache delete <CACHE_ID> --repo owner/repo
+      # Or delete all pip caches for macOS 26:
+      gh cache list --repo owner/repo --json id,key --jq \
+        '.[] | select(.key | test("macos-26")) | .id' \
+        | xargs -I{} gh cache delete {} --repo owner/repo
+  - language: yaml
+    label: "Matrix build: cache only on platforms where it works cleanly"
+    code: |
+      jobs:
+        test:
+          strategy:
+            matrix:
+              os: [ubuntu-latest, windows-latest, macos-26]
+          runs-on: ${{ matrix.os }}
+          steps:
+            - uses: actions/setup-python@v6
+              with:
+                python-version: "3.10"
+                # macOS 26 pip cache has deserialization issue (setup-python#1317)
+                cache: ${{ matrix.os != 'macos-26' && 'pip' || '' }}
+prevention:
+  - "Watch for `actions/setup-python` releases fixing issue #1317 — once resolved, re-enable caching on macOS 26."
+  - "When a new macOS runner label becomes `macos-latest`, clear pip caches from the old image version to avoid deserialization mismatches on the first run."
+  - "Test your workflows on new macOS runner labels before `macos-latest` transitions — catch cache format incompatibilities before they affect production CI."
+  - "Use GitHub's cache eviction API or `actions/cache@v4` with `fail-on-cache-miss: false` to gracefully handle deserialization failures."
+docs:
+  - url: "https://github.com/actions/setup-python/issues/1317"
+    label: "actions/setup-python#1317: Cache entry deserialization failed on macOS 26 (open bug)"
+  - url: "https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows#managing-caches"
+    label: "GitHub Docs: Managing GitHub Actions caches"
+  - url: "https://github.com/actions/setup-python"
+    label: "actions/setup-python — official action repository"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@htekdev/actions-debugger",
-  "version": "1.0.20",
+  "version": "1.0.22",
   "description": "65+ real GitHub Actions errors, queryable by agents. MCP server + Copilot skills + error database.",
   "type": "module",
   "main": "./dist/index.js",