docs(rfcs): mark pnpm@11.x as supported (drop WIP)

pnpm v11 has shipped stable (11.0.6) and the snap-test coverage
for it has landed, so it is no longer work-in-progress in the
package-manager support matrix.

Author: fengmk2

rfcs/add-remove-package-commands.md

@@ -866,7 +866,7 @@ $ vp add
 
 - pnpm@9.x [WIP]
 - pnpm@10.x
-- pnpm@11.x [WIP]
+- pnpm@11.x
 - yarn@1.x [WIP]
 - yarn@4.x
 - npm@10.x

rfcs/dedupe-package-command.md

@@ -559,7 +559,7 @@ vp dedupe:run
 
 - pnpm@9.x (WIP)
 - pnpm@10.x
-- pnpm@11.x (WIP)
+- pnpm@11.x
 - yarn@4.x (yarn@2+)
 - npm@10.x
 - npm@11.x (WIP)

rfcs/install-command.md

@@ -800,7 +800,7 @@ VITE_PM=pnpm vp install
 
 - pnpm@9.x
 - pnpm@10.x
-- pnpm@11.x [WIP]
+- pnpm@11.x
 - yarn@1.x
 - yarn@4.x
 - npm@10.x

rfcs/link-unlink-package-commands.md

@@ -753,7 +753,7 @@ $ vp link
 
 - pnpm@9.x
 - pnpm@10.x
-- pnpm@11.x [WIP] (pass `-- --no-frozen-lockfile` to `vp unlink` under CI=true; see snap-tests `command-unlink-pnpm11`)
+- pnpm@11.x (pass `-- --no-frozen-lockfile` to `vp unlink` under CI=true; see snap-tests `command-unlink-pnpm11`)
 - yarn@1.x
 - yarn@4.x
 - npm@10.x

rfcs/outdated-package-command.md

@@ -1005,7 +1005,7 @@ vp outdated --update
 
 - pnpm@9.x
 - pnpm@10.x
-- pnpm@11.x [WIP]
+- pnpm@11.x
 - yarn@1.x
 - yarn@4.x
 - npm@10.x

rfcs/update-package-command.md

@@ -646,7 +646,7 @@ vp update react --range # Updates within semver range
 
 - pnpm@9.x [WIP]
 - pnpm@10.x
-- pnpm@11.x [WIP]
+- pnpm@11.x
 - yarn@1.x [WIP]
 - yarn@4.x
 - npm@10.x

rfcs/why-package-command.md

@@ -986,7 +986,7 @@ vp why react --json  # On yarn
 
 - pnpm@9.x
 - pnpm@10.x
-- pnpm@11.x [WIP]
+- pnpm@11.x
 - yarn@1.x
 - yarn@4.x
 - npm@10.x