Feat/2026 04 09 console web ai teams

[AbigailDeng]

Summary

This PR tightens the end-to-end Teams + Studio workflow experience in Console Web, focusing on real usage issues found while dogfooding the flow.

It mainly improves:

• Teams -> Advanced Edit -> Studio / Runs / Invoke navigation
• Ask AI workflow generation compatibility
• workflow save / restore / post-restart visibility
• layout and scrolling issues across Studio, Runs, and Invoke Lab
• local persistent development mode for workflow recovery

What changed

1. Improved Teams + Studio + Runs navigation flow

• Added returnTo propagation so the Runs page can navigate back to the originating Studio route or the team advanced tab correctly
• Improved context handoff between Teams advanced editing, Studio, Runs, and Invoke Lab
• Fixed several broken or confusing back-navigation paths

2. Fixed Ask AI workflow generation failures

• Added compatibility normalization for pseudo step types such as llm, chat, and task, mapping them to llm_call
• Tightened Ask AI prompt guidance to reduce invalid YAML generations
• Fixed workflow rename/save behavior so the saved workflow name stays aligned with the YAML name

3. Fixed workflow execution and result presentation issues

• Fixed an Orleans self-cleanup deadlock during workflow actor destruction after run completion
• Fixed the gap where Last output existed but Messages still showed as empty
• Improved Runs page behavior around trace workspace, tab switching, and back navigation

4. Fixed Studio / Invoke Lab layout and scrolling issues

• Fixed the Studio workflows page where the lower workflow list area could be clipped and effectively unusable
• Fixed the Invoke Lab composer area being visually cut off
• Reduced nested/competing scroll container issues across Studio surfaces

5. Added stronger local persistence and workflow recovery support

• Added a PersistentLocal runtime profile using Orleans + Garnet for local persistent actor state
• Added workflow recovery support from chrono-storage when scope workflow state is missing after restart
• Updated local runtime documentation to make persistent local testing easier

Impacted areas

• Console Web Teams / Studio / Runs / Invoke Lab
• Studio workflow save / load / Ask AI / bind flows
• Orleans runtime actor cleanup
• local persistent development setup
• chrono-storage-backed workflow recovery path

Validation

Executed:

• pnpm exec tsc --noEmit
• pnpm exec jest src/pages/studio/components/StudioShell.test.tsx src/pages/studio/components/StudioWorkflowsPage.test.tsx --runInBand --watchman=false
• ~/.dotnet/dotnet test test/Aevatar.Studio.Tests/Aevatar.Studio.Tests.csproj --filter "FullyQualifiedName~WorkflowCompatibilityProfileTests"
• ~/.dotnet/dotnet test test/Aevatar.Tools.Cli.Tests/Aevatar.Tools.Cli.Tests.csproj --filter "FullyQualifiedName~WorkflowGenerateOrchestratorTests|FullyQualifiedName~AppScopedWorkflowServiceTests"
• ~/.dotnet/dotnet test test/Aevatar.Foundation.Runtime.Hosting.Tests/Aevatar.Foundation.Runtime.Hosting.Tests.csproj --filter "FullyQualifiedName~OrleansActorRuntimeForwardingTests"

Manually verified flows:

• Teams -> Advanced Edit -> Ask AI workflow generation
• Run draft -> Messages / Events inspection
• Runs -> back to team advanced edit
• Bind team entry -> Open Project Invoke
• Studio workflow list browsing and scrolling
• workflow recovery after backend restart

Docs

• Added PersistentLocal local runtime configuration
• Updated Host API README with local persistent runtime guidance

Notes

There are still some outdated assertions in apps/aevatar-console-web/src/pages/runs/index.test.tsx that do not match the current UI. Those are pre-existing test expectation issues and were not treated as blockers for this PR.