Standing alarm — one per breach episode. This issue is maintained by dataSyncWatchdog.mjs:
the body is refreshed on every breach evaluation and the issue closes automatically on recovery.
Streak: 0 consecutive failures.
Last success: 2026-07-26T00:17:01Z [QUARANTINED_URL: github.com].
Latest failure: n/a.
Corpus axis: last resources/content/** commit on dev: 2026-07-17T05:13:29Z (214h old). Deploys, fresh clones, CI, and container KB ingestion all build from committed dev — a green pipeline cannot attest to this backlog.
Breach reasons:
- last
resources/content/** commit is 214.0h old (threshold 48h — deploys, clones, CI and container KB ingestion all build from committed dev)
The pipeline is degrading silently: runs fail on schedule and nothing else surfaces it.
Root-cause work (if any) is tracked elsewhere; this issue only carries the alarm.
This alarm was opened by a forced workflow_dispatch dry run — close it manually if the pipeline is in fact healthy.
Standing alarm — one per breach episode. This issue is maintained by
dataSyncWatchdog.mjs: the body is refreshed on every breach evaluation and the issue closes automatically on recovery. Streak: 0 consecutive failures. Last success: 2026-07-26T00:17:01Z [QUARANTINED_URL: github.com]. Latest failure: n/a. Corpus axis: lastresources/content/**commit ondev: 2026-07-17T05:13:29Z (214h old). Deploys, fresh clones, CI, and container KB ingestion all build from committeddev— a green pipeline cannot attest to this backlog. Breach reasons:resources/content/**commit is 214.0h old (threshold 48h — deploys, clones, CI and container KB ingestion all build from committeddev) The pipeline is degrading silently: runs fail on schedule and nothing else surfaces it. Root-cause work (if any) is tracked elsewhere; this issue only carries the alarm.