Clarify task and bounty submission flow

[jarlyn95]

Summary

• Clarifies how bounty/task submissions work on the landing page FAQ, including proof-of-work expectations.
• Updates the "Looking for Work" examples to reflect current live Gibwork task types and prize pools.
• Makes the example task rows actionable links with proof metadata and verified-only badges where relevant.
• Refreshes SEO/site description copy around funded tasks, open-source bounties, services, and the Solana-powered marketplace.

Why

The landing page should help first-time contributors understand what work looks like on Gibwork before they open the app. This change replaces stale sample work with current examples and makes the proof/submission path concrete.

Validation

• npm run build

Notes

The visible Vercel status is blocked by the Gibwork team's deployment authorization handoff, not by the local build.

[vercel]

@jarlyn2025 is attempting to deploy a commit to the gibwork Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the landing-page content to reflect new example work items and expands the FAQ to better explain bounties/tasks, payments, and acceptable proof submissions.

Changes:

• Refreshed “looking for” work items (titles and reward amounts).
• Expanded FAQ answers for bounty vs task and payment flow.
• Added a new FAQ entry describing what proof to submit.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
components/looking-for.tsx	Updates sample task titles and USDC reward amounts displayed in the “looking for” section.
components/faq.tsx	Improves FAQ clarity and adds a new “proof to submit” question/answer.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[jarlyn95]

Local verification for the current head commit da952c145e22397bf8df8b5a00d91702e728a907 completed on 2026-06-23:

• npm run build passes locally.
• The visible Vercel failure is the Gibwork team deployment authorization handoff, not a project build failure.

This PR adds a second concrete landing-page improvement for the 350 USDC Gibwork task by making task examples current, linked, and easier to verify.