Connect Process Chat to the active Studio case - #95
Merged
EvenSol merged 3 commits intoAug 10, 2026
Conversation
EvenSol
marked this pull request as ready for review
August 10, 2026 05:18
EvenSol
merged commit Aug 10, 2026
fd0fad8
into
automation/web-studio-case-context-20260810
1 check passed
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
Advances the initial S3/S6 active-case handoff as the third and final PR in the bounded Studio stack.
process_modelsession handoff; no second model adapter or simulator is introducedStacked PR contract
automation/web-studio-shell-20260809→main)automation/web-studio-case-context-20260810→ root branch)73233f9c25854b5d8a992b93fd3f6f7439c894b1automation/web-studio-case-context-20260810automation/web-studio-process-chat-handoff-20260810beefaaed69d120936d5b43441247385586a31b34This child is not independently mergeable to
main. PR #93 and then #94 must merge first; this PR must then be safely retargeted and revalidated.The active Studio implementation stack is at its maximum of three open PRs. No fourth implementation PR may be created until an earlier PR is merged or closed.
Engineering boundary
Process Chat retains its existing Classic route, upload/build workflows and deterministic NeqSim-backed tools. This PR does not broaden chat permissions or claim that conversational changes have updated the portable flowsheet definition.
When the live chat model differs, Studio explicitly preserves:
The prompt adapter forwards only a whitelisted JSON-safe projection. Numeric engineering results must still come from the live model or an executed deterministic NeqSim calculation.
Validation
Passed locally on the exact source:
process_chat/chat_tools.py,process_chat/studio_context.py, Process Chat and the new testsPYTHONPATH=. python tests/test_process_chat_studio_context.py -v— 3/3Hosted GitHub Actions Process Flowsheet Studio #388, run
31353304901, completed successfully on exact headbeefaaed. All steps passed:An intermediate head exposed that two inherited tests intentionally construct
ProcessChatSessionwithout__init__. The final head preserves that legacy construction path with an optional-context fallback; the complete cumulative gate then passed.Three-repository evidence
equinor/neqsimmaster advanced to60a6bde7with merged ProcessSystem transient snapshot/event integration (#2917), relevant future S7 evidence but not required by this S3/S6 change.EvenSol/NeqSim-Colabmaster remains7cb7e5d4; the executed DEXPI safety-study notebook remains the current drawing acceptance reference. No notebook change is justified for bounded prompt metadata.Documentation impact
Updates
docs/neqsim_web_studio_roadmap.mdto record bounded prompt evidence and lifecycle limitations as in stack, not merged completion. No Classic documentation, calculation behavior or portable case format changes.Next dependency-ready tranche
The stack is full. Continue with validation, review feedback, conflict repair and integration until PR #93 or #94 is merged. After #93 merges, safely retarget #94 to
main, revalidate its exact head, then advance #95 in order.