Merged
Conversation
…#126) * Initial plan * Migrate fallback-bug.test.ts from forEachEngine to regressionTest Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * Migrate chained.test.ts from forEachEngine to regressionTest Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * Migrate string-interpolation.test.ts and interpolation-universal.test.ts to regressionTest Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * Migrate prototype-pollution.test.ts from forEachEngine Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * Migrate ternary.test.ts from forEachEngine to regressionTest (partial - 2 trace assertions need engine-specific handling) Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * Fix ternary refFallback trace assertion: runtime lazy vs compiler eager Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * refactor: migrate expressions.test.ts from forEachEngine to regressionTest Migrated the following test groups to the regressionTest harness: - expressions: execution (arithmetic, comparisons, tool source, chained) - expressions: operator precedence - boolean logic: not prefix - parenthesized arithmetic - safe flag propagation in expressions (with allowDowngrade) - safe navigation with sync tool (with allowDowngrade) Tests that cannot be migrated due to compiler limitations remain as forEachEngine blocks: - String literal comparison (serializer strips quotes) - Array mapping with expressions (serializer bug) - catch error fallback (compiler doesn't downgrade) - and/or boolean logic (compiler generates broken __and/__or) - Parenthesized boolean expressions (contain and/or) - condAnd/condOr without safe navigation - Safe flag on right operand of and/or Side-effect tests (short-circuit behavior) moved to test/legacy/expressions.test.ts per migration guidelines. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * refactor: migrate force-wire tests to regressionTest harness - Tests 1,2,4,5 migrated to regressionTest with test.multitool - Tests 3 (timing) and 6 (runtime-skip) moved to legacy/force-wire.test.ts - All 6 original test scenarios preserved Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Move remaining forEachEngine tests to legacy/ with README.md of action items Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * Migrate infinite-loop-protection.test.ts to regressionTest (partial) Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * Fix infinite-loop-protection.test.ts: fix traversal coverage and graphql replay failures Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * Fix serializer: support expressions, ternary, coalesce, string interpolation in tool self-wires Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * test: migrate tool-self-wires-runtime to regressionTest harness Move test/legacy/tool-self-wires-runtime.test.ts to test/tool-self-wires-runtime.test.ts using the regressionTest pattern with test.multitool from bridge-tools.ts. All 9 test cases are consolidated into a single regressionTest block with shared const declarations and per-scenario assertions. The compiler handles all cases natively so allowDowngrade is not needed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: migrate native-batching tests to regressionTest harness - Migrate all 3 tests from forEachEngine to regressionTest pattern - Fix serializer bug: loop-scoped tool handles now round-trip correctly - Add element property to HandleBinding type for tool handles - Mark element-scoped tools in parser (processLocalToolBindings) - Serializer skips element handles in header, emits inside array blocks - Serializer correctly identifies element-scoped tool wires - Delete legacy/native-batching.test.ts Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update legacy README with migration patterns and remove migrated files Co-authored-by: aarne <82001+aarne@users.noreply.github.com> * New tsc setup * Fix build * feat: add bridge-types dependency to bridge-compiler and update pnpm-lock * feat: refactor multitool functions for improved error handling and cleanup * Fix graphql control flog bug * Control flow tests are migrated * Test structure * feat: more compiler coverage * feat: enhance error handling and add new regression tests for expressions * fix: fuzzer * Tests * Some progress * Move back to legacy * fix tests * fix: update tools type to Record<string, unknown> in buildAotFn and compileAndRun * Hallukad jalle * Test stability * Broke a bunch of things * Fixed some stuff * Broke some stuff/ fixed some more stuff * Fixed more stuff * Broke some stuff again * Did not really mnage to fix all * Half fixes * Now to graphql * graphql tessts --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: aarne <82001+aarne@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Aarne Laur <aarne.laur@gmail.com>
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bridge | f758e54 | Commit Preview URL Branch Preview URL |
Mar 13 2026, 12:28 PM |
Contributor
Bencher Report
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.
No description provided.