feat: support full JavaScript in Isogloss - #8
Open
owengregson wants to merge 1 commit into
Open
Conversation
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.
Summary
eval,Function,with, observable coercion, intrinsic shadowing, async/generators, private classes, modules, TypeScript, and JSXe8cecb56ba89d47512a16e325d81cf46f64b2ecbWhy
PR 7's source path rejected configured functions when calls, effects, unsupported coercions, unsafe numeric ranges, or other non-provable expressions appeared. That made BPRF proof limits a JavaScript compatibility boundary.
This change separates compatibility from protection. Every valid JavaScript construct remains executable in a native lane; eligible bounded expressions are replaced with BPRF realizations; functions containing both are reported as hybrid. A missing configured target still fails closed so misspellings do not silently bypass selection.
Native regions remain observable JavaScript. Full-language support is intentionally not presented as whole-language protection, and only
protectedRegionCountrepresents BPRF replacement.Benchmark
Full measurements and environment metadata are checked in under
docs/superpowers/baselines/2026-07-25-pr8-isogloss-vs-legacy-vm.{md,json}.The speed and size comparison is not a claim of equal protection: seven current workloads are intentionally native compatibility regions.
Verification
cd packages/ruam && bun run prepublishOnly— typecheck, 205 tests, and package buildcd packages/ruam && bun run build:browsercd apps/web && bun run typecheck && bun run buildcd packages/ruam && bun run bench:architecturesgit diff --checkThis PR is stacked on PR 7 (
codex/pr6-performance-security-hardening).