Skip to content

feat(quick-start): add workflow-backed creation flow - #7

Draft
huyanxius wants to merge 3 commits into
feat/workflow-run-corefrom
feat/quick-start-flow
Draft

feat(quick-start): add workflow-backed creation flow#7
huyanxius wants to merge 3 commits into
feat/workflow-run-corefrom
feat/quick-start-flow

Conversation

@huyanxius

Copy link
Copy Markdown
Owner

Title: feat(quick-start): add workflow-backed creation flow

Dependency

Feature Description

  • Replace the Quick Start placeholder with a responsive natural-language creation surface.
  • Create and observe one WorkflowRun on /quick-start/:runId without redirecting to Workflow Editor.
  • Show real running, failure, interruption, and character-template candidate states from the shared WorkflowRun.

Implementation Approach

  • Prepare a real Project first, then delegate execution, recovery, subscriptions, and interruption to the existing WorkflowController.
  • Keep Project creation behind an injected page-level boundary; unconfigured production wiring fails explicitly and never invents a project ID or Mock success.
  • Reuse the LiveDemo input/progress/result rhythm without copying its fake timers, hardcoded outputs, routes, or runtime.

Testing

  • npm run format:check — passed (49 files)
  • npm run lint — passed
  • npm run typecheck — passed
  • npm run test -- --reporter=dot — passed (6 files, 37 tests)
  • npm run build — passed
  • git diff --check feat/workflow-run-core...HEAD — passed
  • Local browser — desktop/mobile render passed; explicit unavailable state and zero console errors confirmed

Follow-ups

  • Wire real ProjectApis, GenerationApis, and TaskApis after the backend address and DTO fixtures are confirmed.
  • Candidate selection and later workflow steps remain separate vertical slices.

[CX] Prompt & Review

  • Prompt summary: implement the next Quick Start slice on the current reduced architecture, reuse only safe LiveDemo presentation, and preserve the frontend-only WorkflowRun model.
  • AI review: layering, unnecessary complexity, hardcoding, async error boundaries, and test validity were checked; no blocker remained.
  • Human review: pending; keep this PR in Draft.

Refs 1024XEngineer#58

Quick Start needs to drive the frontend WorkflowRun without entering the editor.

Add the page UI and an injectable service that prepares a project and delegates execution to WorkflowController.

Unconfigured production wiring now fails explicitly instead of falling back to fake data.
Quick Start needs regression coverage across its page and controller boundary.

Exercise the real WorkflowRun store and WorkflowController with only external ports substituted.

Lock same-page execution, failure persistence, unexpected errors, and candidate delivery.
…flow

经上游分支带入 main 的后端 1024XEngineer#64,根 .gitignore 冲突已在上游分支解决。
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant