Publish as @redrob-labs/sdk, the scope the organisation actually owns

[its-janghoon]

The publish authenticated and reached Publishing to https://registry.npmjs.org/, then:

npm error 404 Not Found - PUT https://registry.npmjs.org/@redrob-code%2fsdk - Scope not found

@redrob-code is not an npm organisation. @redrob-labs is — confirmed, registry.npmjs.org/-/org/redrob-labs/user returns 200 where redrob-code returns 404.

An npm package's name is its registry identity, so there is no publishing under one scope while calling it another. The name changes, and because a workspace link resolves by name, every importer changes with it: 121 files.

Only this package is constrained

The eighteen sibling workspace packages keep @redrob-code/*. They are private and never face the registry, so their scope is unconstrained and renaming them would be churn for no gain.

@redrob-code/sdk-next is a different package and deliberately untouched — which is why the replacement carries a negative lookahead rather than matching a prefix.

A first pass was too narrow

It covered packages/ only, and bun install then failed:

error: Workspace dependency "@redrob-code/sdk" not found

The root package.json, the separate github/ workspace and both lockfiles sit outside it. The rename is now driven off git ls-files, so it covers every tracked file whatever its extension and touches nothing ignored.

Verified end to end

bun install       relinks: + @redrob-labs/sdk@workspace:packages/sdk/js
typecheck         0 errors across the monorepo
packages/core     974 pass / 0 fail
packages/redrob   3380 pass / 0 fail
httpapi gate      pass=210 fail=0 skip=0 missing=0
dry run           would publish @redrob-labs/sdk@0.4.1 → redrob-labs-sdk-0.4.1.tgz
                  package.json restored to 0.0.0