Repository navigation
test: cover local auxiliary dispatch boundaries - #447
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Oct 30, 2026
This was referenced Oct 30, 2026
This branch was successfully deployed
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
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.
Local-only Runner approvals need regression coverage that detects accidental Jev dispatch. These tests use the real Router, Decisions service and approval gate with a recording transport: local exact rules remain deterministic, natural-language rules wait for a person, and a cloud positive control proves the transport is reachable. Four local failure fixtures also verify retained targets and zero cloud, title, knowledge/pages or Jev dispatches.
Validation at
6b29f421f066470215730e080a668fd27f8a8927:pnpm build && pnpm testpassed with 2,251 passes, 26 skips and zero failures. All 13 focused cases passed. Temporarily removing the compiled local approval guard made both local-approval cases fail on one unexpected request; byte-for-byte restoration returned all 13 to passing. Independent review found no actionable findings. Initial cloud-control fixture failures are preserved in the review evidence.This is partial fixture evidence for #380. Native offline behavior, actual OOM/context handling, the full auxiliary network matrix, shared capacity/subagents, entry-point policy, context provenance and human acceptance remain open. Production behavior and product admission are unchanged.
Evidence:
docs/reviews/2026-10-30-lm5-auxiliary-dispatch.md.Integration: current signed head
3aa8b6bde5c2b12e20603b7f5678f94dfb713a28incorporates landed PR #448 and resolves the status-document conflict while retaining both entries.pnpm buildandpnpm testpassed on this combined tree: 2,261 passed, 26 skipped, zero failures. Fresh hosted CI and native-platform checks are pending. A merge preflight with PR #449 is clean.Prior head
d994f3b9d1a182f3e4c8f6ba345338c255ed80b6included the now-landed Canvas repair from #446. All hosted checks passed there: macOS job123961579838passed 478 desktop cases with four skips and seven site cases, and Windows, Linux, iPhone and CodeQL passed. Its queue request did not produce a queue run before #448 landed and made the status document conflict. Those results are historical evidence; the current head must pass its own hosted and queue validation.