chore(sync): record two upstream infrastructure commits as not applicable

[IgorShevchik]

Records nuxt/ui@68cc4eb4 and nuxt/ui@b2cb53f8 as n/a. They are contiguous in upstream's history, so they share a PR per .sync/PORTING.md §6 step 4b.

Journals: 68cc4eb4…md · b2cb53f8…md

---

68cc4eb4 — cancel vercel previews of other release branches

Rewrites scripts/vercel.sh, Vercel's ignored build step hook:

-if [[ "$VERCEL_GIT_COMMIT_REF" == "v2" || "$VERCEL_GIT_COMMIT_REF" == "v3"  ]] ; then
+if [[ "$VERCEL_ENV" != "production" && "$VERCEL_GIT_COMMIT_REF" =~ ^v[0-9]+$ ]] ; then

Each release branch is the production branch of its own Vercel project, so it
should not also build as a preview of another. Same v5 groundwork as 2aa1702a
(#596).

Why it does not apply

• scripts/vercel.sh does not exist. scripts/ holds
  indistinguishable-snapshots.mjs, lib, regen-indistinguishable-baseline.mjs,
  sync-skill-manifest.mjs.
• There is no Vercel deployment. The docs ship through deploy.yml —
  Deploy to Pages 📰 — to GitHub Pages, which has no per-branch preview projects
  and no ignored-build-step hook.
• There are no v<N> branches for the new pattern to match.

The three vercel mentions in the tree, and why none is this — a grep does
hit, so worth naming them: docs/modules/md-rewrite.ts is guarded by
!nitro.options.preset.includes('vercel') and dormant under the Pages preset;
docs/app/composables/useAnalytics.ts:1 is a commented-out @vercel/analytics
import; docs/content/templates.yml:19 is a "Deploy to Vercel" button URL in the
templates listing. None reads VERCEL_ENV or VERCEL_GIT_COMMIT_REF, none is
invoked by a build.

---

b2cb53f8 — replace playground job in module workflow

Swaps the playground job in .github/workflows/module.yml for a consumer job.
The old one installed the pkg.pr.new build into playgrounds/nuxt and typechecked;
the new one copies test/fixtures/consumer/{full,minimal} to $RUNNER_TEMP —
outside the checkout, so the root node_modules and workspace cannot leak into
resolution — installs with no lockfile, then prepares, typechecks and builds,
with fail-fast: false. Ten new files carry the fixtures, and the playground's
typescript.tsConfig.paths workaround goes with them.

Why it does not apply

• No .github/workflows/module.yml. The workflows here are ci, deploy,
  npm-publish, pr-title, release-please, release-watchdog, smoke.
• No test/fixtures/, so none of the ten added files has a counterpart.
• The module is tested differently. test:module runs
  vitest run --config vitest.module.config.ts over test/module/
  (fixture/ + module-setup.spec.ts) as an ordinary ci.yml gate step, not as a
  separate workflow against a published preview. There is no pkg.pr.new publish
  here for such a job to consume.
• The removal half does not apply either — playgrounds/nuxt/nuxt.config.ts
  has no typescript.tsConfig.paths block, because the CI install that workaround
  existed for never happens here.

Worth noting

The idea behind the new job — resolve the published package from outside the
workspace, with no lockfile, to catch a missing optional peer — is a real gap
test:module does not cover: it runs against the source tree inside the
workspace. That is a possible improvement to this fork's own testing rather than a
port of this commit, and it is written into the journal so the thought is not lost
with the n/a.

---

Gate

dev:prepare · lint · typecheck · build · test:coverage (353 files, 8067
passed) · test:module — green, first full run on main under pnpm 12.4.2.

.sync/dep-parity.json refreshed; the diff is the cursor line alone.

Cursor advances 61b6d53f → 68cc4eb4 → b2cb53f8, and the 61b6d53f entry is
reconciled with #597 / 3ef9979b.

Still queued: 7c4c6e35 — fix(DashboardNavbar): render title only when defined. That one is a real bug this fork shares (DashboardNavbar.vue:109
renders an unguarded <h1 data-slot="title">), and it ports next.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JS8ypVfQSFzYVZzkTHhURb

---

Generated by Claude Code