fix(create): context-aware hint on the built-in escape-hatch entry

The escape-hatch entry's hint read
"Use defaults (monorepo / application / library / generator)" in all
contexts. Two problems inside an existing monorepo:

- `vite:monorepo` gets refused at scaffold time ("Cannot create a
  monorepo inside an existing monorepo", bin.ts:468-472).
- `vite:generator` is never part of `getInitialTemplateOptions` —
  it's only reachable via an explicit `vp create vite:generator`.

So the hint was over-promising. Now it mirrors what
`getInitialTemplateOptions(isMonorepo)` actually offers:

- outside a monorepo: "Use defaults (monorepo / application / library)"
- inside a monorepo:  "Use defaults (application / library)"

RFC examples updated to match, plus a one-sentence note explaining
that the hint is context-aware.

Author: fengmk2

packages/cli/src/create/org-picker.ts

@@ -44,10 +44,16 @@ export async function pickOrgTemplate(
     label: entry.name,
     hint: entry.description,
   }));
+  // Mirror `getInitialTemplateOptions(isMonorepo)`: `monorepo` is hidden
+  // inside an existing monorepo (and would be rejected at scaffold time
+  // anyway); `generator` isn't part of the builtin picker at all.
+  const builtinHint = opts.isMonorepo
+    ? 'Use defaults (application / library)'
+    : 'Use defaults (monorepo / application / library)';
   options.push({
     value: BUILTIN_ESCAPE_VALUE,
     label: 'Vite+ built-in templates',
-    hint: 'Use defaults (monorepo / application / library / generator)',
+    hint: builtinHint,
   });
 
   const picked = await prompts.select({

rfcs/create-org-default-templates.md

@@ -395,9 +395,15 @@ templates" entry. Selecting it drops the user into the existing
   server     Server template (Node + Fastify)
   library    TypeScript library template
   ──────────────────
-  › Vite+ built-in templates   Use defaults (monorepo / application / library / generator)
+  › Vite+ built-in templates   Use defaults (monorepo / application / library)
 ```
 
+The hint trailing "Vite+ built-in templates" matches what
+`getInitialTemplateOptions` actually offers for the current workspace
+context — inside an existing monorepo the hint reads "Use defaults
+(application / library)" since `vite:monorepo` is filtered out and
+`vite:generator` isn't part of the picker.
+
 Rules:
 
 - The escape-hatch entry is appended by Vite+, not by the org manifest. It
@@ -449,7 +455,7 @@ below), followed by a trailing **Vite+ built-in templates** entry (see
   server    Server template (Node + Fastify)
   library   TypeScript library template
   ──────────────────
-  › Vite+ built-in templates   Use defaults (monorepo / application / library / generator)
+  › Vite+ built-in templates   Use defaults (monorepo / application / library)
 ```
 
 ### Context-aware filtering