@datalabz_/dashboard-kit 4.0.3 → 4.0.4

package/README.md

@@ -1,7 +1,8 @@
 # dashboard_kit
 
 Source for **DashboardKit**, the hosted JS+CSS bundle every LLM-generated
-dashboard loads from `https://html-ui-kit-master.888drafts.com/`.
+dashboard loads. Each `kit-v*` tag releases it to Cloudflare Pages and npm (see
+[Hosting](#hosting)).
 
 ## What problem it solves
 
@@ -36,15 +37,11 @@ ever added to, never altered (see Rules).
 
 - **`v4` is the current and only live major** — what the authoring guide
   links, what `catalog.html` demos, and the only kit that is published.
-- **`v1`, `v2` and `v3` are deprecated — treat them as gone.** They live in
-  `deprecatedVersions/` for reference only and are not published. Don't move
-  them back, don't publish them, don't cite them in docs or `catalog.html`,
-  and don't copy from them when cutting a new major — start from `v4`.
-  Because they are unpublished, nothing added to these files can reach a
-  browser — a runtime deprecation warning was tried and reverted for exactly
-  that reason. Whatever is live at their CDN URLs is frozen at its last
-  published state and will vanish if the publish step prunes what is no
-  longer published.
+- **`v1`, `v2` and `v3` are deprecated — treat them as gone.** They are not in
+  this repo and are not published. Don't bring them back, don't publish them,
+  don't cite them in docs or `catalog.html`, and don't copy from them when
+  cutting a new major — start from `v4`. Whatever is live at their old
+  888drafts URLs is frozen at its last published state.
 
 A `vN.js`/`vN.css` pair is one served bundle; the repo's per-file line budget
 (AGENTS.md #2) does not apply to it — it cannot be split without changing the
@@ -94,48 +91,68 @@ URLs already pinned by live dashboards.
 - **The SQL gateway is shared across every live kit major** — a wire-format
   change can break dashboards still on older `vN`s in production, not just the
   latest.
-- **Open questions about a feature, change, or bug go in `TODO.md`, not a
-  unilateral decision.** If work surfaces something worth doing but not asked
-  for, ask the user whether to add it to `TODO.md` rather than deciding or
-  acting on it yourself.
+- **Open questions about a feature, change, or bug go in
+  [docs/todo.md](../docs/todo.md), not a unilateral decision.** If work
+  surfaces something worth doing but not asked for, ask the user whether to
+  add it there rather than deciding or acting on it yourself.
 
 ## Cutting a new version (`v{N+1}`)
 
 1. Copy `v{N}.js`/`v{N}.css` → `v{N+1}.js`/`v{N+1}.css`.
 2. Fix the header comment to `/* DashboardKit v{N+1}.js */`.
-3. Update the hardcoded `vN.css`/`vN.js` lines in `serve.mjs`'s startup
-   `console.log` (just the printed URLs — routing itself isn't version-aware).
+3. In [bitbucket-pipelines.yml](../bitbucket-pipelines.yml), add
+   `v{N+1}.js v{N+1}.css` to the `cp` line and stamp `__BUILD__` in
+   `v{N+1}.js` too — **in addition to** `v{N}`, never instead of it. A
+   Cloudflare Pages deploy replaces the whole site, so a major left out of a
+   deploy stops loading for every dashboard pinned to it.
 4. Make the actual change in the new file only.
 5. Update `catalog.html` and the authoring guide's kit links — only once the
    user has accepted the new `vN`.
-6. The previous `vN` stays in the root and stays published. A major moves to
-   `deprecatedVersions/` only when no dashboard loads it any more — every one
-   regenerated on a newer major or deleted — and only by the user's decision,
-   never as part of cutting the next one.
+6. The previous `vN` stays in the root and in every deploy. A major is removed
+   only when no dashboard loads it any more — every one regenerated on a newer
+   major or deleted — and only by the user's decision, never as part of
+   cutting the next one.
 
 ## Hosting
 
-Served from `https://html-ui-kit-master.888drafts.com/vN.{css,js}` — CORS
-open, `Cache-Control: immutable`. What is published is `v4.js`, `v4.css`,
-`wrapper.js`, `wrapper.css` and `catalog.html`, as they are in this directory,
-with `v4.js`'s `__BUILD__` marker replaced by the commit hash so System Info
-can say which build is live. How that gets to the host is not decided yet:
-the old repo's Bitbucket pipeline and its build script did not survive the
-move into this monorepo, and a replacement is pending with the server team.
+Pushing a `kit-v*` tag (`kit-v4.0.3`, …) runs
+[bitbucket-pipelines.yml](../bitbucket-pipelines.yml). It publishes `v4.js`,
+`v4.css`, `wrapper.js`, `wrapper.css` and `catalog.html` as they are in this
+directory, with `v4.js`'s `__BUILD__` marker replaced by the commit hash so
+System Info can say which build is live, to two places:
+
+- **Cloudflare Pages**, project `dashboard-kit` — for BackOffice dashboards,
+  which load `https://dashboard-kit-2n2.pages.dev/vN.{css,js}`. That is a test
+  address on a test account until the company account serves
+  `https://kit.<domain>/`; dashboards made before then keep the test address,
+  so the test project must stay until they are rewritten. Every file is
+  served with `max-age=0, must-revalidate` and an ETag, so a release reaches
+  every dashboard on its next open. CORS is open.
+- **npm** as
+  [`@datalabz_/dashboard-kit`](https://www.npmjs.com/package/@datalabz_/dashboard-kit?activeTab=versions),
+  served by jsDelivr at
+  `https://cdn.jsdelivr.net/npm/@datalabz_/dashboard-kit@<version>/` — for
+  Claude artifacts, which pin an exact version. A published version never
+  changes.
+
+The release log ends with both addresses.
+
+**Every release gets a new tag; never move a released one.** Re-pushing a
+released tag deploys the new code to Cloudflare under the old number, and npm
+refuses to publish over that version, so the two hosts end up serving
+different code for one version.
+
+**Rolling back:** Cloudflare → Workers & Pages → `dashboard-kit` →
+Deployments → the previous deployment → *Rollback to this deployment*. It
+reaches every dashboard on its next open. npm needs nothing: artifacts keep the
+version they pinned.
 
 ## Dev
 
-No build step — edit `vN.js`/`vN.css` directly.
-
-```bash
-npm start       # serve.mjs — dev server on :3400, CORS open
-```
-
-| URL                                                | What it serves                                                                                                                                      |
-| -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `http://localhost:3400/vN.css` / `vN.js`           | Kit stylesheet / runtime for a given major                                                                                                          |
-| `http://localhost:3400/catalog.html`               | Component catalog — demos kit features                                                                                                              |
-| `http://localhost:3400/wrapper.css` / `wrapper.js` | Local harness: hosts a dashboard in a sandboxed iframe and supplies JWT + date/timezone/hierarchy via `postMessage`, standing in for the BackOffice |
+No build step — edit `vN.js`/`vN.css` directly, and open `catalog.html` in a
+browser to see the kit's components. `wrapper.css`/`wrapper.js` are the local
+harness: they host a dashboard in a sandboxed iframe and supply the JWT and
+date/timezone/hierarchy through `postMessage`, standing in for the BackOffice.
 
 To simulate the harness's boot message against a dashboard opened directly:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@datalabz_/dashboard-kit",
-  "version": "4.0.3",
+  "version": "4.0.4",
   "description": "DashboardKit runtime + styles, served from jsDelivr",
   "license": "UNLICENSED",
   "files": [

package/v4.js

@@ -20,7 +20,7 @@
   let _activeTabId = '';
   let _sections = [];   // { id, label, load, loaded, errors }
   let _title = '';
-  let _gitVer = '857821c'; // replaced at deploy: sed -i "s/857821c/$(git rev-parse --short HEAD)/g" v4.js
+  let _gitVer = 'ded6e67'; // replaced at deploy: sed -i "s/ded6e67/$(git rev-parse --short HEAD)/g" v4.js
   let _calls = [];   // System Info call log
   let _sectionErrors = {}; // sectionId → error count
   let _generation = 0;