Add Resource Loader SPA and JS test harness

README.md

@@ -32,6 +32,7 @@ flowchart LR
 | `posts/` | Longer-lived posts; `posts/career/` has its own index | Source, except generated list pages |
 | `home/` | Utility and dashboard-style pages | Source, except `categories.org` |
 | `play/` | Interactive and experimental pages | Source |
+| `rl/` | Browser-local Resource Loader SPA | Source |
 | `lima/` | Org or Markdown pages with special attachment handling | Source, except `lima-list.org` |
 | `assets/` | Browser code, styles, fonts, images, and content manifests | Mostly source; some manifests/scripts are generated externally |
 | `lisp/` | Modular Emacs Lisp publishing system | Source |
@@ -279,6 +280,8 @@ These APIs are not implemented here. Production routing must serve `output/` and
 
 The hidden-details feature uses browser `localStorage`/`sessionStorage` for visit and discovery state and may call Open-Meteo after explicit geolocation interaction. Its friendly content source is `assets/content/hidden-details.json`; `assets/scripts/features/hidden-details.js` is generated by the external hidden-narrative authoring workflow. Treat both files as a pair and do not hand-edit only the generated JavaScript.
 
+The Resource Loader at `/rl/` is intentionally backend-free. It seeds Work and Personal Study vaults from `assets/content/resource-loader.json`, then stores library metadata and retained PDFs in IndexedDB under `zxh-resource-loader`. JSON exports contain metadata and reading sessions, not PDF binaries. Its page code lives in `assets/scripts/pages/resource-loader.js`; the separately testable schema/progress operations live in `resource-loader-model.js` and run with `make test-js`.
+
 ## Authoring service
 
 The browser authoring UI is a separate sibling repository at: