Retire the site/ landing fork now the factory owns motion

[sarthakagrawal927]

Why

This repo and ios-landings both deployed to Cloudflare Pages project motion, so whichever pushed last won and neither could be relied on. The 2026-08-17 note claiming the landing had cut over to the factory was not in effect — production was still served from site/.

It is now. The factory build was deployed to motion.significanthobbies.com, and live HTML is byte-identical to ios-landings/dist/motion/index.html. This tree is the redundant one.

Nothing regressed in the move

The fork's llms.txt was genuinely better than the factory's. It stated the real fit lines:

- Best fit: body-controlled games where an iPhone reads movement on-device and turns it into game input
- Best fit: screen-mirroring phone gameplay to a larger display without uploading camera frames
- Not a fit: cloud-based motion capture or remote pose processing
- Not a fit: games that require transmitting or storing camera frames

plus a ## CLI block — against factory boilerplate derived from the tagline ("Best fit: learning about Motion — Your body is the controller").

Those were ported into ios-landings/products/motion/site.config.ts behind new optional agentFit / agentCli fields before the deploy. The live llms.txt is now byte-identical to what this fork served. _headers, _redirects, openapi.json, index.md, robots.txt and changelog.md were already identical.

Verified after deploy: /, /privacy/, /support/, /llms.txt, /openapi.json all 200.

Also in this PR

• drops the dead check:landing script and its entry in the quality chain
• drops the biome override for site/**/*.astro
• pnpm run deploy still fails on purpose, and now says where the landing actually lives

🤖 Generated with Claude Code