Skip to content

v17 verification tracker — browser-verify every user-facing change in the 17.0.0 train #3909

Description

@os-zhuang

Tracking issue for end-to-end browser verification of the v17 (17.0.0-rc) train, per the release plan. A dedicated agent will work through this checklist against a running app (PORT=3000 pnpm dev showcase + :5180 objectui dev server where UI-side, or the dogfood-verification flow), acting as a real admin/user. Check items off as they are verified; file a separate issue for every failure found and link it here.

Sources of truth: the curated release page content/docs/releases/v17.mdx, the 300+ pending changesets in .changeset/, and the objectui window cf2d56e32a11 → 4a4829d0ef39 (incl. the backfilled range 2cb8d78e24ad...c6cfdf1288b6, see PR #3908). The docs-sweep log lives at docs/v17-docs-sweep.md.

A. Breaking behavior — verify the new posture actually enforces

B. Removed surfaces — verify they are actually gone (and loud)

C. New capabilities — verify they work end-to-end

D. Docs verification (site)

E. Known out-of-scope items already logged

  • Spec comment drift: core-services.zod.ts 'ai' member comment still says "NLQ, Chat, Suggest, Insights" (comment-only, spec-touching PR).
  • content/docs/releases/implementation-status.mdx predates the v17 window; needs its own regeneration pass.
  • RC exit: after changeset pre exit, re-check the v17 page's version wording and this checklist's remaining items.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions