@focusbc/bbs-lib 0.0.2 → 0.0.4

package/{readme.md → README.md}

@@ -58,13 +58,13 @@ From the repository root you can also run:
 yarn bbs-lib build
 ```
 
-The build output is generated under `dist/`. Only `dist/**/*` and this README are included in the published npm package.
+The build output is generated under `dist/`. Only `dist/**/*` and this README are included in the published npm package. The `demo/` and `sandbox/` folders are **not** published (see `package.json` `"files"` and `.npmignore`).
 
 ---
 
 ## Sandbox (local manual testing)
 
-A small static page under `sandbox/` can be used to test `MapOverlay` against the integration API BBS endpoints.
+A small static page under `sandbox/` can be used to test `MapOverlay` against the integration API BBS endpoints. Unlike `demo/`, the sandbox bundles the **local library source** from this repo.
 
 1. Copy `sandbox/config.example.ts` to `sandbox/config.ts` and set:
    - `INTEGRATION_API_BASE` — for example, `http://localhost:5016`
@@ -91,6 +91,24 @@ Open `http://localhost:5173`, select an event, then a site. The overlay calls `M
 
 ---
 
+## Client demo
+
+The client-facing reference implementation lives in [`demo/`](demo/). It installs `@focusbc/bbs-lib` from **npm** (not the local `src/` or `dist/` in this repo) and bundles with esbuild. See [`demo/README.md`](demo/README.md).
+
+From this directory:
+
+```bash
+yarn demo:serve
+```
+
+Or from the repository root:
+
+```bash
+yarn bbs-demo:serve
+```
+
+---
+
 ## Releasing the library
 
 The release process is handled by `bbs-lib/scripts/release-lib.sh` and can be started from inside `bbs-lib/`:
@@ -122,24 +140,6 @@ yarn release:bbs-lib
 3. Your Google Cloud user must be able to decrypt/encrypt with the existing KMS key used by `auxiliary/scripts/decrypt_file.sh` and `auxiliary/scripts/encrypt_file.sh`.
 4. `bbs-lib/.npmrc.enc` must exist. This is the encrypted version of the npm credentials file and is the only credential file that should be committed.
 
-### Creating `bbs-lib/.npmrc.enc` for the first time
-
-Create a temporary plaintext `bbs-lib/.npmrc` file:
-
-```ini
-//registry.npmjs.org/:_authToken=<NPM_TOKEN>
-```
-
-Then encrypt it using the repository KMS helper and remove the plaintext file:
-
-```bash
-cd bbs-lib
-bash ../auxiliary/scripts/encrypt_file.sh .npmrc .npmrc.enc
-rm .npmrc
-```
-
-Commit `bbs-lib/.npmrc.enc`. Do **not** commit `bbs-lib/.npmrc`.
-
 ### What happens during release
 
 When you run `yarn release:lib`, the script:
@@ -148,7 +148,8 @@ When you run `yarn release:lib`, the script:
 2. Bumps `package.json` using `npm version <patch|minor|major> --no-git-tag-version`.
 3. Builds the package with `npm run build`.
 4. Publishes the package to `https://registry.npmjs.org/` with `npm publish --access public`.
-5. Re-encrypts the temporary `.npmrc` back into `.npmrc.enc`.
-6. Removes the plaintext `.npmrc` from disk.
+5. Uploads `dist/browser/bbs-lib.js` to Cloud Storage at `gs://bbs-lib-bucket/bbs-lib` (override with `BBS_LIB_BUCKET_URI` or `BBS_LIB_BUCKET`).
+6. Re-encrypts the temporary `.npmrc` back into `.npmrc.enc`.
+7. Removes the plaintext `.npmrc` from disk.
 
 If the release fails after the version bump, review `package.json` before retrying because the version may already have been changed locally.