docs(1.0): two generators on the /generators subpath DO have an ownable copy

The migration guide called the subpath "the home of the generators that have no
ownable copy" and then listed `routesFileHono` and `namesFile` among them. Both
are ejectable — `meta eject --list` names them, `src/reference/routes-hono.ts`
and `src/reference/names.ts` are the copies, and `meta init` scaffolds `names`.
A reader wiring `namesFile()` from the subpath on that sentence's authority would
conclude owning it was not an option.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01At3v6M6uqECZ2Sb5eUv6YY

Author: dmealing

docs/features/migrations/0.x-to-1.0.md

@@ -286,10 +286,11 @@ Importing the built-in generators from `@metaobjectsdev/codegen-ts/generators`
   `meta init`, you already import the owned copies — no change needed.)
 
 - **The `@metaobjectsdev/codegen-ts/generators` subpath itself is unchanged.** Only those four
-  names left it. It remains the supported home of the generators that have no ownable copy —
-  `promptRender`, `outputParser`, `outputPrompt`, `extractor`, `renderHelper`,
-  `traceHelperFile`, `routesFileHono`, `namesFile`, `callableFile`. If your config imports
-  only those, **there is nothing to do here.** Check with:
+  names left it. It remains the supported home of `promptRender`, `outputParser`,
+  `outputPrompt`, `extractor`, `renderHelper`, `traceHelperFile`, `routesFileHono`,
+  `namesFile` and `callableFile` — most of which have no ownable copy at all, and two of
+  which (`routesFileHono`, `namesFile`) have one you can take with `meta eject` whenever you
+  want it. If your config imports only those, **there is nothing to do here.** Check with:
 
   ```bash
   grep -rn '@metaobjectsdev/codegen-ts/generators' . \