@datalabz_/dashboard-kit 4.0.4 → 5.0.1

package/README.md

@@ -30,20 +30,24 @@ API reference. The SQL gateway the kit calls is
 
 ## Versions
 
-Each major is a separate, self-contained `vN.js`/`vN.css` pair, **pinned by
-URL from every dashboard generated against it** — those dashboards keep
-loading it indefinitely, so a shipped `vN` is a live dependency that is only
-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.
+Each major is a separate, self-contained bundle, **pinned by URL from every
+dashboard generated against it** — those dashboards keep loading it
+indefinitely, so a shipped `vN` is a live dependency that is only ever added
+to, never altered (see Rules). Up to `v4` a major is a `vN.js`/`vN.css` pair;
+from `v5` on it is `vN.js` alone, carrying its own CSS, because Claude artifacts
+can load scripts from jsDelivr but not stylesheets.
+
+- **`v5` is the current major** — what the authoring guide links and what
+  `catalog.html` demos.
+- **`v4` stays live** and in every release: every dashboard made before `v5`
+  loads it.
 - **`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.
+  cutting a new major — start from the current one. 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
+A major's files are 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
 URLs already pinned by live dashboards.
 
@@ -98,13 +102,15 @@ URLs already pinned by live dashboards.
 
 ## Cutting a new version (`v{N+1}`)
 
-1. Copy `v{N}.js`/`v{N}.css` → `v{N+1}.js`/`v{N+1}.css`.
+1. Copy `v{N}.js` → `v{N+1}.js`. From `v5` on there is no CSS file to copy: it
+   lives in the `DK_KIT_V{N}_CSS` string inside the JS, renamed for the new
+   major.
 2. Fix the header comment to `/* DashboardKit v{N+1}.js */`.
-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.
+3. In [bitbucket-pipelines.yml](../bitbucket-pipelines.yml), add `v{N+1}.js`
+   to the `cp` line and stamp `__BUILD__` in it too, and add it to `files` in
+   [package.json](package.json) — **in addition to** every live major, never
+   instead of one. 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`.
@@ -117,12 +123,13 @@ URLs already pinned by live dashboards.
 
 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:
+`v4.css`, `v5.js`, `wrapper.js`, `wrapper.css` and `catalog.html` as they are
+in this directory, with the `__BUILD__` marker in each kit's JS 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
+  which load `https://dashboard-kit-2n2.pages.dev/v5.js` (older ones
+  `v4.js` and `v4.css`). 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

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "@datalabz_/dashboard-kit",
-  "version": "4.0.4",
+  "version": "5.0.1",
   "description": "DashboardKit runtime + styles, served from jsDelivr",
   "license": "UNLICENSED",
   "files": [
     "v4.js",
     "v4.css",
+    "v5.js",
     "wrapper.js",
     "wrapper.css"
   ],

package/v4.js

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