Skip to content

refactor(jev): unify source artifacts and remove compatibility paths - #187

Merged
M09Ic merged 3 commits into
masterfrom
refactor/jev-source-unification
Oct 25, 2026
Merged

M09Ic merged 3 commits into
masterfrom
refactor/jev-source-unification

Conversation

@M09Ic

@M09Ic M09Ic commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

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, executable Program values with typed qualification, and one complete JSON artifact at each generation boundary.

  • Remove library versions, candidate promotion/recovery, backup scanning, legacy suite/source inputs and manufactured entry descriptions. Keep rejected source and actionable diagnostics in Generation events and audit logs.
  • Share the actual trajectory once during semantic review. Validate report evidence references without expanding the same result at every boundary, retain system and prior user constraints, and consume typed replay outcomes directly instead of decoding our own diagnostic JSON. Native snapshots use the existing contract type directly.
  • Remove Guardrail mode/error-policy translations, deprecated --init rewriting, gogo output-flag rewrites, Harness credential fallbacks, unused config field migration callbacks and version-specific SQLite migration advice.
  • Render original live AOP events and typed libraries in the production UI components. Fix overlapping library entries and details on narrow screens. Update the RFC and current documentation around the implemented behavior.

Validation:

  • Default and full-edition JEV tests; production AIScan profile, Guardrail, config/CLI, IOA, gogo, console and Web service regressions.
  • Architecture checks, focused go vet, golangci-lint (0 issues), frontend production build and all 86 JEV Playwright tests, including two checks backed by retained real execution evidence.
  • Real deepseek-flash at 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.
  • Raw execution evidence and screenshots were checked for the supplied credentials; no matches. Credentials and runtime artifacts are excluded from the commit.

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.md for scope and reproduction.

Closes #186

@M09Ic M09Ic changed the title refactor(jev): converge on one library and artifact schema refactor(jev): unify source artifacts and remove compatibility paths Oct 24, 2026
@M09Ic
M09Ic merged commit 5ab5d6c into master Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RFC: 从源头收敛 JEV 库与类型化协议

1 participant