Frontend: Pilot demo path and end-to-end smoke script

[Abiorh001]

Parent: #29
Depends on: #50, #49, #51, #52, #56, #55, #53, #45, #46

Why

The demo week needs a visible end-to-end product path, not only backend scripts. The roadmap says the output is not a demo-only UI, but the frontend still needs a reliable demo path for pilot proof.

Roadmap Source

• contributor onboarding context: quarterly demo-day package and current v0.1 checkpoint
• docs/roadmap_pilot_plan.md
• docs/roadmap_day_by_day_execution_plan.md Days 20-30

Scope

• Define one clickable frontend path: project setup -> task -> worker submission -> checks -> review -> revision/acceptance -> contribution/payment/reputation summary.
• Add smoke/demo script or documented test steps for local maintainer/contributor validation.
• Capture screenshots or demo notes for checkpoint reporting.

Acceptance Criteria

• A maintainer can run the backend and frontend locally and walk through the pilot path.
• The demo path uses real API calls, not hardcoded mock state, except where backend work is explicitly pending and labeled.
• Output can be included in demo-day package.

Contributor Fit

High demo-week value. Good pairing task for frontend + backend contributors.