[DO NOT MERGE] Implement Workflow Activity vNext console - #3187
Draft
AbigailDeng wants to merge 192 commits into
Draft
AbigailDeng wants to merge 192 commits into
AbigailDeng wants to merge 192 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## dev #3187 +/- ##
==========================================
- Coverage 83.43% 83.43% -0.01%
==========================================
Files 1685 1685
Lines 193217 193217
Branches 23239 23239
==========================================
- Hits 161218 161202 -16
- Misses 21194 21200 +6
- Partials 10805 10815 +10
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
* Implement Workflow Activity vNext * Render Workflow Activity vNext as standalone workbench * Refine Workflow Activity vNext settings layout * Hide internal workflow diagnostics from primary UI * Decode system-default LLM settings * Fix Workflow Activity table scrolling * Document workflow list filter semantics * Align Workflow and Activity filters * Fix Workflow Activity user path defects * Fix committed workflow editor fallback * Complete Workflow Activity functional paths * Reuse Workflow Studio canvas surface * Document NyxID visual alignment * Fix AI service selection * Align Workflow Activity with NyxID * Complete Workflow Activity vNext implementation * Fix workflow API error feedback * Fix console web type errors --------- Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
* Document settings save action dock * Plan Settings save action dock implementation * Fix Settings save action dock
Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
* Keep new workflow setup recoverable * codex: fix CI failure on PR #3234 --------- Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
* Map run failures to actionable toasts * codex: fix CI failure on PR #3232 --------- Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
* Improve editor save and publish readiness * codex: fix CI failure on PR #3241 --------- Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
* Redesign account identity surface * codex: fix CI failure on PR #3237 --------- Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
* Document workflow list metadata design * Plan workflow list metadata refinement * Refine workflow list metadata hierarchy --------- Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
* Document new workflow creation UX * Plan new workflow creation UX * Fix new workflow creation experience --------- Co-authored-by: Abigail Deng <abigaildeng@AbigaildeMacBook-Pro.local>
* Document workflow row action hierarchy * Plan workflow row action hierarchy * Fix workflow row action hierarchy
* Design workflow archive behavior * Plan workflow archive implementation * Model workflow archival observation * Add workflow archive controls
…ow-activity-vnext
* Use toast for workflow save failures * Route transient frontend errors to toast
* Document workflow published invoke flow * Invoke published workflows from the editor * Add published run translations
* Document Add node sequential link fix * Document Add node implementation plan * Test implicit workflow transition materialization * Materialize implicit workflow transitions * Test Add node sequential placement * Fix Add node sequential placement
* Document content skeleton design * Plan content skeleton implementation * Refine skeleton TDD sequence * Add shared content skeleton presets * Add skeletons to primary catalog tables * Add skeletons to primary resource lists * Add skeletons to governance catalogs * Add a Mission Wall loading skeleton * Refine skeleton loading semantics * Fix console locale catalog audit * Fix console web merge type errors
…t-name-suffix fix: Add six random digits to default channel names
…as-scaling Scale Workflow Activity vNext canvas for large workflows
…tion-feedback Clarify workflow generation and pending change feedback
…l-skill-name Fix channel connection feedback and show authorized services
…and-ci-scope Fix workflow home scope and frontend-only coverage routing
…me-editor Add channel runtime editor with shared connection controls
…h-loading Show connected channels table loading during manual refresh
…e-layout Display channel authorized services in one horizontal list
…eedback Fix channel editor returning to details after saving
…imeouts fix: Prevent frontend CI test timeouts without skipping coverage
…ction-success fix: Restore Telegram creation success details
…ames fix(channels): edit only label and skill name
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.
This draft implements the Workflow Activity vNext console: a dedicated workspace for creating workflows, running them, inspecting execution activity, managing schedules, and configuring account/AI settings. The implementation uses the existing backend APIs and the checked-in design baseline.
Implemented behavior
/scopes/:scopeId/workflow-activity-vnextworkbench with Workflows, Activity, and Settings navigation.Scope and backend impact
At merge commit
6254a4117e0ff960d70ba18344fc1a0628209069, the PR contains 381 changed files compared withdev: 347 files under the frontend package, 32 repository documentation files, and 2 CI workflow/test files.There are no backend production or backend test changes under
src/ortest/, and no C#, project, or protobuf contract changes. Backend contracts are consumed by the frontend. The.github/workflows/ci.ymlchange affects backend coverage job routing, so the PR's impact includes CI behavior.Primary implementation paths:
apps/aevatar-console-web/src/pages/workflow-activity-vnext/apps/aevatar-console-web/src/shared/,src/locales/, andsrc/app.tsxapps/aevatar-console-web/config/and dependency manifestsapps/aevatar-console-web/docs/and related repositorydocs/.github/workflows/ci.ymlHome and CI behavior
The home URL is
/workflows. It refreshes the existing/api/auth/meaccount scope and opens the current account's scoped workflow catalogue with loading, retry, and sign-in recovery. The branch-name backend coverage exemption has been removed: coverage is skipped for frontend-only PR changes, while mixed changes, CI/build infrastructure changes, and scheduled/manual/mainline runs retain the applicable gate. Frontend tests are partitioned into four CI shards; the existingconsole-webgate also owns typecheck and production build.Design and API contract
The design specification records the original
feature/integratecontract baseline. Feature-specific changes must be checked against that branch's current API contracts, retain separate resource identities, and expose API failure/projection delay honestly.Synchronization with dev — 2026-09-16
Merge commit
6254a4117e0ff960d70ba18344fc1a0628209069mergesdevat1df08db0d88627eb47c2e8a9a44b5df806ee293dinto the previous integration head3dfb85f2796f1fd2c13a9e00c7962adab78e7331. It incorporates 972 previously missing commits without rewriting the branch history.devis now an ancestor of this integration head.Resolved 16 conflicted files. The merge keeps canonical scoped navigation and vNext routes, combines dev's Chat actor-state/control APIs with the existing shared toast/tooltip behavior, preserves required access-review return URLs while adding exact OAuth resource indicators, adopts member endpoint invocation-readiness contracts, retains Team request views, and uses dev's deterministic Kafka batch reader. A deletion-failure regression test protects the retained Chat toast behavior. No backend production or test differences remain relative to dev; backend changes brought into this branch are inherited from dev.
Documentation impact: the existing product/design documents remain the feature contract, dev documentation updates are incorporated, and this PR records the integration decisions and verification evidence.
Local verification
chatPresentation.tsx(accessibility and array-index keys), plus existing warnings. Both parent versions reproduce the accessibility diagnostics; all nine index-key diagnostic source lines are unchanged in both parents. These were not introduced by the conflict resolutions.git diff --checkfor the resolved files passes. The complete incoming diff retains one pre-existing trailing blank-line diagnostic intest/Aevatar.AI.Tests/NyxIdChatActionContinuationEndpointsTests.cs, identical to dev.Exact focused verification commands
Frontend commands were run from
apps/aevatar-console-web/:The broader changed-file lint command (pre-existing diagnostics noted above):
Commands run from the repository root:
The scope analyzer used pre-merge
HEAD(3dfb85f2796f1fd2c13a9e00c7962adab78e7331) while the merge was staged. High-fan-out locale/app/route files were verified through scoped static checks and explicit contract/consumer tests; no unbounded dependency-discovery run was used.