feat(frontend): add SCF diligence snapshot panel

[Oyinkans0la12]

Closes #148

Summary

Add a compact Diligence Snapshot panel that surfaces existing deployment information for SCF reviewers and investors.

Changes

• Added a frontend Diligence Snapshot panel
• Displayed current public mode (testnet-only or mainnet-enabled)
• Displayed configured Sepolia HTLC and ResolverRegistry addresses with explorer links
• Displayed configured Stellar Testnet HTLC and ResolverRegistry contracts with Stellar Expert links
• Displayed coordinator status link when configured
• Added graceful fallback for missing configuration values
• Added/updated frontend tests

Why

Reviewers should be able to verify deployment evidence directly from the application without searching through documentation. This panel surfaces existing configuration in a compact, read-only format while avoiding duplicated configuration.

Testing

Covered:

• Panel renders without wallet connection
• Configured values display correctly
• Missing configuration displays "Not configured"
• Explorer links are clickable
• Frontend build passes

Validation:

pnpm --filter @oversync/frontend build

Scope

This PR is frontend-only. It does not modify swap behavior, settlement logic, deployment configuration, network semantics, or runtime application behavior.

[vercel]

@Oyinkans0la12 is attempting to deploy a commit to the karagoz's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@Oyinkans0la12 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[karagozemin]

Thanks for the SCF diligence snapshot panel. I cannot merge this yet because the frontend typecheck fails on the merge result.

Command run:

pnpm --filter @oversync/frontend exec tsc --noEmit

Failure:

src/components/DiligenceSnapshot.tsx(1,1): error TS6133: `React` is declared but its value is never read.

Please remove the unused React import and rerun:

pnpm --filter @oversync/frontend exec tsc --noEmit
pnpm --filter @oversync/frontend test -- --run
pnpm --filter @oversync/frontend build
git diff --check origin/master...HEAD

One behavioral note while you are touching it: DiligenceSnapshot.tsx currently falls back to a hard-coded production coordinator health URL when VITE_API_BASE_URL is unset but import.meta.env.PROD is true. For a reviewer-facing diligence panel, it would be safer to show Not configured unless the app config explicitly provides the coordinator URL, or to derive it from a documented env value. That avoids linking reviewers to a stale or unrelated deployment.

[karagozemin]

Thanks for the PR. I rechecked the merge ref after the latest master update, but it is not merge-ready yet.

Command run:

git diff --check master...pr-199-merge

Result:

frontend/src/components/DiligenceSnapshot.test.tsx:87: trailing whitespace.
frontend/src/components/DiligenceSnapshot.tsx:18: trailing whitespace.
frontend/src/components/DiligenceSnapshot.tsx:20: trailing whitespace.

Please strip the trailing whitespace and push an update. After that I will re-run the frontend tests/build and verify the snapshot panel stays aligned with the investor/demo evidence surfaces already on master.

[Oyinkans0la12]

Thanks for the PR. I rechecked the merge ref after the latest master update, but it is not merge-ready yet.

Command run:

git diff --check master...pr-199-merge

Result:

frontend/src/components/DiligenceSnapshot.test.tsx:87: trailing whitespace.
frontend/src/components/DiligenceSnapshot.tsx:18: trailing whitespace.
frontend/src/components/DiligenceSnapshot.tsx:20: trailing whitespace.

Please strip the trailing whitespace and push an update. After that I will re-run the frontend tests/build and verify the snapshot panel stays aligned with the investor/demo evidence surfaces already on master.

I've resolved all pending issues; kindly review and merge please.

[karagozemin]

Thanks for the PR! The code builds fine locally ✅, but GitHub reports merge conflicts with the base branch. Could you rebase onto the latest master and resolve the conflicts? Once it's mergeable I'll get it merged. 🙏

[Oyinkans0la12]

Thanks for the PR! The code builds fine locally ✅, but GitHub reports merge conflicts with the base branch. Could you rebase onto the latest master and resolve the conflicts? Once it's mergeable I'll get it merged. 🙏

i've resolved the conflicts, please review.