[SCF high][easy] Add frontend diligence snapshot panel for deployment proof

[karagozemin]

Why this matters

SCF reviewers and investors should be able to see the live OverSync proof points without digging through README tables. This is a small frontend-only feature that turns existing deployment facts into an investor/SCF-ready evidence surface.

Scope

Add a compact Diligence snapshot panel to the frontend that shows:

• current public mode: testnet-only vs mainnet-enabled flag;
• Sepolia HTLC address with explorer link;
• Sepolia ResolverRegistry address with explorer link;
• Stellar testnet HTLC contract with Stellar Expert link;
• Stellar testnet ResolverRegistry contract with Stellar Expert link;
• coordinator status link if configured;
• short copy: No validator set, no attester, HTLC refund path.

Prefer deriving values from existing config/deployment files instead of hard-coding new constants in the component.

Suggested files

• frontend/src/App.tsx
• frontend/src/config/networks.ts
• deployments.testnet.json
• optional new component under frontend/src/components/

Acceptance criteria

• Panel is visible in testnet mode without requiring wallet connection.
• All displayed explorer links are clickable.
• Empty/missing config values degrade to Not configured instead of throwing.
• No swap or settlement semantics change.
• pnpm --filter @oversync/frontend build passes.

[Killerjunior]

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

Hi, I would love to work on this issue. Kindly assign.

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

[Kappa16]

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

PLEASE maintainer..I can handle this issue FAST and professionally before the deadline TM EXPECT PR ASAP

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

[Shecodes174]

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

Hi Maintainer I have read the description and I can resolve this issue please kindly assign to me.

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

[temisan0x]

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

Good day team, please i’d like to take on this issue

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

[tecmalik]

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

Please assign me to this issue

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

[Oyinkans0la12]

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

Can I work on this please?

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

[shogun444]

@shogun444 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.
I've contributed to Rust, TypeScript, backend, frontend, and smart contract projects, with a focus on delivering focused, well-tested changes. I'll keep the implementation within the requested scope, preserve existing behavior unless the issue requires otherwise, include the necessary tests and documentation, and submit a PR that's straightforward to review.
Portfolio: https://portfolio-amber-one-v8ggyhsjyr.vercel.app/ • ETA: ~2 hours.

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

[DTriple-p]

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

Hi there, I'd like to work on this issue.

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