Cover Flow authoring, execution, and observability journeys

[gbaudrit]

Technical category

Testing

Area

Console

Problem

PR #170 covers creation of one handoff orchestration and Entry binding, but Workflow authoring, the visual designer, composed Flow and Tool steps, publication lifecycle, execution, run inspection, causality, task linkage, and failure states remain uncovered at browser level.

Impact

Flow orchestration is a central product capability. Browser regressions can make valid domain behavior unusable or misrepresent run state while lower-level tests continue to pass. This is important roadmap coverage with manual workarounds, so priority P2 applies.

Expected outcome

Typed journeys and deterministic fixtures cover Flow creation and editing across supported modes, publication and activation, execution, run/event/task inspection, nested causality, and expected validation or runtime failure presentation.

Scope

• Flows list, new Flow, details, orchestration editor, and visual designer.
• Workflow, orchestration/handoff, Flow-call, and governed Tool step authoring where exposed.
• Publish/activate and immutable namespaced views.
• Flow Runs, run details, agent runs, run events, task details, and task-linked Flow Runs.
• Deterministic success, pause/pending action, cancellation, and representative failure states supported by the local fixture.

Out of scope

Live model quality evaluation, external MCP services, performance/load testing, and unsupported future Flow modes.

Dependencies

• Parent: Provide reusable Playwright journeys for UX tests and communication captures #283.
• Initial reusable automation: PR feat(testing): add reusable Playwright browser journeys #170.
• Executable Playwright coverage catalog.
• Current Flow composition implementation on main.

Implementation guidance

Use fixture APIs to materialize precise run states when reaching them entirely through the UI would test unrelated setup. Journeys must still exercise user-visible authoring and lifecycle operations.

Alternatives considered

Only screenshotting the designer was rejected because it would not validate persisted definitions, publication, execution, or observable run transitions.

Acceptance criteria

• Every in-scope route renders from deterministic fixture state.
• Supported Flow authoring modes have reusable journeys and persisted-state assertions.
• Publication, activation, execution, and run-state transitions are asserted without arbitrary sleeps.
• Nested Flow causality and task links are visible and navigable in browser tests.
• Expected validation and representative runtime failures are covered.
• Coverage catalog ownership and capture checkpoints are updated.

Tests and validation

Run TypeScript compilation, affected Playwright suites, full browser smoke, Flow-focused .NET tests, full .NET validation, documentation build, and desktop/mobile executable smoke for changed UI.

Additional context

This is a squashable child increment targeting the Playwright coverage integration branch.

Attachments

None.

Preliminary checks

• I searched for an existing issue covering this work.