Document workflow execution board implementation boundary#2347
Open
AbigailDeng wants to merge 2 commits into
Open
Document workflow execution board implementation boundary#2347AbigailDeng wants to merge 2 commits into
AbigailDeng wants to merge 2 commits into
Conversation
AbigailDeng
force-pushed
the
feat/2026-06-24_workflow-execution-board-screen
branch
from
3e37b12 to
114e477
Compare
AbigailDeng
force-pushed
the
feat/2026-06-24_workflow-execution-board-screen
branch
from
114e477 to
64742ee
Compare
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
1 participant
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
Impact Paths
docs/designs/issue-2333-workflow-execution-board/consensus-plan.mddocs/designs/issue-2333-workflow-execution-board/frontend-api-gaps.mdNotes
The consensus keeps the PR design layout and product target while requiring capability-aware rendering: supported fields use existing APIs, runtime evidence stays visually isolated, and workflow node execution fields remain
unavailable/pending backend contractuntil a backend current-execution read model exists.Validation
bash tools/docs/lint.sh