fix(live-proof): dispatch from the exact-event lane and enable live tests everywhere - #1184
Merged
Merged
Conversation
…ests everywhere The exact-event review lane delivers GitHub effects directly and skips the artifact publication job, so its recommended live proofs never dispatched (observed on #1182, run 32002395638). Both lanes now share a repair-built candidates CLI, which the conditional build-script emits in every branch, and dispatch with a host-repo app token. live_test is now inherited from generic fallback profiles, enabling terminal-surface live proofs for every openclaw/* and steipete/* target (including openclaw/openclaw), with browser configs for ClawHub and the ClawSweeper bay demo. A recommended browser plan for a terminal-only repository is a logged skip instead of an error.
Contributor
|
🦞👀 Pull request received. I will update this pull request when review starts. |
Contributor
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: fix(live-proof): dispatch from the exact-event lane and enable live tests everywhere This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Production verification of the live-proof lane (#1181) on #1182 exposed a lane gap: the exact-event review path delivers GitHub effects directly and skips the artifact publication job, so its recommended live proofs never dispatched (run 32002395638 reviewed #1182 with every publish job skipped). Both lanes now extract dispatch candidates through one repair-built CLI —
repair:live-proof-candidates, emitted by every branch of the job's conditional build-script, satisfying the static workflow assertion — and POST theclawsweeper_live_proofdispatch with a host-repo app token that works regardless of which target repository was reviewed.Per maintainer direction, live tests are also enabled everywhere:
live_testis now inherited from generic fallback profiles, giving everyopenclaw/*andsteipete/*target (including openclaw/openclaw via the fallback) terminal-surface live proofs with install-only setup, plus explicit browser configs for ClawHub (vite dev server) and the ClawSweeper bay demo, and terminal configs for openclaw-facetime and fs-safe. A recommended browser plan for a repository without a configured dev server is now a logged skip instead of an execution error.Validation
pnpm buildandpnpm run build:repairclean.pnpm checkfailures are the known environmental repair fixtures that need a network package mirror.