fix(pricing): align landing actions with subscription state

[Siri-Ray]

Why

The public Pricing page can read the signed-in user's billing summary, but it previously reduced that state to a Personal tier. That made month/year changes, first-month eligibility, pending changes, cancel-at-period-end, and Personal-checkout restrictions look actionable when Vela would reject or reroute them.

This PR makes Landing's catalog an honest preview of the checkout behavior while leaving Vela authoritative for workspace roles, Team subscription mutations, seats, and payment state. It also restores the existing signed-in account avatar and account menu on Pricing only, where subscription context is relevant.

What users will see

• Team plans can switch between monthly and yearly pricing, totals, and checkout targets.
• Signed-in Personal subscribers land on their current billing interval.
• Same-interval tier upgrades remain actionable; tier + interval changes are disabled with guidance to switch back first.
• Same-tier monthly-to-yearly changes remain actionable; yearly-to-monthly changes are blocked with guidance to cancel the subscription first.
• Current, canceling, scheduled, checkout-unavailable, downgrade, and intro-ineligible states have explicit labels and pricing.
• Cancel-at-period-end is shown on the current plan card without a duplicate page-level status banner.
• Signed-in users see their avatar, Console link, and Sign out action in the Pricing header only. Other Landing routes keep the account module disabled.

Surface area

• UI — new page / dialog / panel / menu item / setting / empty state in apps/web or apps/desktop (including Electron menu bar)
• Keyboard shortcut — new or changed
• CLI / env var — new od subcommand or flag, new tools-dev / tools-pack flag, or new OD_* env var
• API / contract — new /api/* endpoint, new SSE event, or changed shape in packages/contracts
• Extension point — new entry under skills/, design-systems/, design-templates/, or craft/, or change to the skills protocol
• i18n keys — added new translation keys (see TRANSLATIONS.md for the locale workflow)
• New top-level dependency — adding any new entry to the root package.json (dependencies or devDependencies); workspace-package package.json files are out of scope. Include a paragraph on what we get vs. what bytes we ship (see CONTRIBUTING.md → Code style)
• Default behavior change — changes what existing users experience without opting in (default model, default setting, file/SQLite schema, auto-network on startup, auto-install)
• None — internal refactor, docs, tests, or translation update only

Screenshots

The review document contains the state matrix and nine screenshots covering default Personal pricing, the Pricing-only account menu, dual changes, Team monthly pricing, a yearly subscriber switching to the Monthly tab, checkout restrictions, scheduled changes, cancel-at-period-end, and the Vela fallback toast:

https://powerformer.feishu.cn/docx/DU1RdSqQRoMxqNxFtCic7huRn7e

Bug fix verification

• Test paths: apps/landing-page/tests/pricing-current-plan.test.ts, apps/landing-page/tests/pricing-contract.test.ts, and apps/landing-page/tests/header-download-cta.test.ts
• Did the test go red on main and green on this branch? yes
• The resolver cases were added red-first for interval upgrades, dual changes, checkout restrictions, scheduled changes, canceling state, and portal availability. The Pricing-only account opt-in contract also failed before the Header/Layout implementation.

Validation

• pnpm --filter @open-design/landing-page test — 198 passed
• pnpm --filter @open-design/landing-page typecheck — 0 errors, 0 warnings, 179 existing hints
• pnpm --filter @open-design/landing-page build:static — 6,739 pages built
• pnpm guard
• pnpm typecheck
• focused post-merge Pricing/header tests — 70 passed
• Browser QA with mocked billing summaries:
  • monthly Go defaults to Monthly; higher same-period upgrades enabled
  • yearly selection enables same-tier conversion and blocks dual changes
  • a yearly subscriber switching to Monthly cannot change the same tier and sees “取消订阅后可变更套餐”
  • Personal checkout restriction disables Personal CTAs while preserving Team handoff
  • Pricing renders avatar, Console, and Sign out; /faq/ renders no account module
  • cancel-at-period-end has no page-level banner and remains visible on the current plan card
• git diff --check

Related

• Review document: https://powerformer.feishu.cn/docx/DU1RdSqQRoMxqNxFtCic7huRn7e
• Companion Vela Draft PR: https://github.com/powerformer/vela/pull/1721

[github-actions]

🚀 Landing page preview

This PR is deployed to a Cloudflare Pages preview — not staging or production:

• Stable alias: https://pr-7239.open-design-landing-staging.pages.dev
• This build: https://6a30d843.open-design-landing-staging.pages.dev
  Updated for commit 73ef783.

[lefarcen]

Saw the draft — keeping /pricing/ aligned with the live billing state and limiting the account chrome to that route looks like the right direction. We can do the full pass once this is marked ready for review.

[lefarcen]

Ready for review noted — leaving the current head with @mrcfps for the code pass.

[mrcfps]

@Siri-Ray thanks for the careful Pricing subscription-state work — this is a solid fix.

I reviewed the changed ranges across the resolver (resolvePersonalPlanAction / loadPersonalPricingContext), Pricing page CTA wiring (interval sync, intro eligibility, disable/re-enable + syncCtas), Team monthly/yearly checkout labels, and the Pricing-only account opt-in. The action matrix matches the stated product rules (same-interval upgrades, monthly→yearly, blocked dual changes and yearly→monthly, scheduled/canceling/checkout-unavailable), href restoration after re-enable looks correct, and the focused red-spec coverage plus header/Pricing opt-in contracts give good confidence.

No actionable correctness, safety, or maintainability issues on this head. Nice job landing a clear preview of Vela’s boundaries without overreaching into Team/workspace authority.

_{🔁 Powered by Looper · runner=reviewer · agent=opencode · An autonomous AI dev team for your GitHub repos.}