@htekdev/actions-debugger 1.0.125 → 1.0.126

package/errors/concurrency-timing/concurrency-timing-059.yml

@@ -0,0 +1,146 @@
+id: concurrency-timing-059
+title: 'Skipped downstream job satisfies required status check — PR merges despite upstream job failure'
+category: concurrency-timing
+severity: silent-failure
+tags:
+  - needs
+  - skipped
+  - required-status-check
+  - branch-protection
+  - dependency
+  - silent-merge
+  - job-conclusion
+patterns:
+  - regex: 'This job was skipped'
+    flags: 'i'
+  - regex: 'Result: skipped'
+    flags: 'i'
+  - regex: 'needs\.[a-zA-Z0-9_-]+\.result.*skipped'
+    flags: 'i'
+error_messages:
+  - "This job was skipped."
+  - "Skipping this job because a previous job in the chain was skipped or failed."
+root_cause: |
+  GitHub Actions marks a downstream job as `skipped` (not `failure`) when an upstream
+  `needs:` dependency fails or is cancelled and the downstream job has no explicit `if:`
+  condition to handle that state.
+
+  Since April 2023, GitHub's branch protection rules treat a `skipped` check conclusion
+  as **passing** — equivalent to `success` — to support the common "aggregator job"
+  pattern. This means:
+
+  1. `build` job fails.
+  2. `test-results` job (which `needs: [build]`) is marked `skipped`.
+  3. Branch protection rule requires `test-results` to pass.
+  4. GitHub sees conclusion = `skipped` → treats it as satisfied → merge is allowed.
+
+  The PR can be merged even though the `build` step failed. There is no warning or
+  error in the UI — the required check shows a green checkmark (or neutral status)
+  rather than a red blocking indicator.
+
+  This behavior is distinct from:
+  - `cancel-in-progress` cancelling a required check (conclusion = `cancelled`, which
+    blocks merging — a separate issue).
+  - Path-filter causing a workflow to never run (check stays "Expected" / pending).
+  - The general skipped-needs cascade (which documents that downstream jobs skip, but
+    not the branch protection bypass consequence).
+fix: |
+  Add an explicit **catch-all aggregator job** that runs whenever any dependency failed
+  or was cancelled, and exits with a non-zero code:
+
+  ```yaml
+  ci-gate:
+    if: ${{ always() && (contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled')) }}
+    needs: [build, test, lint]
+    runs-on: ubuntu-latest
+    steps:
+      - name: Fail — one or more required jobs did not succeed
+        run: |
+          echo "Required jobs: ${{ toJSON(needs.*.result) }}"
+          exit 1
+  ```
+
+  Set `ci-gate` as the sole required status check in branch protection. This aggregator
+  job only runs (and fails) when something upstream fails. When all upstream jobs
+  succeed, `ci-gate` is `skipped` → satisfies the required check. When any upstream
+  fails, `ci-gate` runs and explicitly fails → blocks the merge.
+
+  Alternatively, use the pattern that always runs the aggregator:
+
+  ```yaml
+  ci-gate:
+    if: always()
+    needs: [build, test, lint]
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check all required jobs passed
+        run: |
+          results='${{ toJSON(needs.*.result) }}'
+          if echo "$results" | grep -qE '"failure"|"cancelled"'; then
+            echo "One or more jobs failed: $results"
+            exit 1
+          fi
+          echo "All required jobs passed."
+  ```
+fix_code:
+  - language: yaml
+    label: 'Broken — downstream skipped check silently satisfies branch protection'
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          steps:
+            - run: ./build.sh   # Fails
+
+        test-results:
+          needs: [build]        # Skipped when build fails
+          runs-on: ubuntu-latest
+          # ⚠ No if: condition — job is skipped when build fails
+          # ⚠ Branch protection requires test-results to "pass"
+          # ⚠ skipped = passing in GitHub's branch protection evaluation
+          steps:
+            - run: ./test.sh
+
+  - language: yaml
+    label: 'Fixed — explicit catch-all aggregator job that fails on upstream failure'
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          steps:
+            - run: ./build.sh
+
+        test:
+          runs-on: ubuntu-latest
+          steps:
+            - run: ./test.sh
+
+        ci-gate:
+          if: always()
+          needs: [build, test]
+          runs-on: ubuntu-latest
+          steps:
+            - name: All required jobs must succeed
+              run: |
+                results='${{ toJSON(needs.*.result) }}'
+                if echo "$results" | grep -qE '"failure"|"cancelled"'; then
+                  echo "Pipeline failed: $results"
+                  exit 1
+                fi
+                echo "All jobs passed: $results"
+
+      # In branch protection: require "ci-gate" — not "build" or "test" individually
+
+prevention:
+  - 'Use a single aggregator job (`ci-gate`) as the required status check instead of individual job names.'
+  - 'Always include `if: always()` on the aggregator and explicitly check `needs.*.result` for failure/cancelled.'
+  - 'Do NOT rely on `needs:` skipping to propagate failures to branch protection — skipped is treated as passing.'
+  - 'After changing which jobs are required status checks, verify by letting a build fail and confirm the PR is blocked.'
+  - 'actionlint does not detect this misconfiguration — manual testing is required.'
+docs:
+  - url: 'https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/troubleshooting-required-status-checks'
+    label: 'GitHub Docs: Troubleshooting required status checks'
+  - url: 'https://github.com/actions/runner/issues/2566'
+    label: 'actions/runner#2566: Skipped jobs satisfy required checks (many reactions)'
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/using-conditions-to-control-job-execution'
+    label: 'GitHub Docs: Using conditions to control job execution'

