@betterportal/theme-bootstrap1 10.1.46 → 10.1.48

package/bp-resources/SKILL.md

@@ -8,7 +8,7 @@ description: Build BetterPortal service UI that fits the active Bootstrap1 shell
 1. Read the active app's `/llms-api.txt` and this theme's UI guide.
 2. Identify the service view, methods, schemas, required permissions and stable `viewId`.
 3. Render server-side JSX/HTMX for the `bootstrap1` theme. Return only service content, never the shell.
-4. Use `ctx.routeUrl()` for service requests and `ctx.uiRouteUrl()` only for GET page navigation.
+4. In renderers, use `ctx.url.route()` for service requests and `ctx.url.uiRoute()` only for GET page navigation. Pass a declared dependency alias as `serviceId` for another service.
 5. Use the framework `BPElement` JSX helper with `ctx` for cross-service or active-shell fragments. Reference the dependency alias/key declared in `betterportal.json`, never a title, service UUID, hostname, or absolute URL. Omit `bp-ok` for direct success insertion; an explicit wrapping `bp-ok` must have exactly one `<template />`.
 6. Prefer Bootstrap components and native HTML controls. Add custom CSS or JavaScript only when the theme and platform primitives cannot express the behavior.
 7. Include loading, empty, validation, forbidden and service-unavailable states.

package/bp-resources/page-template.tsx

@@ -1,14 +1,14 @@
 /** @jsxImportSource jsx-htmx */
-import type { PageRenderer } from "@betterportal/framework";
+import type { RegisteredViewRenderer } from "@betterportal/framework";
 
