pict-section-flow 0.0.12 → 0.0.13

package/example_applications/simple_cards/package.json

@@ -5,6 +5,7 @@
 	"main": "source/Pict-Application-FlowExample.js",
 	"scripts": {
 		"start": "node source/Pict-Application-FlowExample.js",
+		"prebuild": "node ../../scripts/generate-card-help.js",
 		"build": "npx quack build && npx quack copy",
 		"test": "echo \"Error: no test specified\" && exit 0"
 	},

package/example_applications/simple_cards/source/card-help-content.js

@@ -0,0 +1,16 @@
+// Auto-generated by scripts/generate-card-help.js — do not edit manually.
+// Source markdown files are in docs/card-help/
+module.exports = {
+	"EACH": "<h1>Each (Loop Iterator)</h1><p>The <b>Each</b> node iterates over a collection, executing connected downstream nodes once for each item. When iteration completes, the <b>Done</b> output fires.</p><h2>Ports</h2><ul><li><b>Collection</b> (input) — an array or iterable to loop over</li><li><b>Item</b> (output) — fires once per element with the current item</li><li><b>Done</b> (output) — fires after all items have been processed</li></ul><h2>Behavior</h2><p>When a collection arrives at the input port, the Each node processes items sequentially. For every element in the collection, the <b>Item</b> output is activated with the current element as the payload. After the final element is processed, the <b>Done</b> output fires to signal completion.</p><h2>Tips</h2><ul><li>Connect <b>Item</b> to a processing chain and <b>Done</b> to continuation logic</li><li>Nested loops are supported by chaining multiple Each nodes</li><li>Empty collections skip directly to the <b>Done</b> output</li></ul>",
+	"FREAD": "<h1>File Read</h1><p>The <b>File Read</b> node reads the contents of a file from the filesystem and outputs the data.</p><h2>Ports</h2><ul><li><b>Path</b> (input) — the filesystem path to read</li><li><b>Data</b> (output) — the file contents on success</li><li><b>Error</b> (output) — fires if the read operation fails</li></ul><h2>Properties</h2><ul><li><b>FilePath</b> — the path to the file to read</li><li><b>Encoding</b> — character encoding for text files (e.g. <code>utf8</code>, <code>ascii</code>)</li></ul><h2>Behavior</h2><p>When triggered, the node reads the file at the configured path. On success, the raw file contents are emitted from the <b>Data</b> output. If the file does not exist or cannot be read, the <b>Error</b> output fires with a descriptive error message.</p><h2>Tips</h2><ul><li>Use a Get Value node upstream to dynamically set the file path</li><li>Pair with a Data Preview node to inspect the file contents</li><li>Connect the <b>Error</b> output to logging or notification nodes for robust error handling</li></ul>",
+	"FWRITE": "<h1>File Write</h1><p>The <b>File Write</b> node writes data to a file on the filesystem.</p><h2>Ports</h2><ul><li><b>Path</b> (input) — the destination filesystem path</li><li><b>Data</b> (input) — the content to write</li><li><b>Done</b> (output) — fires after a successful write</li><li><b>Error</b> (output) — fires if the write operation fails</li></ul><h2>Behavior</h2><p>When both inputs are satisfied, the node writes the provided data to the specified file path. On success the <b>Done</b> output fires. If the write fails (for example due to permissions or a missing directory), the <b>Error</b> output fires with a descriptive error message.</p><h2>Properties Panel</h2><p>The properties panel shows a View-based info panel with details about the configured file path and write options.</p><h2>Tips</h2><ul><li>Directories in the path are not created automatically — ensure they exist before writing</li><li>Combine with a Set Value node to format data before writing</li><li>Connect the <b>Error</b> output to a Log Values node to capture write failures</li></ul>",
+	"GET": "<h1>Get Value</h1><p>The <b>Get Value</b> node retrieves a named variable from the flow context and emits its current value.</p><h2>Ports</h2><ul><li><b>In</b> (input) — trigger to read the value</li><li><b>Value</b> (output) — the retrieved value</li></ul><h2>Behavior</h2><p>When triggered, the node looks up a named key in the flow context and emits the stored value from the <b>Value</b> output. If the key does not exist, the output value is <code>undefined</code>.</p><h2>Usage</h2><p>Pair with a <b>Set Value</b> node to establish a read/write variable pattern. The Set Value node stores a value under a named key; the Get Value node retrieves it downstream.</p><h2>Tips</h2><ul><li>Variable names are case-sensitive</li><li>Use descriptive variable names to keep flows readable</li><li>Get Value is especially useful for accessing values set in a different branch of the flow</li></ul>",
+	"ITE": "<h1>If-Then-Else</h1><p>The <b>If-Then-Else</b> node evaluates a boolean condition expression and routes the flow to one of two outputs.</p><h2>Ports</h2><ul><li><b>In</b> (input) — trigger that starts the evaluation</li><li><b>Then</b> (output) — activated when the condition is <b>true</b></li><li><b>Else</b> (output) — activated when the condition is <b>false</b></li></ul><h2>Behavior</h2><p>When the input fires, the node evaluates the configured condition expression against the current flow context. If the expression resolves to a truthy value, the <b>Then</b> output is activated. Otherwise, the <b>Else</b> output is activated. Exactly one output fires per evaluation.</p><h2>Configuration</h2><p>Set the condition expression in the node's data properties. The expression is evaluated in the flow context, giving it access to any variables set by upstream Set Value nodes.</p><h2>Tips</h2><ul><li>Chain multiple If-Then-Else nodes for complex branching logic</li><li>Connect the <b>Else</b> output to another If-Then-Else to build else-if chains</li><li>Use descriptive condition expressions to keep the flow self-documenting</li></ul>",
+	"LOG": "<h1>Log Values</h1><p>The <b>Log Values</b> node writes incoming data to the console or log output for debugging purposes.</p><h2>Ports</h2><ul><li><b>Values</b> (input, multi) — accepts one or more connections carrying values to log</li><li><b>Pass</b> (output) — passes the last received value through unchanged</li></ul><h2>Properties</h2><ul><li><b>LogLevel</b> — the severity level for the log entry (e.g. <code>info</code>, <code>warn</code>, <code>error</code>, <code>trace</code>)</li><li><b>Format</b> — an optional format string controlling how values are serialized</li></ul><h2>Behavior</h2><p>When data arrives at any input connection, the node serializes the value and writes it to the configured log output at the specified log level. The data is then forwarded to the <b>Pass</b> output unchanged, so the Log Values node can be inserted inline without disrupting the flow.</p><h2>Tips</h2><ul><li>Use multiple input connections to aggregate log output from parallel branches</li><li>Set the log level to <code>trace</code> during development and <code>warn</code> in production flows</li><li>Insert between any two nodes for quick inline debugging</li></ul>",
+	"NOTE": "<h1>Comment</h1><p>The <b>Comment</b> node is a floating annotation for documenting flow logic. It has no input or output ports and does not participate in data flow execution.</p><h2>Usage</h2><p>Drop a Comment node anywhere on the canvas to add context, explain design decisions, or leave notes for collaborators. The note text is stored in the node's <code>Data.NoteText</code> property and displayed directly in the node body.</p><h2>Properties</h2><ul><li><b>NoteText</b> — the annotation content displayed in the node body</li></ul><h2>Tips</h2><ul><li>Use comments to explain complex branching logic or non-obvious configuration choices</li><li>Comment nodes can be freely repositioned without affecting connections</li><li>Group related comments near the nodes they describe</li></ul>",
+	"PREV": "<h1>Data Preview</h1><p>The <b>Data Preview</b> node displays a tabular summary of the data flowing through it. Use it as an inline debugger to inspect field names, types, and current values without interrupting the flow.</p><h2>Ports</h2><ul><li><b>Data</b> (input) — the data object to inspect</li><li><b>Pass</b> (output) — passes the data through unchanged</li></ul><h2>Behavior</h2><p>The preview renders a compact table inside the node body showing each field's name, inferred data type, and current value. The node is pass-through: data enters on the left and exits on the right without modification.</p><h2>Tips</h2><ul><li>Insert a Data Preview between two nodes to inspect intermediate state</li><li>The preview updates whenever new data arrives at the input port</li><li>Useful during development for verifying data transformations</li></ul>",
+	"SET": "<h1>Set Value</h1><p>The <b>Set Value</b> node assigns a value to a named variable in the flow context.</p><h2>Ports</h2><ul><li><b>In</b> (input) — trigger to perform the assignment</li><li><b>Out</b> (output) — fires after the value has been set</li></ul><h2>Properties</h2><ul><li><b>Variable Name</b> — the key under which the value will be stored</li><li><b>Value Expression</b> — the expression to evaluate and assign</li></ul><h2>Behavior</h2><p>When triggered, the node evaluates the <b>Value Expression</b> and stores the result under the configured <b>Variable Name</b> in the flow context. Downstream nodes can read this value using a <b>Get Value</b> node with the same variable name.</p><h2>Configuration</h2><p>Open the properties panel to configure the variable name and value expression using the built-in form editor.</p><h2>Tips</h2><ul><li>Variable names are case-sensitive — use consistent naming conventions</li><li>Value expressions have access to the current flow context</li><li>Use Set Value at the beginning of a flow to initialize default variables</li></ul>",
+	"SPKL": "<h1>Sparkline</h1><p>The <b>Sparkline</b> node renders a live sparkline chart visualizing numeric throughput data directly in the node body.</p><h2>Ports</h2><ul><li><b>Values</b> (input) — a numeric array or stream of values to plot</li><li><b>Stats</b> (output) — emits computed statistics (min, max, mean) for the data set</li></ul><h2>Behavior</h2><p>The node draws a compact line chart inside the node body using a canvas renderer. As new numeric data arrives at the input, the chart updates to reflect the latest values. The filled area under the line and an endpoint dot provide visual emphasis on the current value.</p><h2>Appearance</h2><p>The chart uses the node's theme color for the line and fill area. The last data point is highlighted with a dot. The sparkline scales automatically to fit the available body area.</p><h2>Tips</h2><ul><li>Connect to any node that produces a numeric array for instant visualization</li><li>Use alongside a Data Preview node for combined visual and tabular inspection</li><li>The Stats output is useful for feeding threshold values into an If-Then-Else node</li></ul>",
+	"STAT": "<h1>Status Monitor</h1><p>The <b>Status Monitor</b> node monitors the health status of upstream services and reports availability.</p><h2>Ports</h2><ul><li><b>Check</b> (input, multi) — accepts connections from one or more services to monitor</li><li><b>Healthy</b> (output) — fires when all monitored services report healthy</li><li><b>Degraded</b> (output) — fires when one or more services report degraded status</li></ul><h2>Behavior</h2><p>The node body displays a visual health grid showing the status of each monitored service with colored indicators. Green indicates a healthy service; yellow indicates degraded performance. When all services are healthy, the <b>Healthy</b> output is activated. If any service reports degraded status, the <b>Degraded</b> output fires instead.</p><h2>Appearance</h2><p>The node body renders SVG status circles labeled with service names (e.g. API, DB, Cache, Queue). Port labels appear on hover for a cleaner default appearance.</p><h2>Tips</h2><ul><li>Connect multiple services to the <b>Check</b> input to build a comprehensive health dashboard</li><li>Route the <b>Degraded</b> output to notification or alerting nodes</li><li>Combine with an Each node to check a dynamic list of service endpoints</li></ul>",
+	"SW": "<h1>Switch</h1><p>The <b>Switch</b> node routes execution to one of multiple outputs based on a matching value, similar to a switch/case statement in programming.</p><h2>Ports</h2><ul><li><b>In</b> (input) — the value to match against cases</li><li><b>Case A</b> (output) — fires when the input matches case A</li><li><b>Case B</b> (output) — fires when the input matches case B</li><li><b>Default</b> (output) — fires when the input does not match any defined case</li></ul><h2>Behavior</h2><p>When a value arrives at the input, the node compares it against each configured case. The first matching case's output is activated. If no case matches, the <b>Default</b> output fires. Only one output is activated per evaluation.</p><h2>Configuration</h2><p>Define case match values in the node's data properties. Each case corresponds to one of the named outputs.</p><h2>Tips</h2><ul><li>Add more output ports by extending the card definition for additional cases</li><li>Use the <b>Default</b> output as a catch-all for unexpected values</li><li>Chain a Switch after an If-Then-Else for multi-level routing logic</li><li>Case matching is based on strict equality</li></ul>"
+};

