feat(flutter): landing page that explains puls3: problem, audiences, how it works, live agents, comparison, Stellar identity and payments, reviews, about us and FAQ

[Pericena]

What

The landing page (S01) only had a headline, two buttons and the "Why Stellar" block. It did not explain what puls3 is, who it is for or how it works. This rewrites it as a product page, keeping the brand: same colors, typography, halftone logo and pulse field.

Sections, top to bottom

1. Navigation: Marketplace, Agent Studio, Docs, GitHub and Open app. Below 1000 px the links move into a menu.
2. Hero: "Build. Discover. Pay. AI agents on Stellar.", with three CTAs (Explore agents → /market, Build an agent → /studio, View documentation → docs/), trust badges, and a live agent from the catalog.
3. Why puls3: the three problems from docs/vision.md (building, finding, paying) and how puls3 answers each.
4. For builders / For hirers: what each side gets, with a link into the app.
5. How puls3 works: an 8-step diagram with an animated pulse. Each step is labelled Live on testnet, In development or Planned, so nothing planned reads as working. Two rows on desktop, a timeline on phones; the pulse is off with reduced motion.
6. Agents you can hire today: up to six agents from the real catalog in a new AgentShowcaseCard: avatar, model, Testnet badge, two-line description, skills, price, rating, on-chain id, and Details / Hire. Loading, error, demo and empty states are kept.
7. Compare: "a typical agent listing" vs puls3, row by row (find, identity, hire, pay, refund, create).
8. Stellar identity and payments: the Identity Registry and Escrow contracts and the first hire's create_job and fund transactions (from feat: wallet connection in Flutter app #25/feat: hire and pay flow in Flutter app #28), each opening StellarExpert, plus "Why Stellar".
9. Reviews: no testimonials are invented. While landingTestimonials is empty, the section invites people to hire on testnet and share feedback. Real quotes, added with permission, render as cards automatically.
10. About us: the team's story (pulse on BNB Chain → puls3 on Stellar, from docs/vision.md), mission, three principles, and the team linked to their GitHub profiles.
11. FAQ: eight expandable questions (real money?, what you need, where the payment goes, what if the agent does not deliver, models, open source…).
12. For developers, final CTA and a footer with product and project links, including the new /brand page.

Phones: smaller type (hero 26 px, section titles 20 px, body 14–15 px), single-column cards, and no horizontal overflow from 320 px.

Honest by design

• Every status, address and hash is real. Planned or in-development steps are labelled, and the hero says "Live on Stellar Testnet".
• No testimonials, logos or metrics are invented. A test checks that landingTestimonials stays empty until real reviews exist.
• All copy lives in lib/src/domain/landing_content.dart, so it can be reviewed and edited in one place.

Files

• lib/src/screens/landing_screen.dart: the container.
• lib/src/domain/landing_content.dart: copy (problems, audiences, comparison, team, FAQ, testimonials).
• lib/src/domain/project_links.dart: repository, docs and evidence links.
• lib/src/ui/molecules/agent_showcase_card.dart.
• lib/src/ui/organisms/landing/: the diagram, the blocks and the shared sections.
• docs/blueprints/wireframes/S01-landing-{1440,390}.png: regenerated.

Verification

[moises-cisneros]

The page is well structured and the "no invented testimonials" test is a good guard. I checked the on-chain evidence: both transaction hashes match the ones in #25 and #28. Two things to fix before merging, both about the "honest by design" promise.

1. Some "Live on testnet" labels do not match main.

• "Create an agent" is live, but the Studio is still behind FakeStudioGateway (drafts in memory, test run and deploy are a labelled demo until #35). It also reads oddly next to "Register its identity" and "Publish" being inDevelopment. It should be inDevelopment.
• "Discover and hire" and "Pay into escrow" are live, but the public web build runs the labelled demo hire until the Pages rebuild (#31 step 1, with the pins from #176). Either say that in the step body ("live on the server, demo on the public web build for now") or mark the hire part inDevelopment.
• "Run the task" is inDevelopment. The server already runs the demo agents on Workers AI for a funded hire. Worth checking against main and aligning, so the diagram does not under-claim either.

2. The copy states in the present tense what the diagram says is not live. The builders list ("Your agent gets an id in the Identity Registry and its own Stellar wallet", "Validation as you type...") and the comparison row "An id and an owner in a Soroban registry" read as shipped, while step 2 says in development. A short "coming" or the same status wording would keep both consistent.

Non-blocking: this is about 2.7k lines in one PR, well over the 400-line budget, and there is no size:exception note. If it is easy to split, landing_content.dart + project_links.dart + the molecule first, then the organisms and the screen, would make the review much lighter.

[cloudflare-workers-and-pages]

Deploying puls3 with    Cloudflare Pages

Latest commit:	54c699c
Status:	✅  Deploy successful!
Preview URL:	https://f0991207.puls3-4lw.pages.dev
Branch Preview URL:	https://feat-landing-page-redesign.puls3-4lw.pages.dev

View logs

[moises-cisneros]

My blocking points are addressed in bf2d818: 'Create an agent' is now inDevelopment, the hire/pay steps say the public web build is a labelled demo until the rebuild, and the builder/comparison/FAQ copy is marked as coming. I also checked that the server submits release and claim_refund at the deadlines, so 'Result and release' as inDevelopment is accurate. The test guarding builder copy is a good addition. The size-exception note is still missing but non-blocking. CI green.