Rename npm scope across pnpm monorepo and standalone package without breaking workspace publishes

A pnpm monorepo and a separate standalone npm package needed to move from an unavailable npm scope to a new organization scope. The change had to cover package names, workspace dependency references, imports, docs/config templates, lockfiles, generated dist artifacts, and publish metadata while preserving unpublished private workspace packages.