Repository navigation
Conversation
The story engine and its backend interface, the fake backend the tests run on, the action registry and built-in actions, segments with their save policy, postcondition checks, scene judges, CommonTools/ScreenMachine and the story-file loader (built-in files; the dev-file span stays as the loader's test seam, without the lab's folder scan). From plza/fault-sweep, with only what PLZA AutoStory builds.
This was referenced Nov 15, 2026
Owner
Author
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.
Depends on #522
PLZA upstream chain, S2a: run a story. It adds the story engine over a backend interface (
StoryBackend,StoryGame, the action registry and built-in actions, step runner, engine policy, pose concept withZonePose), the fake backend the tests run on, segments with their save and verify policy, postcondition checks, scene judges,CommonTools/ScreenMachine, and the story-file loader. The loader keeps its dev-file span as a test seam, but the lab's dev-folder scan is left out. Everything is cut fromplza/fault-sweep(24133e1) with only what PLZA AutoStory builds; console operations (run options, launch from HOME) come in S2b. Under 10k lines, so the loader stays in this PR.Tests: StoryEngine, StoryEnginePolicy, StoryEngineRuns, StoryEngineSaveRetry, FrameCoverage, CoveredWatch, StorySegments, StorySavePolicy, SceneJudges and StoryFiles, all on the fake backend or synthetic data; the StoryStepExecutor suite gets its segment cases back. No CommandLineTests frames needed. Fork Draft CI builds and runs them.