next.js

6f98e9fc - [test] Isolate deploy e2e revalidation scope per suite (#100718)

[test] Isolate deploy e2e revalidation scope per suite (#100718) `revalidatePath`/`revalidateTag` invalidate cache at Vercel **project** scope, not per deployment. Deploy e2e suites share one project per matrix dimension, so concurrent suites could purge each other's cache entries: `app-static` and `actions` both used the tags `thankyounext`/`justputit`, and several suites revalidated `/`. The deploy manifest recorded the fallout as known-failed tests. - Prefix cache tags with their suite slug: `actions:*`, `app-static:*`, `revalidatetag-rsc:*`, `use-cache-after-uncached-io:*`, `use-cache-custom-handler:*` - Move `parallel-routes-revalidation` under `/prr` and `actions-discarded-navigation-revert` under `/adr` so no deploy-active fixture revalidates `/`; retarget navigation's popstate-revalidate action to its own subtree and prefetch-inlining's default revalidate path to its own route - Give the cache-components deploy job (`build_and_test.yml`) its own Vercel project (`vtest314-e2e-tests-cache-components`) via a new `VERCEL_TEST_PROJECT` override in `next-deploy.ts`, so its suites can't interfere with the plain deploy job's suites; the weekly project-reset cron keeps the new project fresh - Remove the healed known-failed entries from the deploy manifest and add the `increment to trigger deploy tests` marker so the PR deploy jobs exercise the affected suites - `app-static`: assert cache persistence on a suite-unique route in deploy mode (the `/` check can still observe foreign root-layout purges from `vary-params-base-dynamic`, whose project-wide purge is its test subject and can't be renamed), and fix the persistence loop never recording `prevData` ## Verification CI <!-- NEXT_JS_LLM --> --------- Co-authored-by: Claude Code <noreply@anthropic.com>