@bagdja/kumpul 1.0.1 → 1.0.2

package/README.md

@@ -15,7 +15,7 @@ direction and notes about the prototype's sample data and host-managed pages.
 ## Contract
 
 - Package: `@bagdja/kumpul`
-- Version: `1.0.0`
+- Version: `1.0.2`
 - Template slug: `kumpul`
 - `rendererApiVersion`: `1`
 - Entry point: `dist/server.cjs`
@@ -23,8 +23,9 @@ direction and notes about the prototype's sample data and host-managed pages.
 - React: supplied by the Bagdja runtime
 
 The package is kept separate from the production renderer. Publishing a package
-does not publish or activate a template in the runtime registry; registration,
-review, and publication are separate platform steps.
+to npm does not publish or activate it in Bagdja: the platform fetches and
+validates the exact version into staging, then activates it only after the
+separate deep-review approval and release.
 
 ## Development
 
@@ -100,3 +101,13 @@ Bagdja; the local fixture preview is not that approval.
 `npm pack --dry-run` previews the contents to be uploaded to npm without
 publishing anything. The design reference is documentation material and is
 intentionally excluded from the published package.
+
+After review, publish the exact version declared in `package.json`:
+
+```sh
+npm publish --access public
+```
+
+The generated npm package must contain `manifest.json`, `dist/server.cjs`, and
+optionally `dist/client.js`; the platform retrieves those files from npm, so
+reviewers do not upload bundle files manually.