ultravisor 1.0.3 → 1.0.8

package/docs/features/tasks-meadow-api.md

@@ -0,0 +1,163 @@
+# Meadow API Tasks
+
+Tasks for performing CRUD operations against Meadow REST API endpoints, providing database access through the Meadow data access layer.
+
+---
+
+## Meadow Create
+
+Creates a new record via a Meadow REST API endpoint.
+
+### Settings
+
+- **Entity** — Entity (table) name.
+- **Endpoint** — Base URL of the Meadow API server.
+- **DataAddress** — State address of the object containing the record data to create.
+- **Headers** — JSON string of request headers for authentication.
+- **Destination** — State address to store the created record (includes server-generated fields like ID).
+
+### Outputs
+
+- **Created** — The newly created record object with its assigned ID.
+
+### Events
+
+- **Complete** — Fires after the record is created.
+- **Error** — Fires on failure.
+
+### Tips
+
+Build the record data with **Set Values** or **Template String** before passing it to Meadow Create. The created record output includes the server-assigned ID, which you can use in subsequent steps.
+
+---
+
+## Meadow Read
+
+Reads a single record by its ID from a Meadow REST API endpoint.
+
+### Settings
+
+- **Entity** — Entity (table) name to query.
+- **Endpoint** — Base URL of the Meadow API server.
+- **RecordID** — The ID of the record to retrieve.
+- **Destination** — State address to store the retrieved record.
+- **Headers** — JSON string of additional request headers for authentication.
+
+### Outputs
+
+- **Record** — The retrieved record object.
+
+### Events
+
+- **Complete** — Fires after the record is retrieved.
+- **Error** — Fires if the record is not found or the request fails.
+
+### Tips
+
+Use **Set Values** or **Template String** to build the RecordID dynamically from other state values. Pair with **Meadow Update** to read-modify-write a record.
+
+---
+
+## Meadow Reads
+
+Reads multiple records from a Meadow REST API endpoint, with optional filtering and pagination.
+
+### Settings
+
+- **Entity** — Entity (table) name to query.
+- **Endpoint** — Base URL of the Meadow API server.
+- **Filter** — Meadow filter expression to narrow the result set (e.g. `FBV~IDUser~EQ~42~0~`).
+- **Destination** — State address to store the records array.
+- **Headers** — JSON string of request headers for authentication.
+- **PageSize** — Number of records per page (default `100`).
+- **PageNumber** — Zero-based page number (default `0`).
+
+### Outputs
+
+- **Records** — Array of retrieved record objects.
+- **RecordCount** — Number of records returned.
+
+### Events
+
+- **Complete** — Fires after records are retrieved.
+- **Error** — Fires on request failure.
+
+### Tips
+
+Use the Meadow filter expression to limit results server-side for better performance. Combine with **Split Execute** to process each record individually, or with **Comprehension Intersect** to join data from two entities.
+
+---
+
+## Meadow Update
+
+Updates an existing record via a Meadow REST API endpoint.
+
+### Settings
+
+- **Entity** — Entity (table) name.
+- **Endpoint** — Base URL of the Meadow API server.
+- **DataAddress** — State address of the record data to update. Must include the record's ID field.
+- **Headers** — JSON string of request headers for authentication.
+- **Destination** — State address to store the updated record.
+
+### Outputs
+
+- **Updated** — The updated record object.
+
+### Events
+
+- **Complete** — Fires after the update.
+- **Error** — Fires on failure.
+
+### Tips
+
+Use **Meadow Read** first to load the current record, modify the fields you need with **Set Values**, then pass the modified object to Meadow Update. The data object must include the record's primary key field.
+
+---
+
+## Meadow Delete
+
+Deletes a record by its ID via a Meadow REST API endpoint.
+
+### Settings
+
+- **Entity** — Entity (table) name.
+- **Endpoint** — Base URL of the Meadow API server.
+- **RecordID** — The ID of the record to delete.
+- **Headers** — JSON string of request headers for authentication.
+
+### Events
+
+- **Done** — Fires after the record is deleted.
+- **Error** — Fires on failure.
+
+### Tips
+
+Meadow Delete is permanent — consider adding a **Value Input** confirmation step before deleting records in user-facing workflows. Build the RecordID dynamically with template expressions when deleting records identified by earlier processing steps.
+
+---
+
+## Meadow Count
+
+Counts records for an entity via a Meadow REST API endpoint, with optional filtering.
+
+### Settings
+
+- **Entity** — Entity (table) name.
+- **Endpoint** — Base URL of the Meadow API server.
+- **Destination** — State address to store the count value.
+- **Headers** — JSON string of request headers for authentication.
+- **Filter** — Meadow filter expression to count only matching records.
+
+### Outputs
+
+- **Count** — Number of records matching the criteria.
+
+### Events
+
+- **Complete** — Fires after the count is retrieved.
+- **Error** — Fires on failure.
+
+### Tips
+
+Use Meadow Count before **Meadow Reads** to check the result set size, or to report progress statistics. It is much faster than reading all records when you only need the total.

package/docs/features/tasks-user-interaction.md

@@ -0,0 +1,49 @@
+# User Interaction Tasks
+
+Tasks for pausing execution to collect user input or logging diagnostic messages during flow execution.
+
+---
+
+## Value Input
+
+Pauses flow execution and prompts the user for input. The flow resumes when the user provides a value or cancels.
+
+### Settings
+
+- **PromptMessage** — The message displayed to the user (default: "Please provide a value:").
+- **OutputAddress** — State address where the user's input will be stored.
+- **InputType** — Type of input control: `text`, `number`, `boolean`, or `select` (default `text`).
+- **DefaultValue** — Pre-filled default value.
+- **Options** — JSON array of allowed values when InputType is `select`.
+
+### Outputs
+
+- **InputValue** — The value provided by the user.
+
+### Events
+
+- **ValueInputComplete** — Fires when the user submits a value.
+- **Cancelled** — Fires if the user cancels without providing input.
+
+### Tips
+
+Use Value Input for human-in-the-loop workflows: approval gates, manual data entry, or parameter selection at runtime. Wire the Cancelled output to an appropriate fallback path. Use `select` InputType with Options for constrained choices.
+
+---
+
+## Error Message
+
+Logs an error, warning, info, or debug message to the execution log. Use this card to emit diagnostic information during flow execution without halting the workflow.
+
+### Settings
+
+- **MessageTemplate** — The message text to log. Supports Pict template expressions for including state values (default: "An error occurred.").
+- **Level** — Log level: `error`, `warning`, `info`, or `debug` (default `error`).
+
+### Events
+
+- **Complete** — Fires after the message is logged. Execution continues normally.
+
+### Tips
+
+Error Message does not stop the flow — it only records a log entry. Place it on error branches to capture diagnostic context when failures occur. Use the `info` level for progress markers and `debug` for development-time tracing.

package/docs/features/tasks.md

@@ -4,6 +4,20 @@ Tasks are the fundamental unit of work in Ultravisor. Each task represents a
 single executable action: a shell command, an HTTP request, or another
 supported task type.
 
+## Task Reference by Category
+
+For detailed documentation on each built-in task type, see the per-category reference pages:
+
+- [Data Transform](tasks-data-transform.md) — Set values, string manipulation, templates, expressions, CSV parsing, and dataset operations
+- [File System](tasks-file-system.md) — Read, write, copy, and list files on the local file system
+- [Flow Control](tasks-flow-control.md) — Conditionals, loops, sub-operations, and shell commands
+- [HTTP Client](tasks-http-client.md) — GET/POST requests, JSON APIs, and fully configurable REST calls
+- [LLM](tasks-llm.md) — Chat completions, embeddings, and tool use with large language models
+- [Meadow API](tasks-meadow-api.md) — CRUD operations against Meadow REST API endpoints
+- [Content System](tasks-content-system.md) — Remote file operations on Content System beacon workers
+- [Extension](tasks-extension.md) — Low-level Beacon dispatch for remote worker execution
+- [User Interaction](tasks-user-interaction.md) — User input prompts and diagnostic logging
+
 ## Task Model
 
 Every task requires at minimum a `GUIDTask`. All other fields are optional

package/docs/index.html

@@ -9,7 +9,7 @@
 		<title>Documentation</title>
 
 		<!-- Application Stylesheet -->
-		<link href="https://cdn.jsdelivr.net/npm/pict-docuserve@0/dist/css/docuserve.css" rel="stylesheet">
+		<link href="css/docuserve.css" rel="stylesheet">
 		<!-- KaTeX stylesheet for LaTeX equation rendering -->
 		<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/katex@0.16.21/dist/katex.min.css">
 		<!-- PICT Dynamic View CSS Container -->

package/docs/retold-catalog.json

@@ -1,5 +1,5 @@
 {
-	"Generated": "2026-02-11T17:45:35.255Z",
+	"Generated": "2026-03-12T00:32:41.527Z",
 	"GitHubOrg": "stevenvelozo",
 	"DefaultBranch": "master",
 	"Groups": [