-export const render: PageRenderer = (data, ctx) => (
+export const render: RegisteredViewRenderer["render"] = (data, ctx) => (
   <section class="container-fluid py-3">
     <div class="d-flex flex-wrap justify-content-between align-items-center gap-2 mb-3">
       <div>
         <h1 class="h3 mb-1">Page title</h1>
         <p class="text-body-secondary mb-0">Explain the task in one sentence.</p>
       </div>
-      <a class="btn btn-primary" href={ctx.uiRouteUrl("example.create") ?? "#"}>Create</a>
+      <a class="btn btn-primary" href={ctx.url.uiRoute("example.create") ?? "#"}>Create</a>
     </div>
     <div class="card shadow-sm">
       <div class="card-body">{JSON.stringify(data)}</div>

package/bp-resources/ui-guide.md

@@ -13,7 +13,7 @@ Use Bootstrap 5 classes and server-rendered JSX/HTMX. BetterPortal service rende
 ## Forms and mutations
 
 - Use real `<form>` elements and labelled controls. Validation text uses `.invalid-feedback` or `.form-text`.
-- Use `ctx.routeUrl()` for form actions, HTMX calls, downloads and SSE. `ctx.uiRouteUrl()` is only for GET navigation through a mounted page route.
+- In renderers, use `ctx.url.route()` for form actions, HTMX calls, downloads and SSE. `ctx.url.uiRoute()` is only for GET navigation through a mounted page route. For another service, pass its declared dependency alias as `serviceId`; both helpers resolve the active app-mounted provider. Handler equivalents are `ctx.routeUrl()` and `ctx.uiRouteUrl()`.
 - Use `<BPElement ctx={ctx} service="dependency-alias" path="/contract/path" fragment="location.id">` for cross-service UI fragments. `service` is the dependency alias/key declared in `betterportal.json`; never put service titles, UUIDs, hostnames, or absolute URLs in renderer code. The server consumes `ctx` and resolves the active app-mounted provider.
 - Use `service="shell"` and a singular shell fragment id to reuse active-shell UI such as `theme-selector`. Add `bp-loading`, status-specific `bp-status`, and `bp-nok` states as needed. Omit `bp-ok` to insert successful content directly; add it only to wrap success content, with exactly one `<template />`.
 - The renderer's second argument is `ViewRenderContext`. Use its limited `tenant`/`app` presentation projections and `ctx.url` helpers; keep authorization and business data in the handler. Auth navigation fields are view IDs and must be resolved with `ctx.url.uiRoute()`.

package/lib/bp-contracts/org.betterportal.theme.bootstrap1.json

@@ -4,7 +4,7 @@
     "pluginId": "org.betterportal.theme.bootstrap1",
     "title": "Bootstrap1 Theme",
     "description": "Bootstrap 5 + htmx theme that renders BetterPortal app shells.",
-    "version": "10.1.46",
+    "version": "10.1.48",
     "category": "theme",
     "deploymentModes": [
       "self-hosted"
@@ -249,7 +249,7 @@
         "title": "Bootstrap1 UI guide",
         "description": "Layout, component, HTMX, responsive and accessibility rules.",
         "mediaType": "text/markdown; charset=utf-8",
-        "content": "# Bootstrap1 UI guide\n\nUse Bootstrap 5 classes and server-rendered JSX/HTMX. BetterPortal service renderers return fragments; the theme owns the shell, navigation, visible URL and global assets.\n\n## Layout\n\n- Render primary content for the `main` slot. Never emit another page shell, `<html>`, `<head>`, sidebar navigation or top bar.\n- Start pages with a semantic heading and a short action row when actions exist.\n- Use `.container-fluid`, Bootstrap grid classes and responsive gaps. Avoid fixed widths except a declared `data-bp-sidebar-width`.\n- Use cards for grouped settings, tables for comparable records and list groups for short navigation or status collections.\n- Keep primary actions on the right of desktop action rows and allow them to wrap on small screens.\n\n## Forms and mutations\n\n- Use real `<form>` elements and labelled controls. Validation text uses `.invalid-feedback` or `.form-text`.\n- Use `ctx.routeUrl()` for form actions, HTMX calls, downloads and SSE. `ctx.uiRouteUrl()` is only for GET navigation through a mounted page route.\n- Use `<BPElement ctx={ctx} service=\"dependency-alias\" path=\"/contract/path\" fragment=\"location.id\">` for cross-service UI fragments. `service` is the dependency alias/key declared in `betterportal.json`; never put service titles, UUIDs, hostnames, or absolute URLs in renderer code. The server consumes `ctx` and resolves the active app-mounted provider.\n- Use `service=\"shell\"` and a singular shell fragment id to reuse active-shell UI such as `theme-selector`. Add `bp-loading`, status-specific `bp-status`, and `bp-nok` states as needed. Omit `bp-ok` to insert successful content directly; add it only to wrap success content, with exactly one `<template />`.\n- The renderer's second argument is `ViewRenderContext`. Use its limited `tenant`/`app` presentation projections and `ctx.url` helpers; keep authorization and business data in the handler. Auth navigation fields are view IDs and must be resolved with `ctx.url.uiRoute()`.\n- Mutations should return a useful fragment and emit an `HX-Trigger` event for passive regions that need to reload.\n- Disable buttons only while their own request is active. Keep a visible loading indicator and an error fragment.\n\n## Components\n\n- Buttons: `.btn`, with one obvious `.btn-primary` action per group.\n- Status: Bootstrap badges with text; never communicate state by colour alone.\n- Destructive actions: `.btn-outline-danger` or `.btn-danger`, with confirmation proportional to impact.\n- Side panels: wrap content in `data-bp-sidebar`, add `data-bp-sidebar-title`, and open it with `data-bp-sidebar-open`. The theme converts it to an offcanvas.\n- Modals and offcanvas content may be teleported by the shell. Do not depend on a specific DOM parent after activation.\n\n## Accessibility\n\n- Preserve heading order, visible labels, keyboard focus and native controls.\n- Every icon-only action needs an accessible name.\n- Tables need headers; use a responsive wrapper instead of shrinking text.\n- Focus the first meaningful control when opening a task panel and return focus to its trigger when it closes.\n\n## Avoid\n\n- No SPA framework, client router, iframe, client state store or hardcoded service hostname.\n- No inline copy of Bootstrap or shell JavaScript.\n- No theme-origin mutation URL. Service requests go to service URLs.\n- No custom colour that bypasses the app palette when a Bootstrap semantic token exists.\n"
+        "content": "# Bootstrap1 UI guide\n\nUse Bootstrap 5 classes and server-rendered JSX/HTMX. BetterPortal service renderers return fragments; the theme owns the shell, navigation, visible URL and global assets.\n\n## Layout\n\n- Render primary content for the `main` slot. Never emit another page shell, `<html>`, `<head>`, sidebar navigation or top bar.\n- Start pages with a semantic heading and a short action row when actions exist.\n- Use `.container-fluid`, Bootstrap grid classes and responsive gaps. Avoid fixed widths except a declared `data-bp-sidebar-width`.\n- Use cards for grouped settings, tables for comparable records and list groups for short navigation or status collections.\n- Keep primary actions on the right of desktop action rows and allow them to wrap on small screens.\n\n## Forms and mutations\n\n- Use real `<form>` elements and labelled controls. Validation text uses `.invalid-feedback` or `.form-text`.\n- In renderers, use `ctx.url.route()` for form actions, HTMX calls, downloads and SSE. `ctx.url.uiRoute()` is only for GET navigation through a mounted page route. For another service, pass its declared dependency alias as `serviceId`; both helpers resolve the active app-mounted provider. Handler equivalents are `ctx.routeUrl()` and `ctx.uiRouteUrl()`.\n- Use `<BPElement ctx={ctx} service=\"dependency-alias\" path=\"/contract/path\" fragment=\"location.id\">` for cross-service UI fragments. `service` is the dependency alias/key declared in `betterportal.json`; never put service titles, UUIDs, hostnames, or absolute URLs in renderer code. The server consumes `ctx` and resolves the active app-mounted provider.\n- Use `service=\"shell\"` and a singular shell fragment id to reuse active-shell UI such as `theme-selector`. Add `bp-loading`, status-specific `bp-status`, and `bp-nok` states as needed. Omit `bp-ok` to insert successful content directly; add it only to wrap success content, with exactly one `<template />`.\n- The renderer's second argument is `ViewRenderContext`. Use its limited `tenant`/`app` presentation projections and `ctx.url` helpers; keep authorization and business data in the handler. Auth navigation fields are view IDs and must be resolved with `ctx.url.uiRoute()`.\n- Mutations should return a useful fragment and emit an `HX-Trigger` event for passive regions that need to reload.\n- Disable buttons only while their own request is active. Keep a visible loading indicator and an error fragment.\n\n## Components\n\n- Buttons: `.btn`, with one obvious `.btn-primary` action per group.\n- Status: Bootstrap badges with text; never communicate state by colour alone.\n- Destructive actions: `.btn-outline-danger` or `.btn-danger`, with confirmation proportional to impact.\n- Side panels: wrap content in `data-bp-sidebar`, add `data-bp-sidebar-title`, and open it with `data-bp-sidebar-open`. The theme converts it to an offcanvas.\n- Modals and offcanvas content may be teleported by the shell. Do not depend on a specific DOM parent after activation.\n\n## Accessibility\n\n- Preserve heading order, visible labels, keyboard focus and native controls.\n- Every icon-only action needs an accessible name.\n- Tables need headers; use a responsive wrapper instead of shrinking text.\n- Focus the first meaningful control when opening a task panel and return focus to its trigger when it closes.\n\n## Avoid\n\n- No SPA framework, client router, iframe, client state store or hardcoded service hostname.\n- No inline copy of Bootstrap or shell JavaScript.\n- No theme-origin mutation URL. Service requests go to service URLs.\n- No custom colour that bypasses the app palette when a Bootstrap semantic token exists.\n"
       },
       {
         "id": "bootstrap1.skill",
@@ -257,7 +257,7 @@
         "title": "Bootstrap1 UI skill",
         "description": "Agent workflow for producing theme-compatible service UI.",
         "mediaType": "text/markdown; charset=utf-8",
-        "content": "---\nname: betterportal-bootstrap1-ui\ndescription: Build BetterPortal service UI that fits the active Bootstrap1 shell.\n---\n\n# BetterPortal Bootstrap1 UI\n\n1. Read the active app's `/llms-api.txt` and this theme's UI guide.\n2. Identify the service view, methods, schemas, required permissions and stable `viewId`.\n3. Render server-side JSX/HTMX for the `bootstrap1` theme. Return only service content, never the shell.\n4. Use `ctx.routeUrl()` for service requests and `ctx.uiRouteUrl()` only for GET page navigation.\n5. Use the framework `BPElement` JSX helper with `ctx` for cross-service or active-shell fragments. Reference the dependency alias/key declared in `betterportal.json`, never a title, service UUID, hostname, or absolute URL. Omit `bp-ok` for direct success insertion; an explicit wrapping `bp-ok` must have exactly one `<template />`.\n6. Prefer Bootstrap components and native HTML controls. Add custom CSS or JavaScript only when the theme and platform primitives cannot express the behavior.\n7. Include loading, empty, validation, forbidden and service-unavailable states.\n8. Check keyboard operation, visible labels, heading order and responsive wrapping.\n9. Verify JSON and HTML representations against the published schemas.\n\nFor side tasks, use `data-bp-sidebar` and `data-bp-sidebar-open`. For authenticated downloads, use `hx-download`. For live refresh, emit an `HX-Trigger` event and subscribe with `hx-trigger=\"event from:body\"`.\n"
+        "content": "---\nname: betterportal-bootstrap1-ui\ndescription: Build BetterPortal service UI that fits the active Bootstrap1 shell.\n---\n\n# BetterPortal Bootstrap1 UI\n\n1. Read the active app's `/llms-api.txt` and this theme's UI guide.\n2. Identify the service view, methods, schemas, required permissions and stable `viewId`.\n3. Render server-side JSX/HTMX for the `bootstrap1` theme. Return only service content, never the shell.\n4. In renderers, use `ctx.url.route()` for service requests and `ctx.url.uiRoute()` only for GET page navigation. Pass a declared dependency alias as `serviceId` for another service.\n5. Use the framework `BPElement` JSX helper with `ctx` for cross-service or active-shell fragments. Reference the dependency alias/key declared in `betterportal.json`, never a title, service UUID, hostname, or absolute URL. Omit `bp-ok` for direct success insertion; an explicit wrapping `bp-ok` must have exactly one `<template />`.\n6. Prefer Bootstrap components and native HTML controls. Add custom CSS or JavaScript only when the theme and platform primitives cannot express the behavior.\n7. Include loading, empty, validation, forbidden and service-unavailable states.\n8. Check keyboard operation, visible labels, heading order and responsive wrapping.\n9. Verify JSON and HTML representations against the published schemas.\n\nFor side tasks, use `data-bp-sidebar` and `data-bp-sidebar-open`. For authenticated downloads, use `hx-download`. For live refresh, emit an `HX-Trigger` event and subscribe with `hx-trigger=\"event from:body\"`.\n"
       },
       {
         "id": "bootstrap1.page-template",
@@ -266,7 +266,7 @@
         "description": "Minimal server-rendered JSX page structure.",
         "mediaType": "text/plain; charset=utf-8",
         "language": "typescript",
-        "content": "/** @jsxImportSource jsx-htmx */\nimport type { PageRenderer } from \"@betterportal/framework\";\n\nexport const render: PageRenderer = (data, ctx) => (\n  <section class=\"container-fluid py-3\">\n    <div class=\"d-flex flex-wrap justify-content-between align-items-center gap-2 mb-3\">\n      <div>\n        <h1 class=\"h3 mb-1\">Page title</h1>\n        <p class=\"text-body-secondary mb-0\">Explain the task in one sentence.</p>\n      </div>\n      <a class=\"btn btn-primary\" href={ctx.uiRouteUrl(\"example.create\") ?? \"#\"}>Create</a>\n    </div>\n    <div class=\"card shadow-sm\">\n      <div class=\"card-body\">{JSON.stringify(data)}</div>\n    </div>\n  </section>\n);\n"
+        "content": "/** @jsxImportSource jsx-htmx */\nimport type { RegisteredViewRenderer } from \"@betterportal/framework\";\n\nexport const render: RegisteredViewRenderer[\"render\"] = (data, ctx) => (\n  <section class=\"container-fluid py-3\">\n    <div class=\"d-flex flex-wrap justify-content-between align-items-center gap-2 mb-3\">\n      <div>\n        <h1 class=\"h3 mb-1\">Page title</h1>\n        <p class=\"text-body-secondary mb-0\">Explain the task in one sentence.</p>\n      </div>\n      <a class=\"btn btn-primary\" href={ctx.url.uiRoute(\"example.create\") ?? \"#\"}>Create</a>\n    </div>\n    <div class=\"card shadow-sm\">\n      <div class=\"card-body\">{JSON.stringify(data)}</div>\n    </div>\n  </section>\n);\n"
       }
     ],
     "shell": {

package/lib/schemas/service-betterportal-theme-bootstrap1.json

@@ -1,7 +1,7 @@
 {
   "pluginName": "service-betterportal-theme-bootstrap1",
   "events": {},
-  "version": "10.1.46",
+  "version": "10.1.48",
   "configSchema": {
     "anyvaliVersion": "1.0",
     "schemaVersion": "1.1",

package/lib/schemas/service-betterportal-theme-bootstrap1.plugin.json

@@ -1,7 +1,7 @@
 {
   "id": "service-betterportal-theme-bootstrap1",
   "name": "service-betterportal-theme-bootstrap1",
-  "version": "10.1.46",
+  "version": "10.1.48",
   "description": "Bootstrap 5 and HTMX based BetterPortal theme",
   "category": "service",
   "tags": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@betterportal/theme-bootstrap1",
-  "version": "10.1.46",
+  "version": "10.1.48",
   "description": "BetterPortal v10 Bootstrap1 theme plugin for Node.js",
   "main": "lib/index.js",
   "types": "src/index.ts",
@@ -33,9 +33,9 @@
     "typescript": "^6.0.3"
   },
   "dependencies": {
-    "@betterportal/framework": "10.1.46",
-    "@betterportal/plugin-bsb": "10.1.46",
-    "@betterportal/theme-runtime": "10.1.46",
+    "@betterportal/framework": "10.1.48",
+    "@betterportal/plugin-bsb": "10.1.48",
+    "@betterportal/theme-runtime": "10.1.48",
     "@bsb/base": "^9.6.60",
     "anyvali": "^1.0.6",
     "bootstrap": "^5.3.8",

package/lib/plugins/service-betterportal-theme-bootstrap1/assets.cleanup.md

@@ -1,9 +0,0 @@
-# Bootstrap1 Asset Ownership
-
-The browser-runtime migration is complete.
-
-- `@betterportal/theme-runtime` owns HTMX, service URL rewriting, BP headers, preload, request lifecycle, route chrome state, history, SSE, downloads, auth failures, and background fragments.
-- `Bootstrap1AdapterSource` is typed TSX produced by `js()` and contains presentation hooks only.
-- Bootstrap1 owns Bootstrap assets, modal/offcanvas lifecycle, component initialization, error/loading presentation, and CSS for `data-bp-chrome-*`.
-- Route chrome is generic presentation state. It never implies authentication.
-- Theme adapters must not register duplicate HTMX lifecycle listeners.