package/errors/concurrency-timing/concurrency-timing-060.yml

@@ -0,0 +1,144 @@
+id: concurrency-timing-060
+title: 'cancel-in-progress: false still silently drops older pending run when third concurrent dispatch arrives — GitHub enforces a 1-active + 1-pending hard limit per concurrency group'
+category: concurrency-timing
+severity: silent-failure
+tags:
+  - concurrency
+  - cancel-in-progress
+  - pending
+  - silent-cancel
+  - dispatch
+  - queue
+  - lost-run
+patterns:
+  - regex: 'This run was cancelled'
+    flags: 'i'
+  - regex: 'cancel-in-progress:\s*false'
+    flags: 'i'
+  - regex: 'Run was cancelled'
+    flags: 'i'
+error_messages:
+  - "This run was cancelled."
+  - "Run was cancelled."
+root_cause: |
+  Setting `cancel-in-progress: false` in a concurrency group does NOT mean "queue all
+  runs indefinitely." It means "do not cancel the currently *in-progress* run."
+
+  GitHub Actions enforces a hard internal limit of **1 in-progress + 1 pending** run
+  per concurrency group (when using the default or `cancel-in-progress: false`).
+  When a third concurrent run arrives:
+
+  1. Run A is **in-progress** (held in slot 1).
+  2. Run B is **pending** (held in slot 2, waiting for Run A to finish).
+  3. Run C arrives → GitHub silently cancels Run B to free slot 2, then queues Run C.
+
+  The net effect: Run B is lost. Run C is now pending and will eventually execute.
+  With `cancel-in-progress: false`, *only Run A is protected* from cancellation — not
+  Run B. The arriving run always displaces the previously pending one.
+
+  This surprises developers who read `cancel-in-progress: false` as "let all runs
+  queue and execute in order." The actual semantics are: "don't kill the in-flight
+  run, but still replace any queued-but-not-yet-running run."
+
+  There is no log entry showing Run B was cancelled by Run C's arrival; the cancellation
+  shows as "This run was cancelled" with no attribution.
+
+  To allow more than 1 pending run, use `queue: max` (up to 100 pending slots) — but
+  note that `queue: max` and `cancel-in-progress: true` cannot be combined.
+fix: |
+  Choose the concurrency strategy that matches your desired behavior:
+
+  **Option 1 — Allow up to 100 queued runs (strict ordering, no drops):**
+  Use `queue: max`. Every run is preserved and executes in arrival order. The 101st
+  concurrent run silently cancels the oldest pending run (see concurrency-timing-058
+  for the queue:max overflow edge case).
+
+  **Option 2 — Cancel stale runs, always run the latest (most common for CI):**
+  Use `cancel-in-progress: true`. Stale pending runs are cancelled; only the most
+  recent push/dispatch runs.
+
+  **Option 3 — Fine-grained concurrency keys to prevent grouping:**
+  Include `github.sha` or `github.run_id` in the group key so each run gets its own
+  isolated slot and nothing is ever cancelled or queued against another run.
+
+  **Option 4 — Accept the default behavior:**
+  Understand that `cancel-in-progress: false` means 1-active + 1-pending, and design
+  your pipeline around this. For example, if you need every commit tested, use
+  `cancel-in-progress: true` so you always test the latest commit, or `queue: max`
+  if you need every commit tested in order.
+fix_code:
+  - language: yaml
+    label: 'Broken — cancel-in-progress: false does NOT queue all runs; 3rd run drops 2nd'
+    code: |
+      on: push
+
+      concurrency:
+        group: deploy-${{ github.ref }}
+        cancel-in-progress: false   # ❌ Only protects the in-progress run (slot 1)
+                                    # ❌ Slot 2 (pending) is still replaced when a 3rd run arrives
+
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          steps:
+            - run: ./deploy.sh
+
+  - language: yaml
+    label: 'Fixed — use queue: max to preserve all pending runs (up to 100)'
+    code: |
+      on: push
+
+      concurrency:
+        group: deploy-${{ github.ref }}
+        queue: max    # ✅ Up to 100 pending runs preserved, executed in order
+                      # ✅ No run is silently dropped until the 101st arrives
+
+      jobs:
+        deploy:
+          runs-on: ubuntu-latest
+          steps:
+            - run: ./deploy.sh
+
+  - language: yaml
+    label: 'Alternative — cancel stale runs, keep only the latest (typical CI pattern)'
+    code: |
+      on: push
+
+      concurrency:
+        group: ${{ github.workflow }}-${{ github.ref }}
+        cancel-in-progress: true   # ✅ Latest commit always runs; stale runs cancelled
+
+      jobs:
+        ci:
+          runs-on: ubuntu-latest
+          steps:
+            - run: ./test.sh
+
+  - language: yaml
+    label: 'Alternative — unique key per run (no cancellation, no queueing)'
+    code: |
+      on: push
+
+      concurrency:
+        group: ${{ github.workflow }}-${{ github.run_id }}   # ✅ Each run is isolated
+        cancel-in-progress: false
+
+      jobs:
+        ci:
+          runs-on: ubuntu-latest
+          steps:
+            - run: ./test.sh
+
+prevention:
+  - 'Read `cancel-in-progress: false` as "protect the running job, not all pending jobs."'
+  - 'Use `queue: max` when you need every dispatched run to eventually execute.'
+  - '`queue: max` and `cancel-in-progress: true` cannot be combined — validation error.'
+  - 'Include `github.sha` or `github.run_id` in the group key to give each run its own isolated slot.'
+  - 'Monitor the Actions tab for unexplained cancellations after rapid pushes to confirm you are hitting the 1-pending limit.'
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs'
+    label: 'GitHub Docs: Control the concurrency of workflows and jobs'
+  - url: 'https://github.com/orgs/community/discussions/5435'
+    label: 'GitHub Community #5435: cancel-in-progress: false still cancels pending runs'
+  - url: 'https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#concurrency'
+    label: 'GitHub Docs: Workflow syntax — concurrency'

