fix: verify docs after release generation

docs/PUBLISHING.md

@@ -58,11 +58,13 @@ The command performs the remaining release as one guarded workflow:
 2. Publish every missing `@wrnexus/*` package in dependency order. Already-published
    packages are verified and skipped, so an interrupted release can be resumed safely.
 3. Confirm every package is private and run the newly published CLI updater, including its
-   migrations, against `D:\Company\wrnexusjs`.
+   migrations, against `D:\Company\wrnexusjs`. The updater's immediate project check is
+   deferred because its generated docs inputs are rebuilt in the next step.
 4. Align every docs-site dependency, regenerate package pages twice, update
    `public/llms.txt`, `public/llms-full.txt`, the sitemap, and the documentation index.
-5. Run the docs-site check and production build, verify that `public/llms.txt` contains the
-   current version and every framework package, then commit and push the docs repository.
+5. Run the authoritative docs-site check and production build, verify that
+   `public/llms.txt` contains the current version and every framework package, then commit
+   and push the docs repository.
 
 If the documentation checkout lives elsewhere, set `WRNEXUS_DOCS_ROOT` before running the
 publish command. Both repositories must start clean and synchronized with their active