pgkiln 0.69.0 → 0.71.0

package/docs/guide/04-pages-and-regions.md

@@ -1160,7 +1160,8 @@ select empno as id, mgr as parent_id, initcap(ename) || ' · ' || initcap(job) a
 ```
 
 Attributes: `expanded` (levels open at first, default 1), `link` (as for maps; `#id#` and any other
-column), `empty`. The tree is drawn on the server with `<details>`: it works without JavaScript,
+column), `empty`. (137) **Create page → Tree** makes one from a table: the key as the id, a foreign key to the
+table itself (`mgr` → `empno`) as the parent and the name column as the label. The tree is drawn on the server with `<details>`: it works without JavaScript,
 and the browser's find-in-page opens closed branches. Clicking a label follows the link; the rest
 of the row opens and closes the branch. Up to 5000 nodes.
 
@@ -1460,6 +1461,7 @@ with 26.1's *Metric Card* and group support). Show a region as `multiple` to get
 | `ut_avatar` | Avatar: a picture or initials | `NAME`, `INITIALS`, `IMAGE` (a relative or https URL), `SIZE` (small, medium, large), `SHAPE` (circle, square) | An avatar group (overlapping) |
 | `ut_badge` | Badge coloured by a state | `LABEL`, `STATE` (success, warning, danger, info, neutral; approved, pending, … are understood) | A row of badges |
 | `ut_comments` | Comments | `USER`, `INITIALS`, `DATE`, `COMMENT`, `ACTIONS` (extra text) | One conversation |
+| `ut_content_row` | (137) Content row: initials or a picture, title (linked when the region has a link) and description, a secondary text and a badge on the right | `TITLE`, `DESCRIPTION`, `MISC`, `INITIALS`, `IMAGE`, `BADGE`, `STATE` | One list |
 | `ut_media_list` | Media list: picture or initials, title (linked when the region has a link), description, badge | `TITLE`, `DESCRIPTION`, `INITIALS`, `IMAGE`, `BADGE`, `STATE` | One list |
 | `ut_metric_card` | Metric card: a key figure with its unit, change and trend | `LABEL`, `VALUE`, `UNIT`, `CHANGE`, `TREND` (up, down, flat), `GOOD` (up or down: which direction shows green), `DESCRIPTION` | A row of cards |
 | `ut_timeline` | Timeline: when, who, title, text, a coloured marker | `TITLE`, `WHEN`, `WHO`, `BODY`, `STATE` | One timeline |
@@ -1641,10 +1643,15 @@ Search configurations):
 | Icon | An [icon name](09-reference.md#icons), or `#COLUMN#` for a column that holds icon names |
 | Link | Where a result goes: `{"page": 3, "items": {"P3_ID": "#ID#"}}` (`#COLUMN#` is the row's value; the link gets a checksum, a modal page opens as a dialog) |
 | Maximum results | Per configuration, 1–100 (default 10); "Showing the first *n* rows." when there are more |
-| Search type | (sprint 135) `standard`: the words as below · `fulltext`: PostgreSQL full-text search (table and sql sources; see [full-text search](#full-text-search)). The type is the place where later types (vector search, and a hybrid of both) will go |
+| Search type | (sprint 135) `standard`: the words as below · `fulltext`: PostgreSQL full-text search (table and sql sources; see [full-text search](#full-text-search)) · (sprint 136) `vector`: by meaning, the rows whose embedding is nearest to the search text's · `hybrid`: full-text and vector together (see [vector search](#vector-search)) |
 | tsvector column or expression | `fulltext`: a `tsvector` column of the source (best: with a GIN index), or an expression such as `to_tsvector('english', title \|\| ' ' \|\| body)`. Empty: `to_tsvector` over the searchable columns on every search |
 | Text search configuration | `fulltext`: `english`, `dutch`, `german`, `simple`… (`pg_ts_config`): the one the tsvector was made with. Empty: the application's primary language's, else `simple` |
 | Did you mean | With the `pg_trgm` extension installed: when nothing is found, a link that searches for the closest words of the searched columns (any search type; reads up to 10,000 rows). Without `pg_trgm` nothing is suggested |
+| Vector provider | `vector`, `hybrid`: the [vector provider](03-builder.md#vector-providers) (static ID) that embeds the search text: the same one that embedded the rows |
+| Vector column | `vector`, `hybrid`: the source's `vector(n)` column, *n* the provider's dimensions |
+| Key column | `hybrid`: the key (e.g. `id`) that matches the full-text and the vector results |
+| Distance | `cosine` (default; most embedding models), `l2` or `inner_product`; an HNSW index helps only when it is built for the same one |
+| Minimum similarity | `vector`, `hybrid`: rows less similar than this are left out (cosine: 1 − distance; inner product: the product; l2: 1 / (1 + distance)). Empty: the nearest rows, however far |
 
 **How it searches.** Each word of the search text must be found (case-insensitively, anywhere in
 the value) in one of the searchable columns, so `clerk mil` finds MILLER the clerk. `%` and `_` are
@@ -1700,6 +1707,41 @@ with search type `fulltext`, tsvector `search_vector`, configuration `english`,
 every search), reports a configuration name that doesn't exist, and a column that isn't a tsvector. A report's
 search box can use the same engine: see its `fulltext` attribute.
 
+#### Vector search
+
+A configuration of search type **vector** (APEX: the search type *Oracle Vector Search*) finds rows by meaning:
+*time off for a family move* finds the policy *Relocation leave … relocate to another city … the new house*,
+though they share no word. It needs the [pgvector](https://github.com/pgvector/pgvector) extension (see
+[chapter 3](03-builder.md#vector-providers) for installing it), a vector provider and a vector column:
+
+1. **A vector provider** (Shared Components → Vector providers, [chapter 3](03-builder.md#vector-providers)): an
+   AI service with an embedding model (OpenAI `text-embedding-3-small`, Gemini, Ollama's `nomic-embed-text` …)
+   or a SQL function returning `vector`.
+2. **A vector column** on the table, kept current: SQL Workshop › Table Properties › **Add vector column**
+   ([chapter 3](03-builder.md)) adds `embedding vector(n)`, an HNSW index and a trigger, and queues the rows for
+   their embeddings.
+3. **The configuration**: search type `vector`, the provider, the vector column, title and description columns,
+   icon and link as for any configuration.
+
+When a user searches, pgkiln embeds the search text with the provider (an AI service: one request, remembered a
+few minutes for search-as-you-type, logged under AI usage; the text goes to that provider), then asks the
+database for the nearest rows (`order by embedding <=> $1 limit n`, which the HNSW index serves) as the
+application's role, so **row level security decides what is found**. The vector is a query parameter; pgvector's
+operators are called schema-qualified. Results are not marked word by word: they need not contain the words.
+
+**Hybrid** (`hybrid`) runs the full-text search (the tsvector and text search configuration above) and the vector
+search, takes the best 50 rows of each, and ranks them together by **reciprocal rank fusion**: each row scores
+1 / (60 + its rank) in each list it is in, summed, best first. Rows found by both rise to the top; a row that only
+one of them finds still shows. Hybrid needs the key column that tells which rows are the same.
+
+Without pgvector a vector or hybrid configuration shows that the extension is missing (and the Advisor reports
+it); the other configurations answer as before. The Advisor also checks that the provider exists, that the
+column is `vector(n)` with the provider's *n*, and warns when it has no HNSW index or one for another distance.
+The HR example (part 72) adds `POLICIES_MEANING` (hybrid, with a stand-in function provider) to page 42.
+
+An AI agent can use any table or SQL configuration as a **Retrieve** tool: the model gives a text, the agent gets
+the best rows ([AI agents](03-builder.md#ai-agents)).
+
 **The region**: attributes
 
 | Key | Meaning |
@@ -1714,7 +1756,7 @@ The region's own field is a GET form (`?s<region id>=text`, so a search can be b
 without JavaScript; with JavaScript it searches while the user types and replaces only the results.
 The Advisor plans every configuration with the columns it names and reports names a region uses
 that don't exist. Search configurations are exported with the application. The HR example's page 42
-searches employees, departments, the HR policies (full-text, part 71) and the shortcuts list.
+searches employees, departments, the HR policies (full-text, part 71; by meaning, part 72) and the shortcuts list.
 
 ### `url` (URL region)
 

package/docs/guide/05-items.md

@@ -21,7 +21,7 @@ page, optionally inside a region. Name them `P<page>_<NAME>` (uppercase letters,
 | `radio` | radio group | the chosen return value |
 | `checkbox` | a single checkbox | `true` / `false` |
 | `switch` | on/off switch | `true` / `false` |
-| `checkbox_group` | several checkboxes | **colon-separated** return values, e.g. `10:30` |
+| `checkbox_group` | several checkboxes | **colon-separated** return values, e.g. `10:30`; (137) `{"switches": true}` shows each as a switch, one per line |
 | `multiselect` | multi-select list | **colon-separated** return values |
 | `display` | read-only text (shows the display value for list items) | whatever was set |
 | `hidden` | not rendered | set by URL (with checksum), fetch or processes |

package/docs/guide/06-processing.md

@@ -598,6 +598,15 @@ the component out (fail closed); the Advisor reports it. Build options are part
 export. On HR page 22, the *Forecast* region needs `LEAVE_FORECAST` (excluded), and *Planner tips*
 (`!LEAVE_FORECAST`) takes its place until it is included.
 
+**Configurable build options** (sprint 137; APEX: the Configuration Options feature): tick *Configurable* on a
+build option, and **Create page → Feature → Configuration options** adds page 9020 *Configuration* where the
+application's administrators switch those options on and off while it runs (a checkbox group shown as switches,
+`{"switches": true}`). From SQL, as the application's own role and for a user with the `admin` role only:
+`meta.configurable_options()` (name, description, enabled) and `meta.set_configurable_options('EXPORT:BETA')`
+(the named ones included, the other configurable ones excluded; an option that is not configurable is refused).
+The change applies to every user at once, like a change in the builder. An import of a newer version of the
+application sets the options as the export has them.
+
 ## Application processes
 
 **Shared Components → Application processes** run for the whole application:
@@ -819,6 +828,15 @@ work for the **current application** only when the caller runs as that applicati
 (pages, processes, automations, workflows and background chains do); the SQL Workshop is not an
 application.
 
+### The activity report by mail
+
+`meta.send_activity_report(to, days default 7)` (sprint 137; APEX: the Email Reporting feature) queues a mail with
+the current application's activity of the last days (page views, users, sign-ins, failed sign-ins, errors and the
+most viewed pages) and the rows as `activity.csv`. It is for the application's automations and its signed-in
+administrators; others get an error. **Create page → Feature → E-mail reporting** adds the application setting
+`EMAIL_REPORT_TO` and an automation `EMAIL_REPORTING` that sends it every Monday at 07:00 UTC; without addresses
+nothing is sent.
+
 ### E-mail templates
 
 Shared Components → **E-mail templates** (APEX: Email Templates): a name, a subject, an HTML body

package/docs/guide/09-reference.md

@@ -167,6 +167,24 @@ select meta.ai_generate('CLAUDE', 'Classify: ' || :P5_TEXT, null,
   enabled and the application is allowed); whether the provider accepts the key shows only when a
   request is made.
 
+### Embeddings in SQL
+
+(sprint 136) `meta.embed(text, provider [, app_id])` returns the embedding of a text by a
+[vector provider](03-builder.md#vector-providers) of the current application (or of `app_id`, one the
+login may see) as `real[]`; cast it for pgvector: `meta.embed(:P1_Q, 'DOC_EMBEDDINGS')::vector`. It
+works for **function providers** and calls the function as the role of the query (security invoker:
+its grants apply), checking the dimensions. A provider that uses an AI service is called by the
+pgkiln server, never from SQL: `meta.embed` raises an error that says so (use a vector search
+configuration, a Retrieve tool or a vector column's queue). `meta.vector_provider(name [, app_id])`
+returns a provider's definition (they hold no secrets).
+
+```sql
+-- the nearest documents to a text, as the application's role (row level security applies)
+select title from sales.doc
+ order by embedding <=> meta.embed('how do I return an order?', 'DOC_EMBEDDINGS')::vector
+ limit 5;
+```
+
 ### Parsing files in SQL
 
 `meta.parse_data()` reads CSV/TSV and JSON in a `bytea` (an uploaded file in `meta.temp_files`, a
@@ -278,13 +296,16 @@ Run these as the owner (in the SQL Workshop, `psql` or migrations):
 |---|---|
 | `meta.generate_crud(app, table, report_page, form_page, label default null, icon default 'table')` | Report page + modal form page + menu entry for a table, with the column names as labels (kept as it was for existing scripts; `meta.generate_page` *report_form* makes the labelled pages of the wizards) |
 | `meta.generate_grid(app, table, page, label default null, icon default 'grid')` | Interactive grid page + menu entry |
-| `meta.generate_page(app, kind, table, page, options default '{}')` | The create page wizards: `kind` is `form`, `cards`, `calendar`, `chart`, `map`, `facets`, `master_detail` (or `report_form`, `grid`). Options left out take the defaults of `meta.wizard_defaults`; JSON `null` means none. Returns the new page's id (below) |
+| `meta.generate_page(app, kind, table, page, options default '{}')` | The create page wizards: `kind` is `form`, `cards`, `calendar`, `chart`, `map`, `facets`, `master_detail` (or `report_form`, `grid`); (137) also `report`, `smart_filters`, `tree`, `timeline`, `media_list`, `content_row`, `comments`, `data_load`, `wizard`, and without a table (`null`) `search`, `tasks`, `workflows`. Options left out take the defaults of `meta.wizard_defaults`; JSON `null` means none. Returns the new page's id (below; a wizard: its first page's) |
 | `meta.wizard_defaults(kind, table)` | The options a wizard proposes for a table, from the catalog |
 | `meta.wizard_catalog(table)` | The columns as the wizards see them: kind (`text`, `number`, `date`, `timestamp`, `boolean`, `point`, `geometry`, `binary`, `other`), key, unique, foreign key and the parent's display column |
 | `meta.wizard_label(name)`, `meta.wizard_table_label(table, plural default true)`, `meta.wizard_column_label(table, column)` | (097) The labels of the wizards: `hiredate` → *Hire Date*, `hr.emp` → *Employees* / *Employee*, `deptno` → *Department*; short comments win ([what the generated pages look like](03-builder.md#what-the-generated-pages-look-like)) |
 | `meta.wizard_report(table, columns default null)` | (097) A report on a table as the wizards make it: `{"source", "hidden", "headings", "formats"}` (foreign keys joined to their parent's display column) |
 | `meta.wizard_grid_labels(table)` | (100) An interactive grid's `{"headings", "formats"}` as the wizards make them: the labels of `meta.wizard_column_label` and the number format masks (keys get none) |
 | `meta.app_activity(days default 30)` | (098) The current application's page views, sign-ins and errors of the last days (1 to 366, at most 10,000 rows, no IP addresses), for a signed-in user with the `admin` role of that application; others get an error. The Activity page of the Create Application wizard reads it |
+| `meta.configurable_options()`, `meta.set_configurable_options(names)` | (137) The current application's [configurable build options](06-processing.md#build-options) (name, description, enabled), and switching them (`names` colon-separated: those are included, the other configurable ones excluded). Only as the application's own role, for a user with the `admin` role; other options are refused |
+| `meta.send_activity_report(to, days default 7)` | (137) Queue a mail with a summary of the current application's activity of the last days and the rows as `activity.csv`. For the application's automations and its signed-in administrators; empty `to`: nothing is sent. The *E-mail reporting* feature's automation calls it |
+| `meta.copy_page(from_app, page, to_app, new_page, name default null, map default '{}')` | (137) [Create page as copy](03-builder.md#create-page-as-copy) (owner only); `map` is `{"lov:JOBS": "JOB_TITLES"}`: a shared component to use instead of copying it. `meta.page_shared_refs(page_id, target_app)` lists what a page refers to by name |
 | `meta.wizard_files(table)` | (097) The `bytea` columns and the columns holding their file name, mime type, size and change time |
 | `meta.export_app(alias)` | The application as JSON (`pgkiln/2` format) |
 | `meta.import_app(json, alias default null)` | Import an export, optionally under a new alias; returns the new app id |
@@ -309,6 +330,17 @@ Options of `meta.generate_page` (all optional; column names must be columns of t
 | `facets` | `columns` (report columns, array), `facets` (array), `search` (boolean), `form_page` |
 | `master_detail` | `detail` (a table), `detail_column` (its column referring to this table) |
 | `report_form` | `form_page` (required) |
+| `report` | `form_page` (137: an interactive report alone) |
+| `smart_filters` | `facets` (array), `form_page` |
+| `tree` | `id_column`, `parent_column` (proposed: a foreign key to the table itself), `label_column`, `expanded` (levels open), `form_page` |
+| `timeline` | `title`, `when`, `who`, `body`, `form_page` |
+| `media_list`, `content_row` | `title`, `description`, `badge` (also its colour), `misc` (content row), `form_page` |
+| `comments` | `user`, `date`, `comment` |
+| `data_load` | `definition` (a data load definition's name: made for the table unless it exists), `mode` (`append`, `merge`, `replace`), `skip_errors` |
+| `wizard` | `columns` (array; NOT NULL columns without a default always), `steps` (1–10), `return_page` |
+| `search` | `configs` (search configurations by name); with a table: a new configuration on it, and `form_page` |
+| `tasks` | `context` (`my`, `initiated`, `admin`), `completed` (boolean) |
+| `workflows` | `context` (`initiator`, `admin`) |
 
 ```sql
 select meta.generate_page('shop', 'calendar', 'shop.meeting', 12, '{"form_page": 13, "drag": true}');
@@ -488,6 +520,7 @@ navigation entries and application processes have the same `build_option` column
 | `app_ai_service` | Which applications may use which AI service, with daily limits `max_requests` and `max_tokens` (null: no limit). Not exported | no (through `meta.ai_available`) |
 | `ai_usage` | One row per AI request: `at`, `app_id`, `page_no`, `username`, `service`, `provider`, `model`, `source`, `input_tokens`, `output_tokens`, `duration_ms`, `status`, `message` (an error class, never prompt or answer text). Not exported | no |
 | `ai_tool_call` | (121) Every tool call of an [AI assistant or agent](03-builder.md#ai-agents): `at`, `app_id`, `page_no`, `region_id`, `username`, `agent`, `tool`, `type`, `arguments` (the model's, cut to 4 KB), `status` (`ok`, `error`, `refused`), `duration_ms`, `message`. Kept 30 days, not exported | no |
+| `embedding_queue` | (136) Rows whose vector column the server re-embeds: `app_id`, `provider`, `tbl` (the table's oid), `vector_column`, `key_column`, `source_columns`, `key_value`, `queued_at`, `next_at`, `attempts`, `last_error`. Filled by `meta.embedding_enqueue` triggers and Backfill; not exported | no |
 | `ai_conversation` | [AI assistant](04-pages-and-regions.md#ai_assistant-ai-assistant) conversations: one per session and region (`messages`: the provider's history, `turns`: what the page shows); deleted with the session. Not exported | no |
 | `ai_table_note` | Descriptions of tables and columns for models ([App Builder AI](03-builder.md#app-builder-ai)): `schema_name`, `table_name`, `column_name` (`''` for the table), `note`. Installation data, not exported | no |
 | `blueprint` | Saved [blueprints](03-builder.md#creating-an-application-from-a-blueprint): `name`, `spec` (the JSON), `app_id` (the application last created from it), `created_by`. Builder data, not exported | no |

package/docs/guide/12-development.md

@@ -145,6 +145,12 @@ src/
                            scramVerifier (SCRAM-SHA-256, SASLprep) and the password slot (maskSql for review and log, withVerifier to run)
   cron-schedule.ts         (sprint 101, DA-12) pg_cron schedules without a database: parseSchedule (cron fields, $, n seconds, macros),
                            nextRuns in a time zone, describeSchedule in words, the builder's presets and fields
+  vector.ts                (sprint 136, AP-1) pgvector: pgvectorStatus(), vectorSchema() (operators and the type schema-qualified),
+                           DISTANCES (cosine/l2/inner_product: operator, HNSW opclass, similarity), vectorColumnDims(); the embedding
+                           queue (meta.embedding_queue, migration 136): embeddingTick() (groups, FOR UPDATE SKIP LOCKED, batches
+                           within the provider's per-minute limit, written with devDbForApp(), retries with backoff), drainEmbeddings(),
+                           kickEmbeddings(), startEmbeddingRunner() (server.ts; EMBEDDINGS=off, EMBEDDING_INTERVAL_S), vectorTriggers()
+                           (meta.embedding_set / embedding_enqueue triggers and their arguments), backfill(), queueState()
   pgcron.ts                (sprint 101, DA-12) pg_cron for SQL Workshop → Scheduling: cronState (installed, loaded, cron.database_name,
                            access), jobs and runs, jobSql/activeSql/unscheduleSql/purgeSql (reviewed, then applySql), runNow
   secrets.ts               secrets at rest (web credentials): AES-256-GCM with PGKILN_SECRET_KEY (or a key given, for rotate-key);
@@ -176,9 +182,19 @@ src/
                            (121) an agent's effort (Claude output_config.effort, OpenAI reasoning_effort) and output limit).
                            Providers (121): anthropic, openai, gemini (OpenAI-compatible endpoint, GEMINI_BASE_URL), openai_compatible
                            (Ollama, vLLM, Azure OpenAI; base URL required, key optional): service.ts serviceKey(), baseUrlFor(), providerLabel()
+                           (sprint 136, AP-1) embeddings.ts: vector providers (meta.app.vector_providers: ai_service with an embedding
+                           model, or a function), vectorProviderProblems(), embedTexts() (the openai SDK's embeddings API, float
+                           encoding, dimensions checked, daily limits via checkDailyLimit(), meta.ai_usage source "embedding"; a
+                           function provider through meta.embed on the caller's connection), embedQuery() (search texts remembered
+                           10 minutes per process), vectorLiteral()
   debug.ts                 debug messages: DebugLog (levels, timed steps, NOTICEs of meta.debug from appTx), started in
                            loadContext, stored after the response (onResponse hook → meta.debug_save), hourly purge
   icons.ts                 icon helper (sprite in public/icons.svg)
+  history.ts               (sprint 138, AP-5) change history and checksums: meta.app_snapshot (the export after the last recorded
+                           change), recordHistory() (export again, workingcopy.ts components() of both, each added/changed/deleted
+                           component with its files before and after into meta.component_change; called by app-updates.ts onSend,
+                           the upgrade page and cli/replace.ts replaceApp), ensureSnapshot() (before a first change), diffDocs(),
+                           appChecksum() / pageChecksums() (SHA-256 of the text layout without the alias), CHANGE_HISTORY_DAYS
   runtime/
     routes.ts              HTTP handlers: show, submit, dynamic actions, cascading lists, login
     signin.ts              the sign-in form (built-in page and the login region of an application's own login page), safeNext, passwordResetAvailable
@@ -234,7 +250,7 @@ src/
     tree.ts                tree region
     lists.ts               lists: static entries or a query, visibility (authorization, conditions, page access), safe URLs; list regions, navigation menu and bar
     template-components.ts template components: template language (allow-list, directives, escaping), plug-in files, report column templates
-    builtin-components.ts  built-in template components (ut_avatar, ut_badge, ut_comments, ut_media_list, ut_metric_card, ut_timeline)
+    builtin-components.ts  built-in template components (ut_avatar, ut_badge, ut_comments, ut_content_row, ut_media_list, ut_metric_card, ut_timeline)
     template-region.ts     template_component region
     tasks.ts               task list region and task actions (approvals); (094) the vacation rule panel and route;
                            (sprint 114) custom outcome buttons, the Fail event and recovery of a failing completion SQL
@@ -255,7 +271,8 @@ src/
                            definitionProblems), agentFor(), prepareTools() (authorization schemes, navigate pages the user may
                            open, strict schemas), runAgentTool() (sql: read-only transaction as the app role with a time limit;
                            function: named arguments, committed; rest; javascript: queued for the browser; navigate: URL and
-                           checksum built here), logToolCall() (meta.ai_tool_call, debug level 4, 30-day purge)
+                           checksum built here), logToolCall() (meta.ai_tool_call, debug level 4, 30-day purge); (136) retrieve:
+                           retrieveTool() (QUERY only, search.ts retrieve() in a read-only transaction as the app role)
     ai-filter.ts           "Ask in your own words" on a report ("ai_filter", sprint 112: AI interactive reports): the box, the chips
                            form (Edit/Remove/Undo, undo history in the session), ask and chips routes; an AI service's structured
                            output (planSchema) or the phrase parser, then ir-plan.ts
@@ -270,6 +287,10 @@ src/
                            searchable columns), websearch_to_tsquery / ts_rank_cd / ts_headline between private-use markers
                            (headlined() escapes, only the markers become <mark>), textSearchConfig() (pg_ts_config names only,
                            passed as $1::regconfig; tsConfigFor(language)), trigramSchema() and "did you mean" with pg_trgm
+                           (sprint 136, migration 136) search types vector (vectorRows: the text embedded by the provider, nearest
+                           rows by the schema-qualified distance operator, the vector as $1, min_similarity) and hybrid (full-text
+                           and vector rankings, 50 rows each, reciprocal rank fusion 1/(60+rank) per key_column); retrieve() for
+                           an agent's Retrieve tool
     url-region.ts          URL region (migration 078): literal origins only (urlTarget), &ITEM. URL-encoded, sandbox and height,
                            frameOrigins() for the CSP's frame-src (security.ts)
     ajax.ts                Ajax callbacks (migration 085: POST …/ajax/:name, point "ajax" processes, x01 … x10 binds) and the
@@ -293,6 +314,10 @@ src/
                            language links (?lang=, a cookie), meta.developer.language
     routes.ts              sign-in, app home, settings, activity, developers, create (POST, via newapp.ts)/import (POST)
     wizards.ts             create page wizards: step 2 forms per page type (defaults from meta.wizard_defaults), POST → meta.generate_page
+    create-page.ts         (137) Create page: the grid of page types with SVG previews (tabs Component / Feature / Copy), the table step,
+                           Create page as copy (step per app and page, shared components mapped or copied → meta.copy_page)
+    features.ts            (137) Add feature: review (what it adds) and install, once, of Access control, Activity reporting,
+                           Configuration options, E-mail reporting, Feedback, About, Login page, Theme style selection, Push
                            (the generators are PL/pgSQL in migration 047: catalog, defaults, form/cards/calendar/chart/map/facets/master-detail)
     home.ts                App Builder home at /builder/apps and /builder (tiles, applications report/cards, Recent; /builder redirects
                            to the Workspace home when meta.workspace.builder_home = 'home'), Create, Import, Dashboard, Utilities;
@@ -360,6 +385,13 @@ src/
     fulltext.ts            (sprint 135, AP-2) Table Properties › Add full-text search: GET/POST /sql/objects/fulltext?o= (text columns
                            with weights A–D, a configuration from pg_ts_config, fulltextDdl(): a generated tsvector column and a GIN
                            index), Preview / Apply (one transaction, recorded in the Change Log) / Open in the worksheet
+    vector-column.ts       (sprint 136, AP-1) Table Properties › Add vector column: GET/POST /sql/objects/vector?o= (a provider of the
+                           workspace's applications, source columns, distance; vectorDdl(): vector(n), HNSW index, the
+                           meta.embedding_set / embedding_enqueue trigger), Preview / Apply (Change Log; the rows queued) / worksheet;
+                           the table's vector columns with progress and Backfill (mode=backfill, all=on)
+    vector-providers.ts    (sprint 136, AP-1) Shared Components → Vector providers (/apps/:id/vector-providers: list, provider form,
+                           test, delete) and Workspace utilities → Vector providers (/vector-providers: pgvector status, Create
+                           extension for administrators, the workspace's providers and vector columns); pgvectorNote()
     data-security.ts       (sprint 119) a table's Security: GET/POST /sql/objects/security?o= (policies, roles × columns, masks), Preview / Apply
     object-actions.ts      (sprint 94) an object's ⋯ menu (objectMenu) in the worksheet and the Object Browser: Quick DDL (objectDdl), Drop with
                            dependents, Add index / trigger / policy as drafts; GET /sql/objects/action, /sql/objects/panel (Open in a panel)
@@ -389,6 +421,18 @@ src/
     region-settings.ts     page designer: settings forms for grid, chart (gauge, drill-down), cards, calendar (views, create, drag and drop), facets, smart filters, display selector, list
     search.ts              app search, "where used" (appEntries, search, whereUsed, usedInPanel)
     advisor.ts             Advisor: EXPLAIN every SQL fragment, reference checks, plpgsql_check
+    utilities.ts           (sprint 138, AP-5) an application's Utilities tab: tiles, dashboard figures, recently updated pages,
+                           application and page checksums; Change history (filters, diffHtml of a change); the icon browser
+                           /builder/icons; historyHooks() (preHandler: ensureSnapshot before a builder POST of an application)
+    dependencies.ts        (sprint 138) Utilities → Database object dependencies: appDependencies() (the Advisor's fragments, each
+                           parsed as the app role into a BEGIN ATOMIC temp function, one statement by the extended protocol;
+                           pg_depend → tables, views, sequences, functions; missing objects from the parser's errors; privileges
+                           needed vs the role's), the page with Object Browser links
+    upgrade.ts             (sprint 138) Utilities → Upgrade application: upgradeCandidates() (nav_appearance, date_picker,
+                           popup_lov), preview diff, POST upgrade by key or rule (found again first), recorded in the history
+    ui-defaults.ts         (sprint 138) UI defaults /builder/ui-defaults (meta.ui_default, migration 138): per column label, mask,
+                           help, alignment, list of values; seed from comments; tables of the workspace's catalog only. The wizards
+                           read them through meta.wizard_column_label and the meta.item trigger meta.ui_default_item
     ddl-tools.ts           SQL Workshop → DDL and Compare (src/ddl.ts); (sprint 106) the Apply and record form
     changelog.ts           (sprint 106) SQL Workshop → Change Log (/builder/sql/changes): change sets per schema, latest app export,
                            downloads (POST, mark exported_at), rename, delete; /sql/compare/apply (one transaction, recorded)
@@ -505,6 +549,10 @@ test/
   fulltext-search.test.ts  (sprint 135) full-text search configurations: stemming, rank order, highlights, websearch syntax, the
                            configuration fallback, did you mean (pg_trgm when it can be installed), the report search on a tsvector
                            column, the Advisor's GIN check, Add full-text search (preview, apply, change log), export/import
+  vector-search.test.ts    (sprint 136) vector providers and their checks, meta.embed, Add vector column (preview, apply, the queue
+                           with the mock's embeddings, a change queued again, Backfill, a failing batch), vector and hybrid search
+                           ("time off for a family move" → Relocation leave; RLS), the Advisor, Retrieve tools on page 49, the
+                           builder pages, export; skips what needs pgvector when it isn't installed
   object-actions.test.ts   (sprint 94) object menus: Quick DDL, Drop with dependents, Add index / trigger / policy, the panel, not-found
   data-modeler.test.ts     (sprint 98) Data Modeler: "hr core" with its FK lines, saved positions, SVG, objects, DDL, dictionary, geometry
   worksheet.test.ts        (sprint 91) the SQL Worksheet: statement at the cursor, Run Script log, plans, notices, history, navigator, Run as
@@ -566,7 +614,9 @@ test/
   find-workspace.test.ts   developers' addresses, builder mail, the workspaces mail, the same answer, limits
   ai-builder.test.ts       App Builder AI: the builder's service, SQL from a question, explain, describe tables, pages with AI
   ai-script-mock.ts        a scripted mock of Claude (SSE, tool_use with a thinking block) and OpenAI (tool calls), reply by reply
-  ai-mock.ts               a local mock of the Claude Messages API (SSE stream) and OpenAI Chat Completions
+  ai-mock.ts               a local mock of the Claude Messages API (SSE stream) and OpenAI Chat Completions; (136) OpenAI's
+                           embeddings (/embeddings, also in ai-script-mock.ts): conceptEmbedding(), eight "topics", the same
+                           as the HR example's hr.policy_embedding
   helpers.ts               a cookie-keeping test browser
   e2e/responsive.test.ts   browser tests at phone/tablet/desktop widths (Playwright)
   e2e/builder-i18n.test.ts (sprint 121) Deutsch on the sign-in page, the status bar's language menu, German screens at 390 px, CSP

package/docs/guide/15-extensions.md

@@ -63,7 +63,7 @@ that includes them.
 | **[pg_cron](https://github.com/citusdata/pg_cron)** | Run SQL on a schedule inside the database (`select cron.schedule('nightly', '0 2 * * *', 'call hr.close_month()')`) | **Automations**, `DBMS_SCHEDULER` |
 | **[pgaudit](https://github.com/pgaudit/pgaudit)** | Statement-level audit logging (reads, writes, DDL, role changes) to the server log, for compliance | Oracle Unified Auditing |
 | **PostGIS** | Geometry and geography types, spatial indexes and functions: the foundation for a map region | **Map region**, Oracle Spatial |
-| **pgvector** | Vector similarity search (embeddings) for semantic search and retrieval-augmented generation | APEX AI (RAG sources), Oracle AI Vector Search |
+| **pgvector** | Vector similarity search (embeddings) for semantic search and retrieval-augmented generation; pgkiln's vector providers, vector and hybrid search configurations and Retrieve tools use it (sprint 136, [chapter 4](04-pages-and-regions.md#vector-search)) | APEX AI (RAG sources), Oracle AI Vector Search |
 | **[plpgsql_check](https://github.com/okbob/plpgsql_check)** | Static analysis of PL/pgSQL: wrong columns, unused variables, missing `RETURN`, hidden casts. Run it on your app's functions in CI | **Advisor** (for code) |
 
 Scheduling example with pg_cron. pg_cron must be in `shared_preload_libraries` (a server setting;

package/docs/guide/16-files.md

@@ -406,7 +406,7 @@ The HR sample has `EMP_XML`, for XML files like `/static/samples/employees.xml`.
 ### Data loading in an application
 
 For end users, add a page with a `file` item and a button, and a **process of type
-`data_load`**. The process runs **as the application's database role**, so grants, row level
+`data_load`** ((sprint 137) **Create page → Data loading** makes the definition and such a page for a table). The process runs **as the application's database role**, so grants, row level
 security, triggers and the audit trail apply, just as they do for the form.
 
 | `config` key | Meaning |

package/examples/hr/README.md

@@ -43,6 +43,7 @@ Then open http://127.0.0.1:3100/a/hr and sign in as `king`, `blake`, `jones`, `a
 | `hr_64_ai_agent.sql` | *HR agent* (page 46): the AI agent `HR_AGENT` (Shared Components → AI Agents) with four tools: `top_earners` (SQL, read-only as `hr_app`), `open_employee` (navigate: a link to the employee form with its checksum, only for users who may open page 3), `give_raise` (the PL/pgSQL function `hr.give_raise`, managers only) and `note` (a JavaScript tool: the custom event `hr_agent_note`). Ask *Who in Sales earns most?* Needs an AI service named `HR_ASSISTANT` (see part 41) |
 | `hr_68_component_details.sql` | *Component details* (page 47): a popup LOV over 6,000 rows that loads more as the dialog scrolls, a wait popup around a two-second process (*Recalculate*) and around an Ajax call (*Check in the background*), and an *Actions* menu whose entries run dynamic actions (event `menu_entry`) |
 | `hr_71_fulltext_search.sql` | Full-text search: `hr.policy` gets a generated `search_vector` column (title weight A, body B, english) with a GIN index, and the search configuration `POLICIES` (search type *fulltext*, *Did you mean* when `pg_trgm` is installed) joins page 42 *Search*: "works home" finds *Working from home*, the matched words highlighted |
+| `hr_72_vector_search.sql` | Search by meaning: `hr.policy` gets *Relocation leave* and a managers-only *Salary bands* with row level security (`audience`); with pgvector, the vector provider `POLICY_EMBEDDINGS` (a stand-in function, `hr.policy_embedding`, eight topics), `hr.policy.embedding vector(8)` with an HNSW index and a trigger, the hybrid search configuration `POLICIES_MEANING` on page 42 (*time off for a family move* finds *Relocation leave*), and *Policy questions* (page 49): the agent `POLICY_AGENT` with the Retrieve tool `policy_search`. Needs an AI service named `HR_ASSISTANT` for page 49 |
 
 The files run in order, each once (recorded in `public.pgkiln_seed`), so new ones can be added
 later. pgkiln's own tests use this application as their fixture (`npm test` installs it first).

package/examples/hr/hr_72_vector_search.sql

@@ -0,0 +1,158 @@
+-- =====================================================================
+-- HR example, part 72: search by meaning (sprint 136, AP-1; migration
+-- 136; docs/guide/04-pages-and-regions.md "Vector search", 03-builder.md
+-- "Vector providers", 20-ai-agents.md)
+--
+-- hr.policy (parts 42 and 71) gets two more policies and an audience:
+-- "Salary bands" is for managers only, and row level security now shows
+-- hr_app only the policies the user may read. Every search below runs as
+-- hr_app, so an employee never finds the managers' policy.
+--
+-- With pgvector installed (the extension is created here when the server
+-- has it and this connection may; otherwise this part only adds the
+-- policies and says so):
+--
+--   - the vector provider POLICY_EMBEDDINGS (Shared Components → Vector
+--     providers) of type function: hr.policy_embedding(text), a tiny
+--     stand-in for an embedding model that maps words to eight topics
+--     (moving house, time off, home working, sickness, pay, requests,
+--     public holidays, anything else). It keeps the example working without
+--     an AI service; for real use, make the provider an AI service with an
+--     embedding model (e.g. OpenAI text-embedding-3-small, 1536 dimensions,
+--     or Ollama's nomic-embed-text, 768) and add the column again with
+--     Table Properties › Add vector column;
+--   - what Table Properties › Add vector column writes: hr.policy.embedding
+--     vector(8), an HNSW index (vector_cosine_ops) and a trigger
+--     (meta.embedding_set) that embeds a policy when its title or body
+--     changes;
+--   - the search configuration POLICIES_MEANING (search type hybrid:
+--     full-text on search_vector and the embedding, merged by reciprocal
+--     rank fusion) joins page 42 "Search": "time off for a family move"
+--     finds "Relocation leave", which uses none of those words;
+--   - page 49 "Policy questions": an AI assistant region with the agent
+--     POLICY_AGENT, whose Retrieve tool policy_search hands the model the
+--     policies that match a question (as hr_app). Like parts 41, 42 and 64
+--     it needs an AI service named HR_ASSISTANT.
+-- =====================================================================
+
+alter table hr.policy add column audience text not null default 'all' check (audience in ('all', 'managers'));
+
+insert into hr.policy (title, body, audience) values
+  ('Relocation leave', 'Employees who relocate to another city for the company get three paid days to settle into the new house, and help with the removal costs.', 'all'),
+  ('Salary bands', 'Managers review the salary bands every spring; a raise above the band needs the director''s approval.', 'managers');
+
+alter table hr.policy enable row level security;
+create policy policy_visible on hr.policy for select
+  using (audience = 'all' or meta.has_role('manager') or meta.has_role('admin'));
+
+-- a stand-in for an embedding model: each word counts for one of eight topics (unknown words a little for the
+-- last), and the vector is normalised, so the cosine of two texts says how much they share topics
+create function hr.policy_embedding(p_text text) returns real[]
+language sql immutable parallel safe set search_path = pg_catalog as $$
+  with w as (select lower(m[1]) as w from regexp_matches(coalesce(p_text, ''), '([[:alpha:]]+)', 'g') m),
+  d as (select case
+                 when w ~ '^(relocat|move|moving|removal|house|settl|city|family)' then 1
+                 when w ~ '^(leave|time|off|holiday|vacation|days|absence)$' then 2
+                 when w ~ '^(home|remote|working|work)$' then 3
+                 when w ~ '^(sick|ill|doctor)' then 4
+                 when w ~ '^(salar|pay|band|raise|wage|scale)' then 5
+                 when w ~ '^(request|approv|manager)' then 6
+                 when w ~ '^(public|closed|office)' then 7
+                 else 8 end as dim,
+               case when w ~ '^(relocat|move|moving|removal|house|settl|city|family|leave|time|off|holiday|vacation|days|absence|home|remote|working|work|sick|ill|doctor|salar|pay|band|raise|wage|scale|request|approv|manager|public|closed|office)'
+                    then 1.0 else 0.05 end as weight
+          from w),
+  v as (select i, coalesce((select sum(weight) from d where d.dim = i), 0) as x from generate_series(1, 8) i),
+  n as (select sqrt(sum(x * x)) as n from v)
+  select array_agg((case when n.n = 0 then (case when i = 8 then 1 else 0 end) else x / n.n end)::real order by i) from v, n
+$$;
+grant execute on function hr.policy_embedding(text) to hr_app;
+
+update meta.app set
+  vector_providers = vector_providers || $j$[
+    {"name": "POLICY_EMBEDDINGS", "type": "function", "function": "hr.policy_embedding", "dimensions": 8,
+     "description": "A stand-in for an embedding model (eight topics); use an AI service for real texts"}
+  ]$j$::jsonb,
+  ai_tools = ai_tools || $j$[
+    {"name": "policy_search", "type": "retrieve", "search_config": "POLICIES_MEANING", "max_rows": 3,
+     "description": "The HR policies that match a question, best first (title and text). Use it for every question about rules, leave, pay or working arrangements."}
+  ]$j$::jsonb,
+  ai_agents = ai_agents || $j$[
+    {"name": "POLICY_AGENT", "description": "Answers questions about the HR policies the user may read",
+     "service": "HR_ASSISTANT", "effort": "low", "tools": ["policy_search"], "max_steps": 3, "max_tokens": 1500,
+     "system": "You answer questions of &APP_USER. about the company's HR policies. Look the policies up with policy_search and answer only from what it returns; say so when no policy covers the question. Name the policy you used. Be brief."}
+  ]$j$::jsonb
+ where alias = 'hr';
+
+-- page 49: questions about the policies, answered through the Retrieve tool
+insert into meta.page (app_id, page_no, name, title, parent_page)
+select id, 49, 'Policy questions', 'Policy questions', 1 from meta.app where alias = 'hr';
+
+insert into meta.region (page_id, seq, title, type, columns, template, source, condition, config)
+select p.id, r.seq, r.title, r.type, r.cols, 'standard', r.source, r.cond, r.config::jsonb
+  from meta.page p join meta.app a on a.id = p.app_id, (values
+  (10, 'Not set up yet', 'static', 12,
+   '<p class="alert alert-info">Policy questions need the pgvector extension in the database and an AI service named <b>HR_ASSISTANT</b> (App Builder → Workspace utilities → AI services, allowed for the HR application).</p>',
+   'not (meta.ai_available(''HR_ASSISTANT'') and exists (select from pg_catalog.pg_extension where extname = ''vector''))', '{}'),
+  (20, 'Ask about the policies', 'ai_assistant', 8, null,
+   'meta.ai_available(''HR_ASSISTANT'') and exists (select from pg_catalog.pg_extension where extname = ''vector'')',
+   $j${"agent": "POLICY_AGENT",
+       "welcome": "Hello! Ask me about the HR policies, e.g. how much time off you get when you move for the company.",
+       "placeholder": "e.g. Do I get time off for a family move?",
+       "max_turns": 20,
+       "error_message": "The policy assistant could not answer just now. Please try again later."}$j$)
+  ) as r (seq, title, type, cols, source, cond, config)
+ where a.alias = 'hr' and p.page_no = 49;
+
+insert into meta.nav_entry (app_id, seq, label, icon, target_page)
+select id, 30, 'Policy questions', 'book', 49 from meta.app where alias = 'hr';
+
+-- with pgvector: the extension (when this connection may create it), the vector column, the search configuration
+-- and the search page
+do $$
+declare
+  v_schema text;
+begin
+  if not exists (select from pg_extension where extname = 'vector') then
+    if exists (select from pg_available_extensions where name = 'vector') and (select rolsuper from pg_roles where rolname = current_user) then
+      create extension vector;
+    else
+      raise notice 'HR part 72: pgvector is not installed: hr.policy gets no vector column (install pgvector, then add one with Table Properties › Add vector column).';
+      return;
+    end if;
+  end if;
+  select n.nspname into v_schema from pg_extension e join pg_namespace n on n.oid = e.extnamespace where e.extname = 'vector';
+  execute format('alter table hr.policy add column embedding %I.vector(8)', v_schema);
+  execute format('create index policy_embedding_idx on hr.policy using hnsw (embedding %I.vector_cosine_ops)', v_schema);
+  execute format($t$create trigger embedding_embed before insert or update of title, body on hr.policy
+                    for each row execute function meta.embedding_set(%L, 'POLICY_EMBEDDINGS', 'embedding', 'id', 'title', 'body')$t$,
+                 (select id from meta.app where alias = 'hr'));
+  -- the policies there are: embedded now (the trigger does it for new and changed ones)
+  execute format($u$update hr.policy set embedding = translate(meta.embed(meta.embedding_text(to_jsonb(policy), '{title,body}'), 'POLICY_EMBEDDINGS', %s)::text, '{}', '[]')::text::%I.vector$u$,
+                 (select id from meta.app where alias = 'hr'), v_schema);
+  insert into meta.search_config (app_id, name, label, seq, source_type, source, search_type, fts_vector, fts_config,
+                                  vector_provider, vector_column, key_column, distance, min_similarity,
+                                  title_column, description_column, icon, max_results)
+  select id, 'POLICIES_MEANING', 'Policies by meaning', 26, 'table', 'hr.policy', 'hybrid', 'search_vector', 'english',
+         'POLICY_EMBEDDINGS', 'embedding', 'id', 'cosine', 0.6,
+         'title', 'body', 'book', 3
+    from meta.app where alias = 'hr';
+  update meta.region r
+     set config = jsonb_set(r.config, '{configs}', (r.config->'configs') || '["POLICIES_MEANING"]'::jsonb)
+    from meta.page p join meta.app a on a.id = p.app_id
+   where r.page_id = p.id and a.alias = 'hr' and p.page_no = 42 and r.type = 'search';
+end $$;
+
+insert into meta.translation (app_id, language, source, target)
+select a.id, 'nl', t.source, t.target
+  from meta.app a, (values
+  ('Policies by meaning', 'Regelingen op betekenis'),
+  ('Policy questions', 'Vragen over regelingen'),
+  ('Ask about the policies', 'Vraag naar de regelingen'),
+  ('Not set up yet', 'Nog niet ingesteld'),
+  ('Hello! Ask me about the HR policies, e.g. how much time off you get when you move for the company.',
+   'Hallo! Vraag me naar de HR-regelingen, bijv. hoeveel vrij je krijgt als je voor het bedrijf verhuist.'),
+  ('e.g. Do I get time off for a family move?', 'bijv. Krijg ik vrij voor een verhuizing met het gezin?')
+  ) as t (source, target)
+ where a.alias = 'hr'
+on conflict do nothing;

package/examples/hr/hr_73_configuration_options.sql

@@ -0,0 +1,17 @@
+-- =====================================================================
+-- HR example, part 73: a configurable build option (sprint 137, AP-3;
+-- migration 137; docs/guide/06-processing.md "Build options",
+-- 03-builder.md "Add feature")
+--
+-- LEAVE_FORECAST (part 22: the Forecast region of page 22, excluded) is
+-- marked configurable. In the builder, Create page → Feature →
+-- Configuration options then adds page 9020 "Configuration" where HR's
+-- administrators (king, demo) switch the forecast on and off while the
+-- application runs, without a developer. Nothing else changes until that
+-- feature is added.
+-- =====================================================================
+
+update meta.build_option o set configurable = true,
+       description = coalesce(o.description, 'The leave forecast on the leave planner (page 22)')
+  from meta.app a
+ where a.id = o.app_id and a.alias = 'hr' and o.name = 'LEAVE_FORECAST';

package/examples/hr/hr_74_app_utilities.sql

@@ -0,0 +1,22 @@
+-- =====================================================================
+-- HR example, part 74: an application's Utilities (sprint 138, AP-5;
+-- migration 138; docs/guide/03-builder.md "Utilities")
+--
+-- UI defaults (App Builder → Utilities → UI defaults, or Workspace
+-- utilities → UI defaults) for hr.leave_request: the page wizards and the
+-- Create Application wizard label its "days" column "Working days" and
+-- show it with a number format mask, and a generated form item for
+-- "reason" gets a help text. Pages that exist already don't change: create
+-- a form on hr.leave_request (Create Page → Form) to see them.
+--
+-- The rest of the Utilities page needs no example data: Database object
+-- dependencies, Change history (recorded from the next change on),
+-- Upgrade application and the application checksum work on the HR
+-- application as it is.
+-- =====================================================================
+
+insert into meta.ui_default (schema_name, table_name, column_name, label, format_mask, help, alignment, updated_by)
+values
+  ('hr', 'leave_request', 'days', 'Working days', '990', 'Working days the leave takes, without weekends and public holidays.', 'end', 'admin'),
+  ('hr', 'leave_request', 'reason', null, null, 'Optional: what the leave is for. Your manager sees it when deciding.', null, 'admin')
+on conflict (schema_name, table_name, column_name) do nothing;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pgkiln",
-  "version": "0.69.0",
+  "version": "0.71.0",
   "description": "Open source low-code, SQL-driven application builder for PostgreSQL, inspired by Oracle APEX",
   "keywords": [
     "postgresql",

package/public/app.css

@@ -1602,6 +1602,15 @@ img.tc-avatar { object-fit: cover; }
 .tc-media { display: flex; gap: 0.8rem; align-items: center; padding: 0.6rem 0; min-width: 0; overflow-wrap: anywhere; }
 .tc-media > .tc-stack { flex: 1; }
 .tc-media-badge { flex: none; }
+/* (137) ut_content_row: avatar, title and description, secondary text and badge on the right */
+.tc-content-rows { list-style: none; margin: 0; padding: 0; display: flex; flex-direction: column; }
+.tc-content-row { display: flex; gap: 0.8rem; align-items: center; padding: 0.6rem 0; min-width: 0; overflow-wrap: anywhere; }
+.tc-content-row + .tc-content-row { border-top: 1px solid var(--border); }
+.tc-content-row > .tc-stack { flex: 1; }
+.tc-content-row-end { display: flex; flex-direction: column; align-items: flex-end; gap: 0.25rem; flex: none; max-width: 40%; text-align: end; }
+@media (max-width: 480px) { .tc-content-row { flex-wrap: wrap; } .tc-content-row-end { flex-direction: row; align-items: center; max-width: none; margin-inline-start: auto; } }
+/* (137) a checkbox group shown as switches ({"switches": true}): one per line */
+.radio-group.switch-group { flex-direction: column; align-items: flex-start; }
 .tc-metrics { display: grid; grid-template-columns: repeat(auto-fill, minmax(min(100%, 13rem), 1fr)); gap: 0.75rem; }
 .tc-metric { gap: 0.25rem; }
 .tc-metric-label { margin: 0; color: var(--muted); font-size: 0.85rem; font-weight: 600; }