@proveanything/smartlinks 2.0.24 → 2.0.26

package/dist/docs/API_SUMMARY.md

@@ -1,6 +1,6 @@
 # Smartlinks API Summary
 
-Version: 2.0.24  |  Generated: 2026-09-27T07:52:03.418Z
+Version: 2.0.26  |  Generated: 2026-09-28T11:34:04.010Z
 
 This is a concise summary of all available API functions and types.
 
@@ -2293,11 +2293,9 @@ interface PublicViewParams {
 interface PublicView {
   id: string;
   title: string;
-  kind: PublicViewKind;
   route?: string;
   set?: Record<string, string>;
   params?: PublicViewParams;
-  default?: boolean;
 }
 ```
 
@@ -2373,8 +2371,6 @@ interface GetCollectionWidgetsOptions {
 
 **AppFunctionAuthority** = `'caller' | 'collection'`
 
-**PublicViewKind** = `'contextual' | 'standalone'`
-
 ### appObjects
 
 **PaginatedResponse<T>** (interface)

package/dist/docs/app-manifest.md

@@ -334,22 +334,23 @@ See the [Deep Link Discovery guide](deep-link-discovery.md) for the full dual-so
 
 #### `publicViews`
 
-Declares the app's **public views** — the soft-routed entries over your single public bundle
-(`index.html` → HashRouter): the contextual page, a display board, a kiosk/TV screen, etc. Without
-this, those routes/modes are invisible to the platform and the Dev Hub. Each view is a `route` + fixed
-`set` params + caller `params` + a `kind`; the `default` **contextual** view is the tag-tap target.
-It's delivery-agnostic — the same view renders as a **page** (standalone, self-CSS, hash-routed, embed
-in an iframe or open directly) or, for a contextual view, as a **component** (`PublicContainer`).
-Not a separate build. (Distinct from `linkable`, which is deep-link discovery.)
+Declares the app's **public views** — **standalone, external screens** served over your single public
+bundle (`index.html` → HashRouter): a display board, a kiosk/TV screen, a dashboard, a public share
+page. Without this, those routes/modes are invisible to the platform and the Dev Hub. Each view is a
+`route` + fixed `set` params + caller `params`.
+
+> **Public views are NOT portal.** They are completely external and independent. Their only input is
+> **URL parameters** (often a `collectionId`, as a plain param). They expect **no** portal wrapper, **no**
+> host-managed auth/session, and **no** physical-twin context (no QR/NFC/tag scan). They open at a URL
+> and stand alone. For the two **portal** surfaces — where the app renders *inside* portal, and the
+> entry points portal menus link to — see below.
 
 ```json
 "publicViews": [
-  { "id": "page",  "title": "Product page",  "kind": "contextual", "route": "/", "default": true,
-    "params": { "required": ["collectionId"], "optional": ["productId", "proofId"] } },
-  { "id": "board", "title": "Display board", "kind": "standalone", "route": "/preview",
-    "params": { "required": ["collectionId", "appId", "pageId"], "optional": ["orientation"] } },
-  { "id": "tv",    "title": "TV / big screen", "kind": "standalone", "route": "/",
-    "set": { "tvMode": "true" }, "params": { "required": ["collectionId", "voteId"] } }
+  { "id": "board", "title": "Display board", "route": "/display",
+    "params": { "required": ["collectionId"], "optional": ["orientation"] } },
+  { "id": "tv",    "title": "TV / big screen", "route": "/", "set": { "tvMode": "true" },
+    "params": { "required": ["collectionId", "voteId"] } }
 ]
 ```
 
@@ -357,14 +358,21 @@ Not a separate build. (Distinct from `linkable`, which is deep-link discovery.)
 |-------|------|----------|-------------|
 | `id` | string | ✅ | Stable id, unique within the app |
 | `title` | string | ✅ | Human label (Dev Hub dropdown, platform pickers) |
-| `kind` | `"contextual"` \| `"standalone"` | ✅ | Context-aware (tag-tap) vs full-screen, non-contextual |
 | `route` | string | ❌ | Hash route within the public bundle (defaults to `"/"`) |
 | `set` | object | ❌ | Query params this view PINS (e.g. `{ "tvMode": "true" }`), merged under caller params |
-| `params` | `{ required?: string[]; optional?: string[] }` | ❌ | The params the caller supplies |
-| `default` | boolean | ❌ | The default contextual view — the tag-tap target (at most one) |
+| `params` | `{ required?: string[]; optional?: string[] }` | ❌ | The params the caller supplies via the URL |
+
+Read the URL params with **`SL.readContext()`** (merges hash → search) instead of hand-rolling it.
+
+##### Public views vs the two portal surfaces
+
+An app can have any combination of three setup styles. Only public views are external:
 
-Read context the same way in every delivery with **`SL.readContext(props?)`** (merges props → hash →
-search), instead of hand-rolling the `containerProps || hash || search` chain.
+| Style | Declared by | Lives | Context |
+|-------|-------------|-------|---------|
+| **Portal components** — where the app renders inside portal (collection / product / batch / variant / proof) | module registry `components.*` (set at publish) | Inside portal | Physical twin (QR/NFC scan) |
+| **Portal deep links** — the entry points portal menus/tabs/side-menus link to (e.g. list view vs calendar view) | `linkable` / `DeepLinkEntry` | Inside portal | Portal (menu picks the entry) |
+| **Public views** — standalone external screens | `publicViews` (this block) | Outside portal | URL params only |
 
 #### `records`
 

package/dist/openapi.yaml

@@ -18480,8 +18480,6 @@ components:
           type: string
         title:
           type: string
-        kind:
-          $ref: "#/components/schemas/PublicViewKind"
         route:
           type: string
         set:
@@ -18490,12 +18488,9 @@ components:
             type: string
         params:
           $ref: "#/components/schemas/PublicViewParams"
-        default:
-          type: boolean
       required:
         - id
         - title
-        - kind
     AppManifest:
       type: object
       properties:
@@ -18635,11 +18630,6 @@ components:
       enum:
         - caller
         - collection
-    PublicViewKind:
-      type: string
-      enum:
-        - contextual
-        - standalone
     PaginatedResponse:
       type: object
       properties:

package/dist/types/appManifest.d.ts

@@ -485,40 +485,42 @@ export interface AppAdminConfig {
  * Setup, import, tunable, and metrics configuration lives in a separate
  * `app.admin.json` file. Use the `admin` field to locate and fetch it.
  */
-/** A public view's kind: context-aware (tag-tap) vs a full-screen, non-contextual screen. */
-export type PublicViewKind = 'contextual' | 'standalone';
 /** The caller-supplied params a public view expects. */
 export interface PublicViewParams {
     /** Params the view REQUIRES to render (e.g. `['collectionId','pageId']`). */
     required?: string[];
-    /** Params the view can use if present (e.g. `['productId','proofId','orientation']`). */
+    /** Params the view can use if present (e.g. `['orientation','theme']`). */
     optional?: string[];
 }
 /**
- * A declared PUBLIC VIEW of the app — one soft-routed entry over the single public bundle
- * (`index.html` → HashRouter), so the platform + Dev Hub can enumerate and target it instead of
- * guessing at undeclared hash routes. A view is `route` + fixed params (`set`) + caller `params` +
- * a `kind`. It is a DELIVERY-agnostic description: the same view renders as a `page` (standalone
- * HTML, hash-routed, its own CSS — embed in an iframe or open directly) or, for a `contextual` view,
- * as a `component` (PublicContainer, props context). NOT a separate build. See
- * docs/design/public-views.md. (Distinct from `linkable`/DeepLinkEntry, which is deep-link
- * discovery; publicViews is the top-level public-entry taxonomy used for preview + tag-tap routing.)
+ * A declared PUBLIC VIEW of the app — a STANDALONE, freeform screen served over the app's single
+ * public bundle (`index.html` → HashRouter), enumerable/targetable by the platform + Dev Hub instead
+ * of guessing at undeclared hash routes. A view is `route` + fixed params (`set`) + caller `params`.
+ *
+ * PUBLIC VIEWS ARE NOT PORTAL. They are completely external, independent pages — display boards,
+ * projector/kiosk screens, dashboards, public share pages. Their ONLY input is URL parameters (often a
+ * `collectionId`, as a plain param). They expect NO portal wrapper, NO host-managed auth/session, and
+ * NO physical-twin context (no QR/NFC/tag scan). They open at a URL and stand alone.
+ *
+ * This is distinct from the two PORTAL-side surfaces, which are declared elsewhere and are context-fed
+ * by the physical twin the portal resolves:
+ *  - WHERE the app renders inside portal (collection/product/batch/variant/proof) → the module
+ *    registry `components.*` (see prove docs/design/module-registry-fields.md).
+ *  - The different entry points portal MENUS/TABS/SIDE-MENUS link to (e.g. one app with a list view
+ *    and a calendar view) → `linkable`/DeepLinkEntry below.
+ * See docs/design/public-views.md.
  */
 export interface PublicView {
     /** Stable id, unique within the app. */
     id: string;
     /** Human label (Dev Hub dropdown, platform pickers). */
     title: string;
-    /** `contextual` (context-aware, tag-tap target) or `standalone` (full-screen display/kiosk). */
-    kind: PublicViewKind;
     /** Hash route within the public bundle. Defaults to `/`. */
     route?: string;
     /** Query params this view PINS (e.g. `{ tvMode: 'true' }`), merged under the caller's params. */
     set?: Record<string, string>;
-    /** The params the caller supplies. */
+    /** The params the caller supplies via the URL. */
     params?: PublicViewParams;
-    /** The default `contextual` view — the tag-tap target. At most one view sets this. */
-    default?: boolean;
 }
 export interface AppManifest {
     $schema?: string;
@@ -601,19 +603,22 @@ export interface AppManifest {
         components: AppContainerComponent[];
     };
     /**
-     * Static deep-linkable states built into this app.
-     * These are fixed routes that exist regardless of content — declared once at build time.
-     * Dynamic content entries (e.g. CMS pages) are stored separately in `appConfig.linkable`.
-     * Consumers should merge both sources to get the full set of navigable states.
+     * PORTAL deep-linkable states built into this app — the entry points the portal's menu system
+     * (bottom menu, side menus, tabs) can link to. Use these when one app has several ways to enter/load
+     * its portal component (e.g. a list view and a calendar view, or a viewer and an editor) that
+     * different parts of portal should link to independently. These live INSIDE portal.
+     * Fixed routes are declared here at build time; dynamic content entries (e.g. CMS pages) are stored
+     * separately in `appConfig.linkable` — merge both for the full navigable set.
      * @see DeepLinkEntry
      */
     linkable?: DeepLinkEntry[];
     /**
-     * The app's PUBLIC VIEWS — the soft-routed entries over the single public bundle
-     * (contextual page, display board, kiosk/TV, …), so the platform + Dev Hub can enumerate,
-     * preview, and target them. Declares `route` + fixed `set` params + caller `params` + `kind`
-     * per view; the `default` contextual view is the tag-tap target. See PublicView +
-     * docs/design/public-views.md.
+     * The app's PUBLIC VIEWS — STANDALONE, external screens (display boards, kiosks/TVs, dashboards,
+     * public pages) served over the single public bundle, so the platform + Dev Hub can enumerate,
+     * preview, and target them. Declares `route` + fixed `set` params + caller `params` per view.
+     * NOT portal: no portal wrapper, no host auth/session, no physical-twin context — URL params only.
+     * For portal surfaces use `components.*` (where it renders) and `linkable` (portal menu entries).
+     * See PublicView + docs/design/public-views.md.
      */
     publicViews?: PublicView[];
     /**

package/docs/API_SUMMARY.md

@@ -1,6 +1,6 @@
 # Smartlinks API Summary
 
-Version: 2.0.24  |  Generated: 2026-09-27T07:52:03.418Z
+Version: 2.0.26  |  Generated: 2026-09-28T11:34:04.010Z
 
 This is a concise summary of all available API functions and types.
 
@@ -2293,11 +2293,9 @@ interface PublicViewParams {
 interface PublicView {
   id: string;
   title: string;
-  kind: PublicViewKind;
   route?: string;
   set?: Record<string, string>;
   params?: PublicViewParams;
-  default?: boolean;
 }
 ```
 
@@ -2373,8 +2371,6 @@ interface GetCollectionWidgetsOptions {
 
 **AppFunctionAuthority** = `'caller' | 'collection'`
 
-**PublicViewKind** = `'contextual' | 'standalone'`
-
 ### appObjects
 
 **PaginatedResponse<T>** (interface)

package/docs/app-manifest.md

@@ -334,22 +334,23 @@ See the [Deep Link Discovery guide](deep-link-discovery.md) for the full dual-so
 
 #### `publicViews`
 
-Declares the app's **public views** — the soft-routed entries over your single public bundle
-(`index.html` → HashRouter): the contextual page, a display board, a kiosk/TV screen, etc. Without
-this, those routes/modes are invisible to the platform and the Dev Hub. Each view is a `route` + fixed
-`set` params + caller `params` + a `kind`; the `default` **contextual** view is the tag-tap target.
-It's delivery-agnostic — the same view renders as a **page** (standalone, self-CSS, hash-routed, embed
-in an iframe or open directly) or, for a contextual view, as a **component** (`PublicContainer`).
-Not a separate build. (Distinct from `linkable`, which is deep-link discovery.)
+Declares the app's **public views** — **standalone, external screens** served over your single public
+bundle (`index.html` → HashRouter): a display board, a kiosk/TV screen, a dashboard, a public share
+page. Without this, those routes/modes are invisible to the platform and the Dev Hub. Each view is a
+`route` + fixed `set` params + caller `params`.
+
+> **Public views are NOT portal.** They are completely external and independent. Their only input is
+> **URL parameters** (often a `collectionId`, as a plain param). They expect **no** portal wrapper, **no**
+> host-managed auth/session, and **no** physical-twin context (no QR/NFC/tag scan). They open at a URL
+> and stand alone. For the two **portal** surfaces — where the app renders *inside* portal, and the
+> entry points portal menus link to — see below.
 
 ```json
 "publicViews": [
-  { "id": "page",  "title": "Product page",  "kind": "contextual", "route": "/", "default": true,
-    "params": { "required": ["collectionId"], "optional": ["productId", "proofId"] } },
-  { "id": "board", "title": "Display board", "kind": "standalone", "route": "/preview",
-    "params": { "required": ["collectionId", "appId", "pageId"], "optional": ["orientation"] } },
-  { "id": "tv",    "title": "TV / big screen", "kind": "standalone", "route": "/",
-    "set": { "tvMode": "true" }, "params": { "required": ["collectionId", "voteId"] } }
+  { "id": "board", "title": "Display board", "route": "/display",
+    "params": { "required": ["collectionId"], "optional": ["orientation"] } },
+  { "id": "tv",    "title": "TV / big screen", "route": "/", "set": { "tvMode": "true" },
+    "params": { "required": ["collectionId", "voteId"] } }
 ]
 ```
 
@@ -357,14 +358,21 @@ Not a separate build. (Distinct from `linkable`, which is deep-link discovery.)
 |-------|------|----------|-------------|
 | `id` | string | ✅ | Stable id, unique within the app |
 | `title` | string | ✅ | Human label (Dev Hub dropdown, platform pickers) |
-| `kind` | `"contextual"` \| `"standalone"` | ✅ | Context-aware (tag-tap) vs full-screen, non-contextual |
 | `route` | string | ❌ | Hash route within the public bundle (defaults to `"/"`) |
 | `set` | object | ❌ | Query params this view PINS (e.g. `{ "tvMode": "true" }`), merged under caller params |
-| `params` | `{ required?: string[]; optional?: string[] }` | ❌ | The params the caller supplies |
-| `default` | boolean | ❌ | The default contextual view — the tag-tap target (at most one) |
+| `params` | `{ required?: string[]; optional?: string[] }` | ❌ | The params the caller supplies via the URL |
+
+Read the URL params with **`SL.readContext()`** (merges hash → search) instead of hand-rolling it.
+
+##### Public views vs the two portal surfaces
+
+An app can have any combination of three setup styles. Only public views are external:
 
-Read context the same way in every delivery with **`SL.readContext(props?)`** (merges props → hash →
-search), instead of hand-rolling the `containerProps || hash || search` chain.
+| Style | Declared by | Lives | Context |
+|-------|-------------|-------|---------|
+| **Portal components** — where the app renders inside portal (collection / product / batch / variant / proof) | module registry `components.*` (set at publish) | Inside portal | Physical twin (QR/NFC scan) |
+| **Portal deep links** — the entry points portal menus/tabs/side-menus link to (e.g. list view vs calendar view) | `linkable` / `DeepLinkEntry` | Inside portal | Portal (menu picks the entry) |
+| **Public views** — standalone external screens | `publicViews` (this block) | Outside portal | URL params only |
 
 #### `records`
 

package/openapi.yaml

@@ -18480,8 +18480,6 @@ components:
           type: string
         title:
           type: string
-        kind:
-          $ref: "#/components/schemas/PublicViewKind"
         route:
           type: string
         set:
@@ -18490,12 +18488,9 @@ components:
             type: string
         params:
           $ref: "#/components/schemas/PublicViewParams"
-        default:
-          type: boolean
       required:
         - id
         - title
-        - kind
     AppManifest:
       type: object
       properties:
@@ -18635,11 +18630,6 @@ components:
       enum:
         - caller
         - collection
-    PublicViewKind:
-      type: string
-      enum:
-        - contextual
-        - standalone
     PaginatedResponse:
       type: object
       properties:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@proveanything/smartlinks",
-  "version": "2.0.24",
+  "version": "2.0.26",
   "description": "Official JavaScript/TypeScript SDK for the Smartlinks API",
   "type": "module",
   "main": "dist/index.js",
@@ -65,8 +65,7 @@
   "author": "Glenn Shoosmith",
   "license": "MIT",
   "publishConfig": {
-    "access": "public",
-    "tag": "next"
+    "access": "public"
   },
   "dependencies": {
     "cross-fetch": "^3.1.5",