@bagdja/kumpul 1.0.1 → 1.0.3

package/README.md

@@ -15,16 +15,18 @@ direction and notes about the prototype's sample data and host-managed pages.
 ## Contract
 
 - Package: `@bagdja/kumpul`
-- Version: `1.0.0`
+- Version: `1.0.3`
 - Template slug: `kumpul`
-- `rendererApiVersion`: `1`
-- Entry point: `dist/server.cjs`
+- `manifestVersion`: `1`, `rendererApiVersion`: `1`
+- Entry point: `dist/server.cjs` (wajib) dan `dist/client.js` (JavaScript browser), dinyatakan di `manifest.entry`
+- Halaman contoh untuk website baru: `manifest.defaultPages` (Beranda, Katalog Gathering, Cara Kerja, Tentang)
 - Export: `render(props)`, returning a React element
 - 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
 
@@ -92,11 +94,21 @@ from it, then replace the renderer and fixtures while preserving the package
 and manifest contract. The local preview is a development aid, not a substitute
 for Bagdja Studio/reviewer preview or the isolated production runtime.
 
-The runtime's optional `client_bundle` capability is approval-gated. Review
-and approve the exact package version before enabling its browser bundle in
-Bagdja; the local fixture preview is not that approval.
+`dist/client.js` dibaca reviewer Bagdja sebelum versi disetujui; setelah
+terbit, JavaScript ini berjalan di semua halaman website seller di dalam iframe
+sandbox. Preview fixture lokal bukan persetujuan tersebut.
 
 `npm run build` builds the package; `npm test` checks the renderer, and
 `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.