Skip to content

Let hosts run a specification's slice isolation themselves - #1061

Merged
einari merged 1 commit into
mainfrom
feat/public-slice-isolation
Oct 25, 2026
Merged

einari merged 1 commit into
mainfrom
feat/public-slice-isolation

Conversation

@einari

@einari einari commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

Added

  • SemanticExecutionPlan.Runs, RunningReactions and RunningCaptures are public, so a host with its own specification executor can run only the isolated slice's reactions, captures and publications, the way Screenplay's runner does.

Expose Runs, RunningReactions and RunningCaptures so an executor outside Screenplay, such as Stage's, can narrow its reactions, captures and publications to the isolated slice.
@einari einari added minor New features, non-breaking additions ai-corpus: none Language change that does not affect the AI corpus (reason stated in a PR comment) labels Oct 25, 2026
@einari

einari commented Oct 25, 2026

Copy link
Copy Markdown
Contributor Author

Corpus impact: none - only widens host API visibility; the language and its semantics are unchanged (the semantic change is tracked in Cratis/AI#926 from #1060).

@einari
einari merged commit c06ba5b into main Oct 25, 2026
15 of 17 checks passed
@einari
einari deleted the feat/public-slice-isolation branch October 25, 2026 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai-corpus: none Language change that does not affect the AI corpus (reason stated in a PR comment) minor New features, non-breaking additions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant