@simplemodule/tsconfig is referenced by sm-scaffolded projects but not published to npm

[antosubash]

Summary

sm new project and sm new module (CLI v0.0.36) generate package.json with a dependency on @simplemodule/tsconfig@^0.0.36, and per-module tsconfig.json files with \"extends\": \"@simplemodule/tsconfig/base\". But @simplemodule/tsconfig does not exist on npmjs.com — npm view @simplemodule/tsconfig versions returns 404.

The other three @simplemodule/* packages (@simplemodule/client, @simplemodule/ui, @simplemodule/theme-default) are all published at 0.0.36. Only tsconfig is missing.

Net effect: npm install fails immediately on a freshly-scaffolded project.

Repro

dotnet tool install -g SimpleModule.Cli   # 0.0.36
sm new project Repro
cd Repro
npm install
# npm error 404  The requested resource '@simplemodule/tsconfig@^0.0.36' could not be found

Expected

npm install succeeds against a clean scaffold.

Suggested fix

Either:

1. Publish @simplemodule/tsconfig to npm at 0.0.36 (and keep it in sync with the other @simplemodule/* packages on each release).
2. Remove the @simplemodule/tsconfig dependency from the templates and inline the tsconfig content directly into the generated tsconfig.json files.

Option 1 keeps the templates DRY and matches the @simplemodule/client/ui/theme-default distribution model. Option 2 reduces a publish-time coupling but loses centralized config updates.

Environment

• sm --version: 0.0.36
• dotnet --version: 10.0.201
• npm --version: latest stable