home: a Get started front door, frames that boot on a click, and no 404 poll

The t27.ai home has three problems.

It is overloaded. It was measured live on 2026-10-04. One scroll through the page:
- mounts four same-origin copies of the whole app as iframes (the Spec Explorer, and the kanban, factory and agents boards);
- plus three light app.t27.ai bridge frames;
- makes 218 requests and decodes about 8 MB;
- is 17,898 px tall.
Every board copy polls the supervisor on its own.
The console fills with errors. Every Queen instance polls two supervisor routes that do not exist: /queen/public-modules every 15 s and /queen/public-foundation every 60 s. Each poll prints a 404.
- curl on 2026-10-04 confirms both 404. /queen/status and /queen/public-board answer 200.
- Each part already falls back to the vendored file, so the data on screen is correct. The 404 is pure noise, repeated forever.
There is no front door by kind of visitor. Compute networks open with a "Get started" row: a developer, a host, a contributor. The home names only the developer's moves (HOW TO PLAY), further down.

Acceptance

A GET STARTED block, right under the hero, with three cards (en + ru). Each button opens a place that works today:
- I write code: the Spec Explorer on hello_world.t27.
- I bring hardware: MY RUNNERS.
- I contribute: the board.
What a card cannot back is said on the card, in the words of the place that owns the fact:
- the runner's next stage comes from MY RUNNERS;
- TRI's testnet status comes from the TOKEN tab;
- GPU/FPGA rental for TRI is marked as planned.
The module and Spec Explorer frames on the home boot on a click, not on scroll. Until then the frame shows what it holds and the button.
A wire route that answers 404 is asked once per page, not on every poll; a 5xx is still retried. A contract holds both behaviours.
The home's spec count no longer fetches the 2 MB manifest a second time.