package/errors/known-unsolved/known-unsolved-073.yml

@@ -0,0 +1,172 @@
+id: known-unsolved-073
+title: '`timeout-minutes:` does not accept expressions — must be a literal integer; variables, inputs, and secrets are unsupported'
+category: known-unsolved
+severity: limitation
+tags:
+  - timeout-minutes
+  - expressions
+  - limitation
+  - no-dynamic-value
+  - job-timeout
+  - step-timeout
+  - vars-context
+patterns:
+  - regex: 'timeout-minutes:\s*\$\{\{'
+    flags: 'i'
+  - regex: 'timeout-minutes.*vars\.|timeout-minutes.*inputs\.|timeout-minutes.*env\.'
+    flags: 'i'
+  - regex: 'Unexpected value.*timeout-minutes|timeout-minutes.*invalid'
+    flags: 'i'
+error_messages:
+  - "The workflow is not valid. .github/workflows/ci.yml (Line: N, Col: M): Unexpected value 'true'"
+  - "timeout-minutes: unexpected value"
+  - "Expected Integer, String"
+root_cause: |
+  The `timeout-minutes:` field at both the **job level** and the **step level** only
+  accepts a **literal integer** (e.g., `30`, `120`). GitHub Actions does not evaluate
+  expressions (`${{ }}`) in this field.
+
+  Attempting to use any of the following will either produce a YAML validation error
+  or silently fall back to the default timeout (6 hours for jobs, unlimited for steps):
+
+  - `timeout-minutes: ${{ vars.JOB_TIMEOUT }}`      — variables context
+  - `timeout-minutes: ${{ inputs.timeout }}`         — inputs context
+  - `timeout-minutes: ${{ env.TIMEOUT_MINUTES }}`    — env context
+  - `timeout-minutes: ${{ 30 * 2 }}`                 — arithmetic expression
+  - `timeout-minutes: ${{ matrix.timeout }}`         — matrix value
+
+  This is a long-standing feature request (actions/runner#1242, opened 2021, 500+
+  reactions) with no official resolution as of June 2026. GitHub's position is that
+  expression support in `timeout-minutes:` is not currently planned.
+
+  actionlint (>=1.6.x) correctly flags `timeout-minutes: ${{ ... }}` as a type error:
+  "type of expression at 'timeout-minutes' must be number but found string type."
+  However, some older actionlint versions or CI linting setups may not catch this,
+  allowing the invalid value to reach production where it silently uses the default.
+
+  Common motivation for wanting dynamic timeouts:
+  - Different environments (staging vs production) need different timeouts.
+  - A reusable workflow caller wants to pass a timeout as an input.
+  - Matrix jobs with different test suites need proportional timeouts.
+  - Organizational policies want to set timeouts via repository variables.
+fix: |
+  There is no native fix — expressions in `timeout-minutes:` are not supported.
+
+  **Workaround 1 — Hardcode multiple job variants with `if:` conditions:**
+  Create separate job definitions for each timeout scenario, each with a hardcoded
+  `timeout-minutes:` and an `if:` condition that selects the appropriate one based
+  on the context. This is verbose but fully supported.
+
+  **Workaround 2 — Use a wrapper script with a timeout command:**
+  Instead of relying on job-level timeout, implement a timeout inside the step's run
+  script using the OS `timeout` command (Linux/macOS) or PowerShell's `Wait-Process`:
+  ```yaml
+  steps:
+    - name: Build with dynamic timeout
+      env:
+        BUILD_TIMEOUT: ${{ vars.BUILD_TIMEOUT_SECONDS || '1800' }}
+      run: timeout "$BUILD_TIMEOUT" ./build.sh
+  ```
+  This gives dynamic timeout behavior but does NOT release the runner immediately —
+  the job continues running (idle) after the script times out until the job-level
+  `timeout-minutes:` (hardcoded) fires.
+
+  **Workaround 3 — Hardcode a generous upper bound:**
+  Set `timeout-minutes:` to the maximum acceptable value for any scenario, and rely
+  on internal script logic to exit early when needed. Ensures the runner is eventually
+  released even in worst-case scenarios.
+
+  **Workaround 4 — For reusable workflows, hardcode per caller:**
+  If a reusable workflow needs caller-specified timeouts, duplicate the job definition
+  per timeout tier or create multiple reusable workflows with different timeouts.
+fix_code:
+  - language: yaml
+    label: 'Does NOT work — expression in timeout-minutes is not supported'
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          timeout-minutes: ${{ vars.JOB_TIMEOUT_MINUTES }}   # ❌ Expression not supported
+          steps:
+            - run: ./build.sh
+
+      # Also does NOT work:
+      jobs:
+        test:
+          runs-on: ubuntu-latest
+          timeout-minutes: ${{ inputs.timeout || 30 }}        # ❌ inputs not supported here
+          steps:
+            - run: ./test.sh
+
+  - language: yaml
+    label: 'Workaround — use OS timeout command inside step for dynamic behavior'
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-latest
+          timeout-minutes: 60    # ✅ Hardcoded upper bound (releases runner if script hangs)
+          steps:
+            - uses: actions/checkout@v4
+            - name: Build with dynamic timeout from variable
+              env:
+                # Variable in seconds: default 1800 (30 min), override via repo var
+                BUILD_TIMEOUT: ${{ vars.BUILD_TIMEOUT_SECONDS || '1800' }}
+              run: timeout "$BUILD_TIMEOUT" ./build.sh
+              # The job-level 60-minute timeout catches runaway cases
+
+  - language: yaml
+    label: 'Workaround — conditional job variants for different timeout requirements'
+    code: |
+      jobs:
+        build-short:
+          if: ${{ github.event_name == 'pull_request' }}
+          runs-on: ubuntu-latest
+          timeout-minutes: 15    # ✅ Short timeout for PR checks
+          steps:
+            - uses: actions/checkout@v4
+            - run: ./build.sh --quick
+
+        build-full:
+          if: ${{ github.ref == 'refs/heads/main' }}
+          runs-on: ubuntu-latest
+          timeout-minutes: 60    # ✅ Full timeout for main branch builds
+          steps:
+            - uses: actions/checkout@v4
+            - run: ./build.sh --full
+
+  - language: yaml
+    label: 'Reusable workflow workaround — hardcode tiers, expose as separate workflows'
+    code: |
+      # .github/workflows/ci-fast.yml — for PRs
+      on:
+        workflow_call:
+      jobs:
+        ci:
+          runs-on: ubuntu-latest
+          timeout-minutes: 15   # ✅ Fast tier
+          steps:
+            - run: ./ci.sh
+
+      # .github/workflows/ci-full.yml — for main branch
+      on:
+        workflow_call:
+      jobs:
+        ci:
+          runs-on: ubuntu-latest
+          timeout-minutes: 60   # ✅ Full tier
+          steps:
+            - run: ./ci.sh
+
+prevention:
+  - 'Accept that `timeout-minutes:` requires a literal integer — design your timeouts with hardcoded values from the start.'
+  - 'Use actionlint in CI to catch `timeout-minutes: ${{ ... }}` during PR review before it reaches production.'
+  - 'Set `timeout-minutes:` to a safe upper bound to ensure runners are eventually released even when scripts hang.'
+  - 'Use step-level `run: timeout N command` for dynamic per-step timeouts without changing job-level `timeout-minutes:`.'
+  - 'Upvote actions/runner#1242 — expression support in timeout-minutes is a high-demand feature request.'
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes'
+    label: 'GitHub Docs: Workflow syntax — jobs.<id>.timeout-minutes (literal integer only)'
+  - url: 'https://github.com/actions/runner/issues/1242'
+    label: 'actions/runner#1242: Support expressions in timeout-minutes (500+ reactions, open since 2021)'
+  - url: 'https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idstepstimeout-minutes'
+    label: 'GitHub Docs: Workflow syntax — jobs.<id>.steps[*].timeout-minutes'

