packages/core: publish as @superinstance/quilt-core, and ship dist/

[SuperInstance]

The scope, and why

@quilt/* is not a scope this fleet owns. npm view @quilt/core is a 404 for every package in the family, so any repo depending on it cannot install:

npm error 404  '@quilt/core@*' is not in this registry.

The root package has been republished as @superinstance/quilt-core (0.3.3 is the first publish that is clean in registry metadata: no promoted devDependencies, no dead-scope peer). This PR completes the rename across the whole monorepo.

What changed

All six manifests move to the scope the fleet holds, and every @quilt/* dependency spec becomes a real version range instead of * or file::

package	before	after
core	@quilt/core 0.3.0	@superinstance/quilt-core 0.3.4
sdk	@quilt/sdk 0.2.0	@superinstance/quilt-sdk 0.2.7
cli / mcp / tui / docs	@quilt/{cli,mcp,tui,docs}	@superinstance/quilt-{cli,mcp,tui,docs}

The root build script selects workspaces by name (-w @quilt/core -w @quilt/sdk ...). Renaming the packages without touching it leaves npm run build building nothing, so it moves too. This was not in the brief and would have broken CI silently.

core's peerDependencies on @quilt/ai is dropped, not repointed: core only documents an AIEngine subset in comments and never imports it, so the peer was a claim on a package we cannot install.

The schema import (TS2307 / ERR_MODULE_NOT_FOUND)

packages/sdk/src/index.ts reached the schema with ../../../schemas/manifest.schema.json — outside rootDir. It resolved in-tree, so the monorepo built green, and the emitted dist/index.js kept the same specifier. After publish the tarball has no schemas/ dir, so the import resolved to node_modules/schemas/ — outside the package — and threw:

FAILED: ERR_MODULE_NOT_FOUND | Cannot find module
'.../node_modules/schemas/manifest.schema.json' imported from
'.../@superinstance/quilt-sdk/dist/index.js'

The schema now ships inside the SDK (src/schemas/ -> dist/schemas/), covered by the existing files: ["dist"].

Verified on this branch

npm install                -> exit 0   (228 packages)
npm run build              -> exit 0   (all 5 workspaces)
npm test                   -> exit 0   core 8 files / sdk 79 pass 0 fail / tui 15 pass 0 fail

published-tarball simulation (dist + README.md only, per files):
  import() OK, 23 exports, manifestSchema resolves (draft-07)

sdk@0.2.7 in a publish-shaped copy OUTSIDE the monorepo
(no devDependencies in the manifest, deps only), installed against the
PUBLISHED @superinstance/quilt-core@0.3.3 from the registry:
  npm test -> # tests 79 / # pass 79 / # fail 0

Deliberately out of scope

docs/ guides, landing/ marketing pages, RELEASE-*.md and quilt_worker/quilt_core/* still say @quilt/*. They are prose and vendored build output, not a package boundary; folding them in would bury the rename. Flagged as follow-up doc debt.

Not merged. Left for review.