diff --git a/.agents/rules/github_actions_workflows.md b/.agents/rules/github_actions_workflows.md
index 8e95dcee5b..00f2177ecc 100644
--- a/.agents/rules/github_actions_workflows.md
+++ b/.agents/rules/github_actions_workflows.md
@@ -12,6 +12,8 @@ globs: [".github/workflows/*.yml", ".github/workflows/*.yaml", ".github/*.yaml"]
   redundant shell parameter stripping or conversions.
 * Print console messages using GitHub workflow command syntax (e.g.,
   `::error::`, `::warning::`, `::notice::`, `::group::`).
+* **Event Payload Resolution**: Load event details directly from
+  `$GITHUB_EVENT_PATH` rather than passing fields via env vars or CLI flags.
 
 ## Workflow Python Scripts & Testing
 * **Test Location**: Place workflow tests under `tests/workflows/`.
diff --git a/.agents/skills/merge-pr/SKILL.md b/.agents/skills/merge-pr/SKILL.md
index ae3e2e3ad5..8be67821e4 100644
--- a/.agents/skills/merge-pr/SKILL.md
+++ b/.agents/skills/merge-pr/SKILL.md
@@ -19,6 +19,8 @@ When the user asks to merge a pull request (e.g., "merge PR <number>", "merge th
      (`retry_buildkite_jobs.py <pr_number>`) to automatically retry any
      transient network flakes (e.g., HTTP 504 gateway timeouts, downloader
      errors).
+   - **Soft-Failing Jobs**: Experimental Buildkite jobs (e.g. `*rolling*`
+     Bazel) are non-blocking soft failures; do not treat them as merge blockers.
    - When the PR is queued, actively discover the merge queue branch via
      `gh api repos/:owner/:repo/branches --jq '.[].name | select(test("gh-readonly-queue/.*/pr-<pr_number>-"))'`
      and monitor commit statuses/Buildkite builds running on that temporary
diff --git a/.agents/skills/monitor-ci-results/SKILL.md b/.agents/skills/monitor-ci-results/SKILL.md
index e2475b55ad..92b1dca7a6 100644
--- a/.agents/skills/monitor-ci-results/SKILL.md
+++ b/.agents/skills/monitor-ci-results/SKILL.md
@@ -33,6 +33,7 @@ or when monitoring CI after PR updates:
 3. **Failure Reporting**: When any GitHub check or Buildkite job completes
    with errors, `monitor_remote_ci.py` dispatches a high-priority notification
    message reporting the failed check back to your conversation.
+   - Soft failures (e.g. `*rolling*` Bazel) are non-blocking warnings; ignore.
 4. **Subagent Analysis**: Upon receiving a failure notification message from
    the monitoring script, immediately launch a separate subagent using the
    `invoke_subagent` tool with the role "CI Failure Analyzer" to run the