Improve Landing page

Currently we have an About page - let's move the info there to the landing page.

Design a modern style "full-page-scroll" style landing page (each section should be at least the height of the screen) with CTA at the top (which is to paste an issue URL and click submit) and different sections below.

What is the main message?
- Bitcoin allows you to pay for AI without purchasing credits or subscriptions, using micropayments through nostr wallet connect
- Your time costs more than AI (Your time is worth more than a few thousand sats)
- Focus more on the project, less on the code
- Fully open source, powered by Goose and NWC (Link to freepilot source code, goose and NWC pages)
- NON-invasive: no need to give "Act on your behalf" permissions to an external app.

Add other sections based on the existing about page e.g. benefits, features, ...

Add a "how it works" section with screenshots / visualization of the steps (1. Write an issue. 2. Paste the issue URL. 3 Connect wallet. 4. new job created, repo checked out etc. 5. Agent implements the changes. 6. PR created. 7. You review the PR and merge it.

Add a section with a few random PRs that were merged + their cost in tokens and sats

Add a stats section:
- How many PRs from freepilot-bot have been merged
- How much bitcoin freepilot-bot has processed
- How many tokens it has used
- Button to follow the bot on github

Add a section for how to use the tool well:
- Make sure that you write a good issue of what you want done. This tool does not replace human thinking.
- Add an example of a very vague issue vs a well-written issue.

Also add a quotes section:

_"wanted to make a PR to the MCP server. started coding, but then used freepilot and did it in 1862 sats: https://github.com/getAlby/mcp/pull/5/files :slightly_smiling_face:" - Bumi_ (profile is https://github.com/bumi and image can be fetched from https://github.com/bumi.png)

add a footer too. (Labs app made by Alby - https://getalby.com - view source (github link: https://github.com/getAlby/freepilot))

There should be CTA's at the bottom of each section which will scroll to the issue input field and focus it

Start by reading the existing About page and identifying the landing-page entry point. Build the full-page-scroll layout around the issue URL CTA, then cover the requested message, workflow visualization, merged PRs, stats, usage guidance, quote, footer, and section CTAs. Done means the landing page presents these sections and each CTA returns to and focuses the issue input.

Written by the indexing model from the issue text.