feat(console-web): strengthen Team operations loop from attention to action

[potter-sun]

Background

Teams is now the Console Web home route, and Team Detail is the main operational workspace. The next product gap is making every attention signal actionable: failed runs, waiting runs, binding problems, and member lifecycle gaps should lead to the right Studio, Runs, Governance, or Platform action.

Scope

• Audit Team home and Team Detail for attention signals without clear next action.
• Add stable deep links from Team member, events, topology, and overview panels to Studio lifecycle steps and Platform tools.
• Keep Team pages honest about eventual consistency, partial data, and unavailable projections.
• Ensure Team Detail does not reimplement full member Build/Bind/Invoke/Observe surfaces.
• Tighten empty, loading, partial, and error states around member roster and run history.

Acceptance Criteria

• Team home surfaces current team/member health without fake global KPIs.
• Team Detail attention items provide a concrete next action.
• Failed or waiting runs can move to Runs or Studio with preserved scope, team, member, and run context.
• Binding or deployment problems deep-link to the right Platform page.
• Team pages stay read-model/query honest and do not build shadow truth.
• Tests cover the main Team -> Studio, Team -> Runs, and Team -> Platform paths.

Verification

• npm --prefix apps/aevatar-console-web run tsc
• npm --prefix apps/aevatar-console-web run build
• npm --prefix apps/aevatar-console-web run test -- --runInBand src/pages/teams/home.test.tsx src/pages/teams/detail.test.tsx src/pages/teams/runtime/teamRuntimeLens.test.ts src/shared/navigation/teamRoutes.test.ts src/shared/navigation/runtimeRoutes.test.ts

References

• apps/aevatar-console-web/src/pages/teams/home.tsx
• apps/aevatar-console-web/src/pages/teams/detail.tsx
• apps/aevatar-console-web/src/pages/teams/runtime/teamRuntimeLens.ts
• apps/aevatar-console-web/src/shared/navigation/teamRoutes.ts
• docs/design/2026-04-15-aevatar-console-web-implementation-checklist.md

[potter-sun]

Implemented in draft PR #662: #662

Summary:

• Preserved concrete run identity in Team -> Runs handoffs by adding runId support to runtime run links.
• Made Team Detail attention actions more direct for waiting/degraded runs.
• Added top-level Team Detail handoffs to Governance bindings and Deployments with service/revision/deployment context.
• Kept Team pages as read-model/query handoff surfaces rather than adding shadow runtime state.

Verification:

• npm --prefix apps/aevatar-console-web run test -- --runInBand src/pages/teams/home.test.tsx src/pages/teams/detail.test.tsx src/pages/teams/runtime/teamRuntimeLens.test.ts src/shared/navigation/teamRoutes.test.ts src/shared/navigation/runtimeRoutes.test.ts
• npm --prefix apps/aevatar-console-web run tsc
• npm --prefix apps/aevatar-console-web run build
• git diff --check