Create an initial Backstage view for flow insights

[ourchitectureio]

Summary

Provide an early embedded experience in an existing developer portal surface.

Why

Backstage is a strong integration surface for early adoption, but it should consume the IDP API rather than become the center of truth.

Scope

Render:

• my blockers
• team flow highlights
• service-level risk signals
• links back to GitHub or GitLab native objects

Acceptance criteria

• View uses the IDP API rather than provider APIs directly
• Prioritizes actionable insights over raw events
• Handles mixed-provider scenarios cleanly
• Includes clear loading, empty, and error states

Notes

Start with a narrow card or page. Do not let the UI drive the domain model.

[github-actions]

This issue is ready for agent processing. An agent can pick this up by running:

/plan-work issue_number=228

Or find it automatically with /find-work.

[github-actions]

This issue has had no activity for 45 days and is now marked stale. If this work should remain open, add context in a comment or apply the keep-open label.