epic: the front door still sells 1.0

Why

2.0 shipped a server. crates/flexiq-server binds four listeners — executor attach, the
dashboard, the admission webhook, and flexiq.v1.ProducerService over gRPC and over plain
HTTP with JSON bodies. Nothing a stranger reads says so.

The landing page still sells the 1.0 story: an embedded library, SQLite, three native SDKs.
The docs footer still brands the project taskito — docs/app/components/landing/footer.tsx
renders the word literally. The interactive language tabs offer three SDKs and no server. And
the README claims "the performance of Rust" without a single published number behind it.

The gap is not capability. It is that the capability is invisible to everyone who has not read
the source.

Shape

Six changes, all in docs/ plus one benchmark harness that lives in the repo and is runnable
by anyone:

• a server fold on the landing page, with the curl snippet that works against the JSON facade
• the footer brand fixed
• flexiq-server as a fourth tab beside python / node / java
• reproducible benchmarks, checked in, charted on the landing page
• a server-and-wire documentation tier beside the three SDK tiers
• an operate section that covers tokens, gRPC, scaling and backup, not just container topology

What this is not

Not a docs rewrite. The information architecture landed in #777 / #780 and is sound: the
content tree is already python/, node/, java/, shared/, not python/-for-everything.
What it lacks is a fourth peer for the network door. Add the tier; do not re-cut the three
that exist.

Not a marketing claim without a harness. No number goes on the landing page that a reader
cannot reproduce from a script in this repository.

Start by reading crates/flexiq-server to understand the documented server entry points, then inspect docs/app/components/landing/footer.tsx and the existing docs/ content tree. Done means adding the server landing-page tier, corrected branding, server-and-wire and operate documentation, plus a checked-in benchmark harness whose results are reproducible before they appear on the landing page.