Add an English Founder Beta acquisition path

[fly1d]

Summary

• add a complete English product page at /en/
• link Chinese and English pages with visible navigation and hreflang metadata
• state clearly that the signed installer is pending while source builds are available now
• add an English macOS source-build guide
• add a privacy-conscious English Founder Beta issue form
• include both language routes in the sitemap
• cover the English funnel and 320 px layout with browser tests

Risk

• Low: documentation, copy, styles, or isolated dictionary data
• Medium: UI behavior, translation provider, document parsing, or shared API
• High: selection capture, OS permissions, credentials, packaging, or releases

Verification

• npm run check
• npm run test:smoke
• npm run test:site (8 passed)
• English issue-form YAML parsed successfully
• Desktop, 390 px, and 320 px visual inspection
• No API keys, user content, or sensitive logs were added
• Error and fallback states were exercised

Review Notes

The page does not claim that a signed download, users, or payments already exist. It identifies source builds as the current trial path, keeps the one-time Founder offer at CNY 39, explains that the MIT source remains free, and directs applicants away from sharing private source text, documents, email addresses, and API keys.

[fly1d]

Reviewed the complete acquisition diff at bbbf213. The English route uses the existing product screenshot, links back to the Chinese route, and adds canonical/hreflang metadata without introducing scripts, analytics, or third-party assets. It explicitly says the signed installer is pending, offers source builds as the current trial path, keeps the MIT source free, and does not claim existing users or payments. The English issue form excludes private text, documents, email addresses, and API keys. The build guide matches the repository commands and current engine behavior. Automated tests cover both language funnels, desktop/mobile rendering, 320 px overflow, hero-action containment, source instructions, and application links. All local suites and all five protected GitHub checks passed. No blocking findings.