feat: add deterministic Trusted Runtime orchestrator#617
Draft
safal207 wants to merge 23 commits into
Draft
Conversation
This was referenced Jun 22, 2026
This was referenced Jun 23, 2026
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
Implements #592 with a provider-neutral deterministic local workflow orchestrator for LS.
This PR is stacked on top of #616. Until #616 is merged, the diff against
mainincludes the contract foundation as its dependency. The PR remains a draft for that reason, although its own implementation and CI are complete.What is included
DeterministicWorkflowOrchestratorOrchestratorConfigWorkflowOrchestratormethods for role assignment and revision trailsmax_stepsmax_depthPLAN_REVISEDCognitive Trail eventsKey behavior
The same task and context produce the same workflow plan. The implementation does not generate timestamps or UUIDs and performs no provider calls.
Safety and boundaries
CI coverage integration
The main Security & CI workflow previously measured all of
python/moduleswhile running only two legacy hardening tests. Adding the Trusted Runtime files lowered aggregate coverage from the 12% threshold to 11.99%, even though the dedicated contract suite passed.This PR keeps the 12% threshold unchanged and adds
python/tests/test_trusted_runtime_*.pyto the existing hardening coverage run with the correctPYTHONPATH. The same JUnit and coverage artifacts now represent the code introduced by the PR.Local verification
Local preflight result: 5 tests passed; Ruff passed.
CI result
All workflows are green on head
83c59d98:Related