Repository navigation
Consolidate reviewed development engines and qualification boundaries - #69
Merged
Merged
Conversation
Keep trusted authored staging separate from finite iterative finalization. Reuse one engine ledger through schema document admission; preserve exact keys, numbers, omission and native schema authority. Add real-engine semantic, lifecycle, compiler and public consumer qualification.
Retain measured variadic composition, record real native and WASI outcomes and the disk blocker, preserve all product-guide checks, and complete prototype test provenance.
Record all production command outcomes, complete sanitizer rerun, corpus and cap counts, strict DocC and actual completion evidence. Keep Linux pending and authored staging limitations explicit.
Trust only GITHUB_WORKSPACE in the ephemeral container and assert its HEAD matches GITHUB_SHA before qualification. Preserve metadata failures and all native, corpus, cap, privacy and compiler checks.
Record both Linux architectures full and safety outcomes, byte-identical clean reproduction, actual WASI DSL tests and Apple SDK builds. Preserve failed attempts and explicit staging/platform scopes; keep merging and release publication separate.
ThorFuchs
marked this pull request as ready for review
October 25, 2026 14:06
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.
Consolidate the existing development proposals on current main while retaining stable 1.6.1 unchanged. This reconciles the reviewed graph source, JSONTransform's single compiler/pull VM, optional exact value/schema DSLs and package-only store preparation/construction. CLI stays 1.7.0-dev; twelve libraries plus CLI and thirteen catalogs include the shared non-product JSONDSLCore reference. Root dependencies, deployment floors, fixtures, notices and 49 baseline caps are preserved.
Compiler graphs preserve all 1,205 admitted declarations unchanged and add exactly 295 (graph 34, Transform 42, ValueDSL 27, SchemaDSL 110 and shared core 82). Runtime source is checked against graph reconciliation 99dbb45, Transform RC 6fe8067, DSL 6426421 and private store b4874c0. CLI host algorithms match 6fe8067; version/identity and integration/qualification glue are deliberately reconciled. DSL staging is trusted authored work with bounded finalization; private store construction shares one original read ledger and adds no public store/follow/persistence API.
Final head a9e1c80, tree a707549c61d424c0e76d48765c201e3f851ae26a. Native CI 40195691957 and Linux CI 40195691945 passed all eight product contexts, including the existing composition/reference-import steps. Native archive independently passed all 58 native commands outside Git and reproduced exact source SHA-256 9741040df4f9fc41e57e15824afd9a28a36e24d5e12d8fd0d9d471e0a15467c6. Downloaded artifacts are verified against GitHub digests and every candidate source member.
Actual populations: 975 native and 959 on each Linux architecture, 390 parameter invocations; targeted concurrency 60 native/59 Linux. WASI passed 82 commands, 871 functions / 353 parameters in Debug and Release, with host timings explicitly unrun. Eight changed-module mobile SDK compile commands passed; no new device-runtime claim. DocC compiled 13 catalogs and documents all 1,500 authored declarations. All 17 original README Swift fences remain; one DSL fence is added. Qualification-harness 26, site regressions 12 and compiler-rejection classifier 3 pass.
Two integration-harness failures were diagnosed and retained: implicit standalone SDK 27.0 selection with SwiftPM SDK 27.2 modules, corrected through explicit supported SDK selection; and the Navigation-only probe's outdated catalog selector, corrected without weakening the full 13-catalog requirement and covered by a failure-detection regression. No Swift runtime algorithm was changed to obtain green results.
Composition/root and lower-floor proposals remain held. Controlled G4, the historical streaming disposition and partial P4 instrumentation remain explicit. The old 1.7-only allocation waiver is not an allocation/overhead pass or a release authorization. Original proposals/refs and private evidence remain preserved separately. This is development consolidation, with no tag, release, protection change or manual deployment.