@shivaedev/create-app 0.35.0 → 0.37.0

package/CHANGELOG.md

@@ -1,5 +1,35 @@
 # Changelog
 
+## 0.37.0 - 2026-11-02
+
+### Added
+
+- Generated apps select and sync the story-testing skill from `@shivaedev/skills`, link their agent guide to the local copy and check managed skills during lint.
+
+### Fixed
+
+- Refresh the application's lockfile during `create-app update` even when CI freezes installs by default.
+- Include authentication email and session sweep queues in Jobs administration in full and minimal generated apps, using shared foundation queue declarations for producers, workers and administration.
+- Preserve `shivaedevSkills` when preparing full and minimal app manifests.
+- Leave starter deletions of customized app files as Git modify/delete conflicts, preserving app contents and applying the rest of the starter delta. Record the applied generator version and explain how to keep or delete each conflicted file.
+- Generated apps apply the host's replacement Layer to module ports before binding services, including the notes source, rate-limit store and job queue.
+- Note creation, import and edits commit with their word-count enqueue. An enqueue failure rejects the request and rolls back the note write.
+
+## 0.36.0 - 2026-11-02
+
+### Added
+
+- Add `redactBrowserText` to mask quoted browser literals, including escaped quotes and multiline content, while preserving diagnostic shape and the existing server text policy.
+- Add opt-in `browserErrors` settings for an Error log per report, signed-in `user.id` attribution and session enforcement. The starter enables all three.
+
+### Fixed
+
+- Mask browser report messages and stacks before they reach diagnostic sinks and record reports at Error severity.
+- Apply starter updates to apps inside enclosing Git repositories while preserving sibling files and unrelated staged changes. Keep the generation record unchanged when a nonempty starter delta applies no changes.
+- Generated notes apps show an alert when adding or saving a note defects, keep the draft, and handle delete completion in the note's own action.
+- Generated Railway workers receive shared `RESEND_API_KEY`, `EMAIL_FROM` and `PUBLIC_URL` settings. Production workers require an explicit email sender at startup; deployment instructions describe queued auth email delivery and the worker's production settings.
+- Generated starter stories settle through screen pending signals and completed HTTP/live results instead of status markup or timed connection sampling. Remove the redundant third-party session lifecycle fixture and its teardown delays.
+
 ## 0.35.0 - 2026-11-01
 
 ### Added

package/README.md

@@ -48,9 +48,13 @@ Run `pnpm run setup` after cloning the generated repository to install dependenc
 
 `pnpm dev` first runs `pnpm db:setup` to prepare both databases through `@shivaedev/local-postgres`. Have local PostgreSQL 18.6 on port 55432 or Docker available; see [local-postgres machine setup](https://github.com/ShivaeDev/platform/tree/main/packages/local-postgres#install-and-machine-setup). `pnpm test` loads `TEST_DATABASE_URL` from `.env.local`.
 
+The app selects `story-testing` from `@shivaedev/skills`. Setup syncs the installed instructions to `.agents/skills/story-testing/`, and `AGENTS.md` links to that local copy. `pnpm lint` rejects edits to managed skills. After changing the skills dependency, run `pnpm skills:sync` and commit the copies and manifest.
+
 ### Take starter updates
 
-Run `pnpm dlx @shivaedev/create-app@latest update` in a generated app with a clean Git working tree to take later starter changes. The command reads `.create-app.json`, downloads the recorded generator’s starter and uses Git’s three-way merge to replay its changes against the current starter; app edits survive, deleted files stay deleted, and conflicts are listed and left for you to resolve. Once the starter changes apply, including a merge with conflicts, `.create-app.json` records the current generator version. The command runs `pnpm install` and the app’s `pnpm run typecheck`, lists every non-ignored file with conflict markers and any unresolved Git conflicts, and exits nonzero while those or either check’s failures remain. Resolve the reported problems and rerun install and typecheck before committing. If pnpm reports a trust downgrade, the command preserves the rejected package and version and gives `pnpm update --depth Infinity` to re-resolve transitive dependencies under the existing trust policy; an exact manifest or catalog pin must first be changed to a trusted version. An update adds the admin Users registration and route to an app that lacks them, and lists conflicts where the app customized those parts.
+Run `pnpm dlx @shivaedev/create-app@latest update` in a generated app with a clean app directory in Git to take later starter changes. Apps inside an enclosing repository receive the changes within their own directory; sibling files and unrelated staged changes stay untouched. Only the app directory must be clean. A nonempty starter delta that applies no changes fails without advancing `.create-app.json`. The command reads `.create-app.json`, downloads the recorded generator’s starter and uses Git’s three-way merge to replay its changes against the current starter; app edits survive, deleted files stay deleted, and conflicts are listed and left for you to resolve. Once the starter changes apply, including a merge with conflicts, `.create-app.json` records the current generator version. The command runs `pnpm install` and the app’s `pnpm run typecheck`, lists every non-ignored file with conflict markers and any unresolved Git conflicts, and exits nonzero while those or either check’s failures remain. Resolve the reported problems and rerun install and typecheck before committing. If pnpm reports a trust downgrade, the command preserves the rejected package and version and gives `pnpm update --depth Infinity` to re-resolve transitive dependencies under the existing trust policy; an exact manifest or catalog pin must first be changed to a trusted version. An update adds the admin Users registration and route to an app that lacks them, and lists conflicts where the app customized those parts.
+
+When the starter deletes a file you customized, the command lists its path and leaves a Git modify/delete conflict with your contents intact. Other starter changes still apply, including text conflicts that need resolution, and the generation record advances to the current generator version. Keep the customized file with `git add -- <path>`, or accept the starter’s deletion with `git rm -- <path>`. Resolve any text conflicts, rerun install and typecheck, then review and commit the update.
 
 ### Reuse the generator