🔌 Plugin: Flow Scorecard — early WIP, seeking feedback

### 🔖 Summary

**What it does**

A plugin surfacing cross-layer validation status for critical user journeys, tied to a shared workflow definition so results across different validation stages stay comparable.

**Status**

Early internal prototype. Not yet integrated with the Soundcheck check/scorecard API.

**Why we’re posting now**

Filing this early per convention, so the community has visibility before the design solidifies.

**Feedback welcome on:**

- Anyone else working on a similar problem, or aware of related efforts

More detail to follow as things stabilize.

### 🌐 Project website (if applicable)

https://github.com/richsignalsrelay/neonarche

### ✌️ Context

**Flow Scorecard**

Today, concretely: one flow (login-happy-path) is registered as a kind: Flow entity in a local Backstage catalog, with a card on its entity page showing live pass/fail status, pulled from a Postgres fact store fed by two producers — a real Playwright run, and a Synthetics canary that's currently a local stub standing in for a real deployed AWS CloudWatch Synthetics canary. That's two of the four layers in the fuller vision below; pre-merge validation and coverage-history integration (Xray) don't exist yet, and neither does automated failure correlation.

The longer-term direction: every critical user journey (login, checkout, account creation) registered the same way, with a scorecard showing pass/fail across all four validation layers — pre-merge, pipeline, production canary, and coverage history — so a failure at any layer traces back to the same flow definition instead of cross-referencing four separate tools. A further-out, separate tier would add automated failure correlation (tracing a break to the specific commit, PR, or feature flag that caused it) and risk-scored release recommendations — neither of those exist yet either.

### 👀 Have you spent some time to check if this plugin request has been raised before?

- [x] I checked and didn't find similar issue

### ✍️ Are you willing to maintain the plugin?

- [x] I understand the responsibilities as a [Plugin Maintainer Governance](https://github.com/backstage/community/blob/main/GOVERNANCE.md#plugin-maintainer) & will maintain the plugin

### 🏢 Have you read the Code of Conduct?

- [x] I have read the [Code of Conduct](https://github.com/backstage/community-plugins/blob/main/CODE_OF_CONDUCT.md)

### Are you willing to submit PR?

Yes I am willing to submit a PR!

The issue names no repository files, tests, or entry points, and describes an early internal prototype rather than a defined implementation task. Start by reviewing the existing Flow entity, Backstage plugin, and validation integrations; the scope is not complete until the design and integration with the Soundcheck check/scorecard API are defined.

Written by the indexing model from the issue text.