[xuelink]

Part of the plan in langx/langx#2067 (item 0).

Copilot is open to every account with a verified email, as a beta, since 25 October 2026 (langx/langx d75edd924 took the allow-list off; flags.copilotEnabled is on in production). The API meters both plans: copilotPer24h gives Free a daily allowance and Pro a larger one, and only guests and unverified emails are refused (requireVerifiedEmail on every Copilot route). CLAUDE.md says a change in what a plan includes is copied by hand to the site, so langx.io stops listing Copilot as a Pro feature.

What changes

• Undoes 770b77e (Copilot: part of Pro, as a beta #297) and goes back to the reviewed Copilot: a beta on Free and Pro, four helps, honest about what is sent #295 wording: "a beta on Free and Pro". This covers the FAQ answer (also on /faq and in llms.txt), the /plans FAQ, the /compare FAQ, WelcomeBack, the features card (the Pro tag comes off) and the blog lines.
• /plans: the Copilot row is Copilot · Beta, "Daily allowance" on Free and "Larger allowance" on Pro. The row had been a dash on Free and "Beta" on Pro. There are no numbers, so there is no third copy of PLAN_LIMITS to drift.
• Dated notes are not rewritten. The "Update, 25 October 2026" notes in the v2 post and the AMA post still say what they said (part of Pro), and each is followed by a new "Update, 26 October 2026" note: Copilot is on Free as well as Pro, for every account with a verified email, and Pro's daily allowance is larger.
• Privacy policy §2.6 now says who can use Copilot: every account with a verified email address, not guest accounts. The provider naming and the description of what each help sends are unchanged. Effective date 26 Oct 2026. §10.7 and the Terms are not touched.
• PRODUCT.md and the SEO writing guide get the rule back. PRODUCT.md also says never to present Copilot as a Pro feature ("part of Pro", "Pro only", "get it with Pro"), gives 25 October 2026 as the day it opened to everybody, and says a dated note stays as written, with a newer note after it.
• The comment in plans.ts no longer compares the row with the app's paywall, because the paywall is changing in the same plan.

Verified

• npm run check: 0 errors, 0 warnings.
• npx vite build, then npm run postbuild for the sitemap and markdown, and npx vitest run: 44 of 44 tests pass, including the build-output guards.
• The prerendered /plans shows the row as "Copilot · Beta | Daily allowance | Larger allowance".
• The built /privacy-policy (HTML and .md) shows the new §2.6 sentence and "Effective Date: 26, Oct 2026". The built v2 and AMA posts show the 25 October note unchanged, then the 26 October note.
• prettier --check and eslint flag nothing new. PrivacyPolicy.md already fails prettier --check on main; this PR does not change that. The full-repo npm run lint already fails on main, in 17 files (prettier) and in tools/+page.svelte (eslint).

Not verified

• No Cloudflare Pages preview was opened, and no page was viewed in a browser. This is a copy-only change.
• Copilot is drawn in the v3 thread (flags.v3Home). Whether every account is on the v3 look was not checked in this PR.

🤖 Generated with Claude Code