package/example_applications/simple_cards/source/cards/FlowCard-Comment.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardComment extends libPictFlowCard
 {
@@ -8,6 +9,7 @@ class FlowCardComment extends libPictFlowCard
 			{},
 			{
 				Title: 'Comment',
+				Help: libCardHelp['NOTE'] || false,
 				Name: 'Annotation',
 				Code: 'NOTE',
 				Description: 'A floating annotation or comment node for documenting flow logic.',

package/example_applications/simple_cards/source/cards/FlowCard-DataPreview.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardDataPreview extends libPictFlowCard
 {
@@ -8,6 +9,7 @@ class FlowCardDataPreview extends libPictFlowCard
 			{},
 			{
 				Title: 'Data Preview',
+				Help: libCardHelp['PREV'] || false,
 				Name: 'Inspect Data',
 				Code: 'PREV',
 				Description: 'Displays a preview of the data flowing through this node.',

package/example_applications/simple_cards/source/cards/FlowCard-Each.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardEach extends libPictFlowCard
 {
@@ -8,6 +9,7 @@ class FlowCardEach extends libPictFlowCard
 			{},
 			{
 				Title: 'Each',
+				Help: libCardHelp['EACH'] || false,
 				Name: 'Loop Iterator',
 				Code: 'EACH',
 				Description: 'Iterates over a collection, executing the body for each item.',

package/example_applications/simple_cards/source/cards/FlowCard-FileRead.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardFileRead extends libPictFlowCard
 {
@@ -8,6 +9,7 @@ class FlowCardFileRead extends libPictFlowCard
 			{},
 			{
 				Title: 'File Read',
+				Help: libCardHelp['FREAD'] || false,
 				Name: 'Read File',
 				Code: 'FREAD',
 				Description: 'Reads the contents of a file from the filesystem.',

package/example_applications/simple_cards/source/cards/FlowCard-FileWrite.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardFileWrite extends libPictFlowCard
 {
@@ -8,6 +9,7 @@ class FlowCardFileWrite extends libPictFlowCard
 			{},
 			{
 				Title: 'File Write',
+				Help: libCardHelp['FWRITE'] || false,
 				Name: 'Write File',
 				Code: 'FWRITE',
 				Description: 'Writes data to a file on the filesystem.',

package/example_applications/simple_cards/source/cards/FlowCard-GetValue.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardGetValue extends libPictFlowCard
 {
@@ -8,6 +9,7 @@ class FlowCardGetValue extends libPictFlowCard
 			{},
 			{
 				Title: 'Get Value',
+				Help: libCardHelp['GET'] || false,
 				Name: 'Read Value',
 				Code: 'GET',
 				Description: 'Retrieves a named value from the flow context.',

package/example_applications/simple_cards/source/cards/FlowCard-IfThenElse.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardIfThenElse extends libPictFlowCard
 {
@@ -11,7 +12,7 @@ class FlowCardIfThenElse extends libPictFlowCard
 				Name: 'Conditional Branch',
 				Code: 'ITE',
 				Description: 'Evaluates a condition and routes to the Then or Else branch.',
-				Help: 'The <b>If-Then-Else</b> node evaluates a boolean condition expression and routes the flow to one of two outputs.<br><br><b>Inputs:</b> A single trigger input that starts the evaluation.<br><br><b>Outputs:</b><ul><li><b>Then</b> &mdash; activated when the condition is true</li><li><b>Else</b> &mdash; activated when the condition is false</li></ul><br>Set the condition expression in the node&apos;s data properties.',
+				Help: libCardHelp['ITE'] || false,
 				Icon: 'ITE',
 				Tooltip: 'If-Then-Else: Routes flow based on a boolean condition',
 				Category: 'Control Flow',

package/example_applications/simple_cards/source/cards/FlowCard-LogValues.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardLogValues extends libPictFlowCard
 {
@@ -8,6 +9,7 @@ class FlowCardLogValues extends libPictFlowCard
 			{},
 			{
 				Title: 'Log Values',
+				Help: libCardHelp['LOG'] || false,
 				Name: 'Log to Console',
 				Code: 'LOG',
 				Description: 'Logs input values to the console or log output.',

package/example_applications/simple_cards/source/cards/FlowCard-SetValue.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardSetValue extends libPictFlowCard
 {
@@ -11,7 +12,7 @@ class FlowCardSetValue extends libPictFlowCard
 				Name: 'Assign Value',
 				Code: 'SET',
 				Description: 'Sets a named value in the flow context.',
-				Help: 'The <b>Set Value</b> node assigns a value to a named variable in the flow context.<br><br><b>Variable Name:</b> The key under which the value will be stored.<br><b>Value Expression:</b> The expression to evaluate and assign.<br><br>Downstream nodes can read this value using a <b>Get Value</b> node with the same variable name.',
+				Help: libCardHelp['SET'] || false,
 				Icon: 'SET',
 				Tooltip: 'Set Value: Assign a value in the context',
 				Category: 'Data',

package/example_applications/simple_cards/source/cards/FlowCard-Sparkline.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardSparkline extends libPictFlowCard
 {
@@ -8,6 +9,7 @@ class FlowCardSparkline extends libPictFlowCard
 			{},
 			{
 				Title: 'Sparkline',
+				Help: libCardHelp['SPKL'] || false,
 				Name: 'Metric Chart',
 				Code: 'SPKL',
 				Description: 'Renders a live sparkline visualization of numeric throughput data.',

package/example_applications/simple_cards/source/cards/FlowCard-StatusMonitor.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardStatusMonitor extends libPictFlowCard
 {
@@ -8,6 +9,7 @@ class FlowCardStatusMonitor extends libPictFlowCard
 			{},
 			{
 				Title: 'Status Monitor',
+				Help: libCardHelp['STAT'] || false,
 				Name: 'Health Check',
 				Code: 'STAT',
 				Description: 'Monitors the health status of upstream services and reports availability.',

package/example_applications/simple_cards/source/cards/FlowCard-Switch.js

@@ -1,4 +1,5 @@
 const libPictFlowCard = require('pict-section-flow').PictFlowCard;
+const libCardHelp = require('../card-help-content');
 
 class FlowCardSwitch extends libPictFlowCard
 {
@@ -8,6 +9,7 @@ class FlowCardSwitch extends libPictFlowCard
 			{},
 			{
 				Title: 'Switch',
+				Help: libCardHelp['SW'] || false,
 				Name: 'Multi-way Branch',
 				Code: 'SW',
 				Description: 'Routes flow to one of multiple cases based on a value.',

package/package.json

@@ -1,12 +1,14 @@
 {
     "name": "pict-section-flow",
-    "version": "0.0.12",
+    "version": "0.0.13",
     "description": "Pict Section Flow Diagram",
     "main": "source/Pict-Section-Flow.js",
     "scripts": {
         "test": "npx mocha -u tdd -R spec --exit test/*_tests.js",
         "start": "node source/Pict-Section-Flow.js",
-        "build": "npx quack build"
+        "generate-help": "node scripts/generate-card-help.js",
+        "build": "node scripts/generate-card-help.js && npx quack build && cd example_applications/simple_cards && npx quack build && npx quack copy",
+        "docs": "npx quack prepare-docs ./docs"
     },
     "author": "steven velozo <steven@velozo.com>",
     "license": "MIT",

package/scripts/generate-card-help.js

@@ -0,0 +1,214 @@
+#!/usr/bin/env node
+/**
+ * generate-card-help.js
+ *
+ * Reads markdown files from docs/card-help/ and generates a CommonJS module
+ * that exports an object mapping card codes to rendered HTML strings.
+ *
+ * Each markdown file is named by its card code (e.g. ITE.md, SET.md).
+ * The file content is converted from markdown to HTML and embedded as a
+ * string in the generated module.
+ *
+ * Usage:
+ *   node scripts/generate-card-help.js [source_dir] [output_file]
+ *
+ * Defaults:
+ *   source_dir  = docs/card-help
+ *   output_file = example_applications/simple_cards/source/card-help-content.js
+ *
+ * If the source directory does not exist or contains no markdown files the
+ * script writes an empty map and exits cleanly — the build never fails due
+ * to missing documentation.
+ */
+
+const libFS = require('fs');
+const libPath = require('path');
+
+// ---------------------------------------------------------------------------
+// Minimal markdown-to-HTML converter
+// ---------------------------------------------------------------------------
+// Handles the subset of markdown used in card help documentation:
+//   headings (#, ##, ###), bold (**), italic (*), inline code (`),
+//   unordered lists (- or *), ordered lists (1.), paragraphs, line breaks,
+//   and horizontal rules (---).
+// ---------------------------------------------------------------------------
+
+function convertMarkdownToHTML(pMarkdown)
+{
+	let tmpLines = pMarkdown.split('\n');
+	let tmpHTML = [];
+	let tmpInList = false;
+	let tmpListType = '';
+	let tmpParagraph = [];
+
+	function flushParagraph()
+	{
+		if (tmpParagraph.length > 0)
+		{
+			tmpHTML.push('<p>' + tmpParagraph.join(' ') + '</p>');
+			tmpParagraph = [];
+		}
+	}
+
+	function closeList()
+	{
+		if (tmpInList)
+		{
+			tmpHTML.push(tmpListType === 'ul' ? '</ul>' : '</ol>');
+			tmpInList = false;
+			tmpListType = '';
+		}
+	}
+
+	function inlineFormat(pText)
+	{
+		// Inline code
+		pText = pText.replace(/`([^`]+)`/g, '<code>$1</code>');
+		// Bold (** or __)
+		pText = pText.replace(/\*\*([^*]+)\*\*/g, '<b>$1</b>');
+		pText = pText.replace(/__([^_]+)__/g, '<b>$1</b>');
+		// Italic (* or _)
+		pText = pText.replace(/\*([^*]+)\*/g, '<i>$1</i>');
+		pText = pText.replace(/(?<!\w)_([^_]+)_(?!\w)/g, '<i>$1</i>');
+		// Links
+		pText = pText.replace(/\[([^\]]+)\]\(([^)]+)\)/g, '<a href="$2">$1</a>');
+		return pText;
+	}
+
+	for (let i = 0; i < tmpLines.length; i++)
+	{
+		let tmpLine = tmpLines[i];
+		let tmpTrimmed = tmpLine.trim();
+
+		// Empty line — flush paragraph
+		if (tmpTrimmed === '')
+		{
+			flushParagraph();
+			continue;
+		}
+
+		// Horizontal rule
+		if (/^-{3,}$/.test(tmpTrimmed) || /^\*{3,}$/.test(tmpTrimmed))
+		{
+			flushParagraph();
+			closeList();
+			tmpHTML.push('<hr>');
+			continue;
+		}
+
+		// Headings
+		let tmpHeadingMatch = tmpTrimmed.match(/^(#{1,6})\s+(.*)$/);
+		if (tmpHeadingMatch)
+		{
+			flushParagraph();
+			closeList();
+			let tmpLevel = tmpHeadingMatch[1].length;
+			tmpHTML.push('<h' + tmpLevel + '>' + inlineFormat(tmpHeadingMatch[2]) + '</h' + tmpLevel + '>');
+			continue;
+		}
+
+		// Unordered list item (- or *)
+		let tmpULMatch = tmpTrimmed.match(/^[-*]\s+(.*)$/);
+		if (tmpULMatch)
+		{
+			flushParagraph();
+			if (!tmpInList || tmpListType !== 'ul')
+			{
+				closeList();
+				tmpHTML.push('<ul>');
+				tmpInList = true;
+				tmpListType = 'ul';
+			}
+			tmpHTML.push('<li>' + inlineFormat(tmpULMatch[1]) + '</li>');
+			continue;
+		}
+
+		// Ordered list item (1. 2. etc)
+		let tmpOLMatch = tmpTrimmed.match(/^\d+\.\s+(.*)$/);
+		if (tmpOLMatch)
+		{
+			flushParagraph();
+			if (!tmpInList || tmpListType !== 'ol')
+			{
+				closeList();
+				tmpHTML.push('<ol>');
+				tmpInList = true;
+				tmpListType = 'ol';
+			}
+			tmpHTML.push('<li>' + inlineFormat(tmpOLMatch[1]) + '</li>');
+			continue;
+		}
+
+		// Regular text — accumulate into paragraph
+		closeList();
+		tmpParagraph.push(inlineFormat(tmpTrimmed));
+	}
+
+	flushParagraph();
+	closeList();
+
+	return tmpHTML.join('');
+}
+
+// ---------------------------------------------------------------------------
+// Main
+// ---------------------------------------------------------------------------
+
+let tmpModuleRoot = libPath.resolve(__dirname, '..');
+let tmpSourceDir = process.argv[2]
+	? libPath.resolve(process.argv[2])
+	: libPath.join(tmpModuleRoot, 'docs', 'card-help');
+let tmpOutputFile = process.argv[3]
+	? libPath.resolve(process.argv[3])
+	: libPath.join(tmpModuleRoot, 'example_applications', 'simple_cards', 'source', 'card-help-content.js');
+
+let tmpHelpMap = {};
+
+// Gracefully handle missing source directory
+if (libFS.existsSync(tmpSourceDir))
+{
+	let tmpFiles = libFS.readdirSync(tmpSourceDir).filter(
+		(pFile) => { return pFile.endsWith('.md'); }
+	);
+
+	for (let i = 0; i < tmpFiles.length; i++)
+	{
+		let tmpFile = tmpFiles[i];
+		let tmpCode = libPath.basename(tmpFile, '.md');
+		try
+		{
+			let tmpContent = libFS.readFileSync(libPath.join(tmpSourceDir, tmpFile), 'utf8');
+			let tmpHTML = convertMarkdownToHTML(tmpContent);
+			if (tmpHTML.length > 0)
+			{
+				tmpHelpMap[tmpCode] = tmpHTML;
+			}
+		}
+		catch (pError)
+		{
+			// Skip files that cannot be read — never fail the build
+			console.warn('generate-card-help: skipping ' + tmpFile + ' (' + pError.message + ')');
+		}
+	}
+
+	console.log('generate-card-help: processed ' + Object.keys(tmpHelpMap).length + ' card help files from ' + tmpSourceDir);
+}
+else
+{
+	console.log('generate-card-help: no docs/card-help directory found — generating empty map');
+}
+
+// Ensure output directory exists
+let tmpOutputDir = libPath.dirname(tmpOutputFile);
+if (!libFS.existsSync(tmpOutputDir))
+{
+	libFS.mkdirSync(tmpOutputDir, { recursive: true });
+}
+
+// Write the generated module
+let tmpOutput = '// Auto-generated by scripts/generate-card-help.js — do not edit manually.\n';
+tmpOutput += '// Source markdown files are in docs/card-help/\n';
+tmpOutput += 'module.exports = ' + JSON.stringify(tmpHelpMap, null, '\t') + ';\n';
+
+libFS.writeFileSync(tmpOutputFile, tmpOutput, 'utf8');
+console.log('generate-card-help: wrote ' + tmpOutputFile);

package/source/providers/PictProvider-Flow-CSS.js

@@ -805,14 +805,12 @@ class PictProviderFlowCSS extends libFableServiceProviderBase
 			flex-shrink: 0;
 			transition: background-color 0.15s;
 			border-top: 1px solid var(--pf-panel-titlebar-border);
-			position: relative;
+			display: flex;
+			align-items: center;
+			justify-content: center;
 		}
 		.pict-flow-panel-resize-handle::after {
 			content: '';
-			position: absolute;
-			left: 50%;
-			top: 50%;
-			transform: translate(-50%, -50%);
 			width: 24px;
 			height: 2px;
 			border-radius: 1px;