Add preprocessor parity and expanded fixture harness support#25
Merged
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
Adds TypeScript parity support for the Python experimental preprocessor contract and expands TS fixture harness coverage to match the newer Python conformance surface.
This PR:
syncs TS fixtures through Python
v0.6.19adds harness support for:
conformance/state-jsonconformance/checkpointpreprocessorimplements experimental preprocessor parity against the synced Python fixture/API contracts
moves the preprocessor implementation into a dedicated experimental module (
src/experimental/preprocessor)removes experimental preprocessor exports from the root TS package surface
Why
TS parity work had expanded beyond the original step/transcript fixture surface.
Python
0.6.18and0.6.19introduced:preprocess/preprocessornamingThis PR brings TS into alignment with those authoritative fixture contracts before future TS 0.6 stabilization/release work.
Scope checklist
nullrule)Notes
No core engine behavior changes.
No Python fixture modifications.
Experimental preprocessor APIs are intentionally isolated from the root TS package exports.
Package subpath export wiring for experimental modules is intentionally deferred to later packaging/release work.
Validation run:
npm testnpm run fixtures:checknpm run fixtures:preprocessor:check