Publish as @schneiderjoseph/devia

[schneiderjoseph]

npm refused the bare name with 403: too similar to degit, dexie and dva. The 404 seen before publishing meant unregistered, not available -- the similarity filter only runs on the PUT. Scoped names skip that filter.

• package.json: name scoped, publishConfig.access=public so the scoped package publishes public without a flag anyone has to remember
• Install lines carry the scope; everything typed afterwards stays devia, the binary name is unchanged. README, MIGRATION, CHANGELOG, 05_FLOWS and the release recipe updated, no bare install left in the tree
• 01_ARCHITECTURE records the decision and why, so no future doc reintroduces npm i -D devia
• 00_OVERVIEW, 02_SURFACES and 06_INTEGRATIONS say what an adopter now types; bare npx devia no longer resolves without the package installed

devia.json keeps project.name "devia": detectName strips the scope, so an adopter of a scoped package still gets a clean project name.

Verified: 32 tests with and without FORCE_COLOR, validate clean, check P0
clear, memory validate clean. Tarball: @schneiderjoseph/devia 0.1.0, 435 files.

Summary

Type

Devia compliance

• Rules touched (IDs):
• New rule? source cited, severity, priority, validation method:
• Breaking for adopters? (rule id, .devia/ layout, CLI contract):
• CHANGELOG.md updated:
• Generated files rebuilt (npm run build:index):

Checks

• npm run validate passes
• npm test passes
• node bin/devia.mjs check --root . passes
• devia init still produces a valid project (devia validate clean in a scratch repo)

Not verified