Add Scenario progress foundation - #2371
Closed
Roman Lutz (romanlutz) wants to merge 1 commit into
Closed
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5d02c2d5-b499-4f78-a04d-03bffa750817
Contributor
Author
|
Superseded by same-repository draft #2372 so the seven dependent PRs can be registered as a native GitHub stack. |
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 persistent versioned Scenario run plans, stable logical work identities, backend-authoritative sizing, incremental progress cursors, and corrected timing/resume semantics. Planned units deduplicate repeated logical objectives while execution attempts remain observable.
What this layer adds
ScenarioRunPlanand progress models persisted in Scenario result metadata.Visual contract
Stack
This is 1 of 7 in the Scenario GUI stack and targets
main. Later layers add the catalog/launch UI, live progress, history, FIFO scheduling, configuration sizing, and result details.2f6c71556cfc145458c5c56971726039478db50c4b81ccf529a0ec02See the full implementation, screenshots, walkthrough, validation, and operational notes. Actual PR links will replace the snapshot links after all seven drafts exist.
Validation
Compatibility note
Prepended-conversation request converters now default to user-role messages, and strict non-chat targets can reject excluded roles. This intentional behavior change is isolated in this foundation layer.