Repository navigation
refactor(jev): unify source artifacts and remove compatibility paths - #187
Merged
Merged
Conversation
Closed
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.
JEV used multiple library and compiler artifact shapes, persisted candidate state, and JSON-encoded qualification fields. The first release now uses one
{claims,reflexes}library, executableProgramvalues with typed qualification, and one complete JSON artifact at each generation boundary.--initrewriting, gogo output-flag rewrites, Harness credential fallbacks, unused config field migration callbacks and version-specific SQLite migration advice.Validation:
go vet, golangci-lint (0 issues), frontend production build and all 86 JEV Playwright tests, including two checks backed by retained real execution evidence.deepseek-flashat the requested gateway, TypeSafe JEV and Chromium: Shadow DOM save and repeated add/checkout both generated Reflexes from empty libraries and passed cold/warm Off/Auto comparisons. Reuse of those actual libraries on the cleaned runtime passed both formal warm tasks: 6/8 native calls, zero main model tool calls, unchanged source and correct private business oracles.Limits: expense submission/recovery has not passed Reflex takeover. Completed runs were business-correct but produced unsupported compound shell calls; a final run using explicit native-wait guidance was interrupted after repeated native replay mismatches. Those failures are retained. An extra Shadow DOM reload preflight also fell back to the main model; its formal warm task passed. The new UI checks replay actual backend/browser events in production components; they do not submit tasks through the full production Web frontend. Cold compilation remains expensive, and this does not establish total token or monetary savings. See
docs/jev.mdfor scope and reproduction.Closes #186