fix(cli): unblock fresh sm new project / sm new module builds

[antosubash]

Summary

Fixes the five open scaffolding gaps that prevent a freshly-scaffolded SimpleModule project from building cleanly.

Closes #148, #149, #150, #151, #152.

Per-issue changes

• sm new module: name-singular collision when module name equals its singular form (e.g. PageBuilder) #148 — entity name collides with module namespace. When the singular form of the module name equals the module name itself (e.g. PageBuilder, Marketplace, Map), the generated entity class shadows the SimpleModule.<Name> namespace and fails CS0118. Added ModuleTemplates.GetEntityName(moduleName) which returns GetSingularName(moduleName) when it differs, otherwise ${moduleName}Item. Wired into NewModuleCommand, NewProjectCommand, NewFeatureCommand, and the reference-template lookups in ModuleTemplates/FeatureTemplates. GetSingularName itself is unchanged so existing tests still pass.

• sm new module: assembly name doesn't match namespace prefix, fails SM0052/SM0053 analyzer out of the box #149 — assembly name doesn't match SM0052/SM0053 expectations. Generated module/contracts/test csproj filenames are <Name>.csproj, but the analyzer expects assemblies named SimpleModule.<Name>. Added a ProjectGroup post-process that injects explicit <RootNamespace> and <AssemblyName> properties when missing, plus baked them into the fallback templates. The csproj filename stays the same so existing structure tests keep passing.

• @simplemodule/tsconfig is referenced by sm-scaffolded projects but not published to npm #150 — @simplemodule/tsconfig not on npm. Removed the @simplemodule/tsconfig dependency from the generated root package.json. Replaced the extends "@simplemodule/tsconfig/base" in both the root and per-module tsconfig.json with the equivalent inlined compilerOptions. npm install now succeeds against a clean scaffold.

• sm new project: missing @tailwindcss/cli dep, breaks SimpleModule.Hosting Tailwind build target #151 — missing @tailwindcss/cli. Added @tailwindcss/cli to the generated root package.json devDependencies (alongside @tailwindcss/vite). The Tailwind v4 split means the tailwindcss package no longer ships a standalone bin, so SimpleModule.Hosting.targets was failing with exit code 127.

• sm new project: Styles/app.css uses monorepo-relative paths that don't resolve for downstream consumers #152 — Styles/app.css monorepo-relative paths. Rewrote HostTemplates.AppCss() to do explicit per-directive substitution rather than blind prefix replacement (the old ../../modules/ → ../../../modules/ rewrite produced an off-by-one ../../../../modules/). Generated app.css now uses node_modules/@simplemodule/{theme-default,ui,client} (3 ups from Styles/) and ../../modules/** (2 ups), matching the actual scaffolded layout.

Verification

• dotnet test for SimpleModule.Cli.Tests: 128/128 passing, including ScaffoldedProject_DotnetBuildSucceeds (the slow end-to-end scaffold + dotnet build against the live source generator).
• Manual sm new project Repro against this branch produces a package.json without @simplemodule/tsconfig, with @tailwindcss/cli, and a Styles/app.css whose paths resolve from src/<Name>.Host/Styles/.
• Manual sm new module PageBuilder in that scaffolded project produces PageBuilderItem entity (no namespace collision) and module/contracts csprojs with explicit <RootNamespace>SimpleModule.PageBuilder</RootNamespace> / <AssemblyName>SimpleModule.PageBuilder</AssemblyName>.

Test plan

• CI green on claude/github-issues-IGNzY.
• After release, repro the original five issues against the next published SimpleModule.Cli and confirm they no longer reproduce.

---

Generated by Claude Code

[cloudflare-workers-and-pages]

Deploying simplemodule-website with    Cloudflare Pages

Latest commit:	017dbd7
Status:	✅  Deploy successful!
Preview URL:	https://754735e1.simplemodule-website.pages.dev
Branch Preview URL:	https://claude-github-issues-ignzy.simplemodule-website.pages.dev

View logs