From 5dc3e16d876cc85dfd269cc48873f858df1636c7 Mon Sep 17 00:00:00 2001 From: Molecule AI Core-DevOps Date: Sat, 16 May 2026 13:58:28 +0000 Subject: [PATCH] ci(workflows): add bp-required:pending #1296 to e2e-peer-visibility jobs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Both `pr-validate` and `peer-visibility` jobs emit the `E2E Peer Visibility` status context. Add the lint-required-context-in-bp convention directive to acknowledge the intentional asymmetry (workflow deliberately RED today — Hermes-401 / OpenClaw-MCP-wiring fixes not yet proven through it). The flip to `bp-required: yes` tracks through molecule-core#1296. Ref: molecule-core#1328 --- .gitea/workflows/e2e-peer-visibility.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.gitea/workflows/e2e-peer-visibility.yml b/.gitea/workflows/e2e-peer-visibility.yml index f7b13f161..7fa8d79d2 100644 --- a/.gitea/workflows/e2e-peer-visibility.yml +++ b/.gitea/workflows/e2e-peer-visibility.yml @@ -101,6 +101,7 @@ jobs: # push/dispatch/cron only (30+ min). This is NOT a fake-green mask of # the real assertion — it validates the driving script's bash syntax # and inline-python so a broken test script fails at PR time. + # bp-required: pending #1296 ← flip to required once e2e-peer-visibility is green pr-validate: name: E2E Peer Visibility runs-on: ubuntu-latest @@ -118,6 +119,7 @@ jobs: # Real gate: provisions a throwaway org + sibling-per-runtime, drives # the LITERAL list_peers MCP call per runtime, asserts 200 + expected # peer set, then scoped teardown. push(main)/dispatch/cron only. + # bp-required: pending #1296 ← flip to required once e2e-peer-visibility is green peer-visibility: name: E2E Peer Visibility runs-on: ubuntu-latest -- 2.52.0