v4.1.1

Patch release fixing two plugin-mode install friction points and tightening the install-time UX. No breaking changes — drop in via `composer update tallcms/cms`.

Fixed

Plugin-mode page editor 500 (#63)

Editing a Page or Post in plugin mode would crash with `Illuminate\Foundation\ViteException: Unable to locate file in Vite manifest: resources/css/filament/admin/preview.css`. That entry only exists in standalone TallCMS's `vite.config.js`; plugin-mode hosts don't have it.

The fix ships a pre-built `tallcms-preview.css` (~255 KB, daisyUI block-preview scoping) in the package's `resources/dist/` and registers it through Filament's asset system in plugin mode. Standalone continues to use its existing `@vite` path so dev hot-reload while iterating on `preview.css` keeps working — both modes are gated so you never get a double-load.

A new `ViteManifest::hasEntry()` helper guards the `@vite` call in the rich-editor view, with full Blade-level regression coverage (manifest absent → guard skips; manifest present → guard runs).

Install-time warning when host Vite manifest is missing (#62)

Plugin-mode adopters running `php artisan tallcms:install` would hit `ViteManifestNotFoundException` the moment they opened the admin, because the host app's Vite manifest hadn't been built. Generic Filament behavior, but the timing made it look like TallCMS was broken.

`tallcms:install` now checks for `public/build/manifest.json` at the end of its run and emits a clear warning with the exact `npm install && npm run build` commands when missing. Silent when the manifest exists.

Docs

• `docs/gs-installation.md` — new Step 6 covering frontend asset build, plus two Common Pitfalls entries for the Vite errors above
• Package README — adds the Node 20+ requirement that was previously only in the root README

Out of scope (deferred)

• Auto-edit installer ergonomics for HasRoles + plugin registration. Same-process re-check is unreliable because the User class and Filament panels are already loaded by the time the installer wants to verify; needs its own design with an "edit then exit, ask user to rerun" flow.
• Laravel 13 support. Still upstream-blocked on `lazychaser/laravel-nestedset` — see #61.