Add catalog provenance field for mock vs live provider data

[emrekayat]

Why this matters

Query402 has deterministic demo fallbacks and live provider paths. Reviewers should know which provider data is mock, fallback, or live before paying.

Scope

Expose a small provenance field in provider catalog responses and render it in the dashboard:

• mock for deterministic demo data;
• fallback for AI/provider fallback mode;
• live for configured real providers;
• unknown as a safe default.

Suggested files:

• apps/api/src/providers/*
• apps/api/src/routes/public.ts
• apps/web/src/App.tsx
• packages/shared/src/schemas.ts

Acceptance criteria

• Every provider returned by the catalog includes provenance.
• Dashboard renders provenance as a compact badge.
• Unknown/missing provenance never renders as live.
• Tests cover catalog response shape and one UI rendering path.
• No pricing or payment behavior changes.

Wave complexity

High - clarifies demo vs live provider credibility for SCF/investor review.

[code-0-stella]

@code-0-stella has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, I have reviewed the issue and understand what needs to be done.

I would appreciate being assigned to it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @code-0-stella to this issue.

[egwujiohaifesinachiperpetual-max]

@egwujiohaifesinachiperpetual-max has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue! because I am very conversant with solving problems like this, and i can submit the pr with 48hr

ℹ️ Repo Maintainers: To accept this application, review their application or assign @egwujiohaifesinachiperpetual-max to this issue.

[Damilorlar]

@Damilorlar has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this project

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Damilorlar to this issue.

[Osifowora]

@Osifowora has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

​Hi maintainer, I would love to work on this issue. I can get started on it right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Osifowora to this issue.

[oscar24357]

@oscar24357 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer I'd love to work on this issue, please assign me to it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @oscar24357 to this issue.

[drips-wave]

Congratulations, @Damilorlar! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Damilorlar: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