package/errors/triggers/triggers-072.yml

@@ -0,0 +1,150 @@
+id: triggers-072
+title: 'Scheduled workflow silently disabled after 60 days of public repository inactivity — distinct from the fork schedule disabling rule'
+category: triggers
+severity: silent-failure
+tags:
+  - schedule
+  - cron
+  - disabled
+  - inactivity
+  - public-repo
+  - silent-disable
+  - 60-days
+patterns:
+  - regex: 'on:\s*\n\s+schedule:'
+    flags: 'im'
+  - regex: 'This workflow was disabled'
+    flags: 'i'
+  - regex: 'Workflow.*disabled.*inactiv'
+    flags: 'i'
+error_messages:
+  - "This workflow was disabled."
+  - "Scheduled workflows are disabled for repositories with no recent activity."
+root_cause: |
+  GitHub automatically disables scheduled (`on: schedule:`) workflows in **public
+  repositories** that have had no activity for more than **60 days**. "Activity"
+  includes pushes, pull requests, issue comments, or other events that generate
+  a repository event payload. Pure time-passing without any interaction does not
+  reset the timer.
+
+  The disabling happens silently:
+  - No email notification is sent to repository owners or workflow authors.
+  - No GitHub notification appears in the repository's notification feed.
+  - The scheduled run simply does not appear in the Actions run history.
+  - The workflow file is not changed — the `on: schedule:` trigger is still present
+    in the YAML, but the schedule is inactive in GitHub's internal scheduler.
+
+  The Actions tab will show the workflow listed but with a note that it has been
+  disabled. The **"Enable workflow"** button must be clicked manually to re-activate it.
+
+  This behavior is separate from the fork schedule-disabling rule (where ALL
+  scheduled workflows are disabled on forked repos regardless of activity). The
+  inactivity rule applies to non-fork public repositories.
+
+  Common scenarios:
+  - Maintenance scripts (e.g., weekly dependency updates, cleanup jobs) in repos
+    that receive no push activity between runs.
+  - Documentation or static-site repos where content is rarely updated but a nightly
+    build/deploy workflow is expected to run.
+  - Monitoring or alerting workflows in repos with no other CI triggers.
+  - Open-source libraries with stable codebases and monthly or quarterly releases.
+fix: |
+  **Immediate fix:** Navigate to the repository → Actions tab → find the disabled
+  workflow → click "Enable workflow."
+
+  **Prevent future silent disabling — Option 1 (Recommended): Add a dummy commit
+  or workflow_dispatch trigger:**
+  Add `workflow_dispatch:` to the workflow so it can be triggered manually and also
+  resets the inactivity timer. Then use `gh workflow run` or the UI to manually
+  trigger it if needed.
+
+  **Prevent future silent disabling — Option 2: Artificially keep the repo active:**
+  Add a companion workflow that runs on schedule and updates a file (e.g., a
+  `last-run.txt` with the current timestamp) via a commit. This creates repository
+  activity and resets the 60-day timer. Warning: this generates commit noise.
+
+  **Prevent future silent disabling — Option 3: Convert to a self-hosted or
+  external scheduler:**
+  Use an external cron service (e.g., a cron job in a cloud provider) to trigger
+  the workflow via `workflow_dispatch` or `repository_dispatch`. External triggers
+  count as activity and keep the workflow enabled.
+
+  **Long-term design:** For workflows that are truly meant to run on a schedule
+  without any other repo activity, always add `workflow_dispatch:` as a co-trigger.
+  This makes the workflow manually invocable AND provides a path to re-enable it if
+  it is ever silently disabled.
+fix_code:
+  - language: yaml
+    label: 'At-risk — schedule-only workflow in a low-activity public repo'
+    code: |
+      # ⚠ This workflow will be silently disabled after 60 days with no repo activity
+      name: Weekly Dependency Update
+
+      on:
+        schedule:
+          - cron: '0 9 * * 1'   # Every Monday at 09:00 UTC
+
+      jobs:
+        update:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - run: npm update && npm audit fix
+
+  - language: yaml
+    label: 'Fixed — add workflow_dispatch to keep the workflow manageable and prevent inactivity disable'
+    code: |
+      name: Weekly Dependency Update
+
+      on:
+        schedule:
+          - cron: '0 9 * * 1'   # Every Monday at 09:00 UTC
+        workflow_dispatch:       # ✅ Allows manual trigger; manual runs also reset the inactivity timer
+
+      jobs:
+        update:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - run: npm update && npm audit fix
+
+  - language: yaml
+    label: 'Alternative — heartbeat workflow that commits a timestamp to keep the repo active'
+    code: |
+      name: Activity Heartbeat (prevents schedule auto-disable)
+
+      on:
+        schedule:
+          - cron: '0 0 * * 0'   # Every Sunday midnight UTC — reset 60-day timer
+        workflow_dispatch:
+
+      permissions:
+        contents: write
+
+      jobs:
+        heartbeat:
+          runs-on: ubuntu-latest
+          steps:
+            - uses: actions/checkout@v4
+            - name: Update heartbeat timestamp
+              run: |
+                echo "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .github/heartbeat.txt
+                git config user.name 'github-actions[bot]'
+                git config user.email '41898282+github-actions[bot]@users.noreply.github.com'
+                git add .github/heartbeat.txt
+                git diff --staged --quiet || git commit -m 'chore: activity heartbeat [skip ci]'
+                git push
+
+prevention:
+  - 'Always add `workflow_dispatch:` alongside `on: schedule:` for any workflow that should run reliably in a low-activity repo.'
+  - 'Check the Actions tab after a period of low repository activity to verify scheduled workflows are still enabled.'
+  - 'The 60-day inactivity rule applies to non-fork public repositories — private repos are NOT subject to this rule.'
+  - 'This is distinct from the fork schedule-disabling rule: forks disable schedules immediately on fork creation, not after inactivity.'
+  - 'Set up a GitHub Actions alert or monitoring workflow that notifies you if expected scheduled runs stop appearing.'
+docs:
+  - url: 'https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule'
+    label: 'GitHub Docs: Events that trigger workflows — schedule (inactivity disable note)'
+  - url: 'https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow'
+    label: 'GitHub Docs: Disabling and enabling a workflow'
+  - url: 'https://github.com/orgs/community/discussions/134086'
+    label: 'GitHub Community #134086: Scheduled workflows not running — inactivity disable reports'

package/package.json

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