pict-section-form 1.0.198 → 1.0.200

package/README.md

@@ -1,5 +1,7 @@
 # PICT Forms Section
 
+> **[Read the Pict-Section-Form Documentation](https://fable-retold.github.io/pict-section-form/)** - an interactive guide with live, runnable examples and the full API reference.
+
 A Form Section with programmatically definable content.  Simple, extensible 
 function APIs for adding groups, rows, entry elements and documentation or
 user workflow guidance.
@@ -262,40 +264,38 @@ Each section is represented within a manyfest.  You could have one manyfest for
 }
 ```
 
-This [manyfest](https://github.com/stevenvelozo/manyfest) file describes a list
+This [manyfest](https://github.com/fable-retold/manyfest) file describes a list
 of application state elements. And intersects these data elements with how
 they should be presented to the user in a form.  This can work for any layout
 of data in your application.
 
 ## Documentation
 
-Comprehensive documentation is available in the [docs](docs/) folder:
+The complete documentation - an interactive guide with live examples - is hosted at **[stevenvelozo.github.io/pict-section-form](https://fable-retold.github.io/pict-section-form/)**:
 
 | Document | Description |
 |----------|-------------|
-| [Getting Started](docs/Getting_Started.md) | Quick start guide for new users |
-| [Architecture](docs/Pict_Section_Form_Architecture.md) | System architecture and design |
-| [Configuration](docs/Configuration.md) | Complete configuration reference |
-| [Input Types](docs/Input_Types.md) | Available input types |
-| [Templates](docs/Templates.md) | Template customization and macros |
-| [Solvers](docs/Solvers.md) | Expression solver system |
-| [Providers](docs/Providers.md) | Provider reference |
-| [Layouts](docs/Layouts.md) | Layout types and customization |
+| [Getting Started](https://fable-retold.github.io/pict-section-form/#/page/Getting_Started) | Quick start guide for new users |
+| [Architecture](https://fable-retold.github.io/pict-section-form/#/page/Pict_Section_Form_Architecture) | System architecture and design |
+| [Configuration](https://fable-retold.github.io/pict-section-form/#/page/Configuration) | Complete configuration reference |
+| [Input Types](https://fable-retold.github.io/pict-section-form/#/page/Input_Types) | Available input types |
+| [Templates](https://fable-retold.github.io/pict-section-form/#/page/Templates) | Template customization and macros |
+| [Solvers](https://fable-retold.github.io/pict-section-form/#/page/Solvers) | Expression solver system |
+| [Providers](https://fable-retold.github.io/pict-section-form/#/page/Providers) | Provider reference |
+| [Layouts](https://fable-retold.github.io/pict-section-form/#/page/Layouts) | Layout types and customization |
 
 ### Example Applications
 
-Working examples demonstrating various features:
+Live, runnable example applications - click to open one in your browser:
 
 | Example | Description |
 |---------|-------------|
-| [simple_form](docs/examples/simple_form/) | Basic form with solvers and visibility control |
-| [simple_table](docs/examples/simple_table/) | Minimal tabular layout example |
-| [simple_distill](docs/examples/simple_distill/) | Entity bundles and trigger groups |
-| [gradebook](docs/examples/gradebook/) | Multi-table app with localStorage |
-| [postcard_example](docs/examples/postcard_example/) | Theme switching and navigation |
-| [complex_table](docs/examples/complex_table/) | Full-featured with charts and entity bundles |
-| [complex_tuigrid](docs/examples/complex_tuigrid/) | TuiGrid with aggregations |
-| [manyfest_editor](docs/examples/manyfest_editor/) | Meta-configuration editor |
+| [Simple Table](https://fable-retold.github.io/pict-section-form/examples/simple_table/) | Tabular layout, reference manifests, and dot-notation access into nested data |
+| [Gradebook](https://fable-retold.github.io/pict-section-form/examples/gradebook/) | Stacked headers, row labels, dynamic columns, row/column selection, and sorting |
+| [Scope Mathematics](https://fable-retold.github.io/pict-section-form/examples/scope_mathematics/) | Solvers that reach across sections and the global form scope |
+| [Change Tracking](https://fable-retold.github.io/pict-section-form/examples/change_tracking/) | A change-detecting solver state machine with bidirectional recompute |
+| [NDT Field Test](https://fable-retold.github.io/pict-section-form/examples/ndt_field_test/) | Offline persistence, pick lists, pass/fail row solvers, and charts |
+| [Dynamic Analysis](https://fable-retold.github.io/pict-section-form/examples/dynamic_analysis/) | Runtime section injection, solver rewriting, and solver-driven charts |
 
 ### Input Providers
 
@@ -303,19 +303,19 @@ Specialized input handlers for different data types:
 
 | Provider | Description |
 |----------|-------------|
-| [Select](docs/input_providers/001-select.md) | Dropdown lists with static/dynamic options |
-| [DateTime](docs/input_providers/002-datetime.md) | Date and time picker |
-| [Markdown](docs/input_providers/003-markdown.md) | Markdown content display |
-| [HTML](docs/input_providers/004-html.md) | Raw HTML content display |
-| [PreciseNumber](docs/input_providers/005-precise-number.md) | Formatted numbers with precision |
-| [Link](docs/input_providers/006-link.md) | Hyperlink inputs |
-| [Templated](docs/input_providers/007-templated.md) | Dynamic template rendering |
-| [TemplatedEntityLookup](docs/input_providers/008-templated-entity-lookup.md) | Entity fetch with template display |
-| [Chart](docs/input_providers/009-chart.md) | Chart.js visualizations |
-| [EntityBundleRequest](docs/input_providers/010-entity-bundle-request.md) | Cascading entity fetches |
-| [AutofillTriggerGroup](docs/input_providers/011-autofill-trigger-group.md) | Trigger-based autofill |
-| [TabGroupSelector](docs/input_providers/012-tab-group-selector.md) | Tab navigation for groups |
-| [TabSectionSelector](docs/input_providers/013-tab-section-selector.md) | Tab navigation for sections |
+| [Select](https://fable-retold.github.io/pict-section-form/#/page/input_providers/001-select) | Dropdown lists with static/dynamic options |
+| [DateTime](https://fable-retold.github.io/pict-section-form/#/page/input_providers/002-datetime) | Date and time picker |
+| [Markdown](https://fable-retold.github.io/pict-section-form/#/page/input_providers/003-markdown) | Markdown content display |
+| [HTML](https://fable-retold.github.io/pict-section-form/#/page/input_providers/004-html) | Raw HTML content display |
+| [PreciseNumber](https://fable-retold.github.io/pict-section-form/#/page/input_providers/005-precise-number) | Formatted numbers with precision |
+| [Link](https://fable-retold.github.io/pict-section-form/#/page/input_providers/006-link) | Hyperlink inputs |
+| [Templated](https://fable-retold.github.io/pict-section-form/#/page/input_providers/007-templated) | Dynamic template rendering |
+| [TemplatedEntityLookup](https://fable-retold.github.io/pict-section-form/#/page/input_providers/008-templated-entity-lookup) | Entity fetch with template display |
+| [Chart](https://fable-retold.github.io/pict-section-form/#/page/input_providers/009-chart) | Chart.js visualizations |
+| [EntityBundleRequest](https://fable-retold.github.io/pict-section-form/#/page/input_providers/010-entity-bundle-request) | Cascading entity fetches |
+| [AutofillTriggerGroup](https://fable-retold.github.io/pict-section-form/#/page/input_providers/011-autofill-trigger-group) | Trigger-based autofill |
+| [TabGroupSelector](https://fable-retold.github.io/pict-section-form/#/page/input_providers/012-tab-group-selector) | Tab navigation for groups |
+| [TabSectionSelector](https://fable-retold.github.io/pict-section-form/#/page/input_providers/013-tab-section-selector) | Tab navigation for sections |
 
 ## Installation
 
@@ -345,19 +345,19 @@ formApp.pict.views.PictFormMetacontroller.render();
 
 Pict Section Form is part of the Pict ecosystem:
 
-- [pict](https://github.com/stevenvelozo/pict) - Core application framework
-- [pict-view](https://github.com/stevenvelozo/pict-view) - View base class
-- [pict-provider](https://github.com/stevenvelozo/pict-provider) - Provider base class
-- [manyfest](https://github.com/stevenvelozo/manyfest) - Schema definitions
-- [fable](https://github.com/stevenvelozo/fable) - Service infrastructure
+- [pict](https://github.com/fable-retold/pict) - Core application framework
+- [pict-view](https://github.com/fable-retold/pict-view) - View base class
+- [pict-provider](https://github.com/fable-retold/pict-provider) - Provider base class
+- [manyfest](https://github.com/fable-retold/manyfest) - Schema definitions
+- [fable](https://github.com/fable-retold/fable) - Service infrastructure
 
 ## Related Packages
 
-- [pict](https://github.com/stevenvelozo/pict) - MVC application framework
-- [pict-view](https://github.com/stevenvelozo/pict-view) - View base class
-- [pict-provider](https://github.com/stevenvelozo/pict-provider) - Data provider base class
-- [pict-template](https://github.com/stevenvelozo/pict-template) - Template engine
-- [manyfest](https://github.com/stevenvelozo/manyfest) - Schema-driven object navigation
+- [pict](https://github.com/fable-retold/pict) - MVC application framework
+- [pict-view](https://github.com/fable-retold/pict-view) - View base class
+- [pict-provider](https://github.com/fable-retold/pict-provider) - Data provider base class
+- [pict-template](https://github.com/fable-retold/pict-template) - Template engine
+- [manyfest](https://github.com/fable-retold/manyfest) - Schema-driven object navigation
 
 ## License
 

package/docs/Comprehensions.md

@@ -1,9 +1,9 @@
 # Comprehensions
 
 The `addComprehensionEntity` solver function builds **multi-context, multi-entity
-comprehensions** from form data — a JSON shape that can be inspected, diffed,
+comprehensions** from form data - a JSON shape that can be inspected, diffed,
 and pushed to a Meadow REST API via
-[`meadow-integration load_comprehension`](https://github.com/stevenvelozo/meadow-integration).
+[`meadow-integration load_comprehension`](https://fable-retold.github.io/meadow-integration/).
 
 Think of it as the "save side" of a form: a single function call lays down one
 property of one record under one workflow context, and many calls compose into a
@@ -17,8 +17,8 @@ addComprehensionEntity(Context, Entity, GUID, Property, Value)
 
 | Parameter | Type | Meaning |
 |---|---|---|
-| `Context` | string (manyfest address) | Workflow bucket — `"OnSave"`, `"OnApprovalAction.Approve"`, etc. Dots create nested branches. |
-| `Entity` | string | The entity name — `"Book"`, `"Recipe"`, `"Fruit"`. Opaque key (not parsed). |
+| `Context` | string (manyfest address) | Workflow bucket - `"OnSave"`, `"OnApprovalAction.Approve"`, etc. Dots create nested branches. |
+| `Entity` | string | The entity name - `"Book"`, `"Recipe"`, `"Fruit"`. Opaque key (not parsed). |
 | `GUID` | string | External GUID for the record. Opaque key (dots are NOT interpreted). |
 | `Property` | string | The field to set on the record. Opaque key. |
 | `Value` | any | The value to write. Strings, numbers, booleans, objects, arrays. |
@@ -42,7 +42,7 @@ Given these solvers on a Book form:
 ]
 ```
 
-…the destination ends up looking like:
+...the destination ends up looking like:
 
 ```json
 {
@@ -70,8 +70,8 @@ Given these solvers on a Book form:
 }
 ```
 
-Every leaf in this tree is a Meadow-shaped record keyed by external GUID — the
-exact format [`load_comprehension`](https://github.com/stevenvelozo/meadow-integration)
+Every leaf in this tree is a Meadow-shaped record keyed by external GUID - the
+exact format [`load_comprehension`](https://fable-retold.github.io/meadow-integration/)
 expects.
 
 ## Where the result lands
@@ -88,7 +88,7 @@ metacontroller:
 this.pict.views.PictFormMetacontroller.comprehensionDestinationAddress = 'AppData.MyWorkflowComprehensions';
 ```
 
-…or pass it in the metacontroller view options if you're constructing the
+...or pass it in the metacontroller view options if you're constructing the
 metacontroller manually:
 
 ```js
@@ -100,7 +100,7 @@ If the address resolves to nothing, the function materializes an object there on
 the first write. If it resolves to a non-object scalar, the call logs a warning
 and bails (it won't overwrite a number with an object).
 
-## Basic example — flat OnSave context
+## Basic example - flat OnSave context
 
 ```js
 "Sections":
@@ -125,15 +125,15 @@ the three properties.
 1. **Empty GUIDs bail.** If any of `Context`, `Entity`, `GUID`, or `Property`
    resolves to `null`, `undefined`, or the empty string, the call logs a warning
    and returns `undefined`. Recipes with an empty `RecipeName` will not silently
-   create a `""` bucket — they just no-op until the user fills the name in.
+   create a `""` bucket - they just no-op until the user fills the name in.
 2. **Solver ordinals.** Solvers run in ascending ordinal order. Put your
    `addComprehensionEntity` calls *after* any solvers they depend on (e.g. after
    the `TotalCalories = SUM(...)` aggregate they read from). The complex_table
-   example uses ordinals 200–220 to keep them after the default-ordinal compute
+   example uses ordinals 200-220 to keep them after the default-ordinal compute
    solvers.
 3. **Re-solves overwrite.** Each solve re-runs every solver, so each
    `addComprehensionEntity` call overwrites the property it wrote last time
-   with the current value. This is what you want — the comprehension always
+   with the current value. This is what you want - the comprehension always
    reflects the current form state.
 4. **The destination is *not* cleared between solves.** If your form removes a
    record (e.g. deletes a row from a grid), the previous comprehension for that
@@ -165,17 +165,17 @@ Or write to a file and push from a CLI:
 npx meadow-integration load_comprehension out.json --prefix MYAPP
 ```
 
-See [meadow-integration: Comprehensions](https://github.com/stevenvelozo/meadow-integration/blob/main/docs/comprehensions.md)
-for the full push semantics — GUID marshaling, foreign-key resolution, batch
+See [meadow-integration: Comprehensions](https://github.com/fable-retold/meadow-integration/blob/main/docs/comprehensions.md)
+for the full push semantics - GUID marshaling, foreign-key resolution, batch
 upserts, idempotency.
 
 ## See also
 
-- [Advanced patterns](Comprehensions_Advanced.md) — mixing hashes and direct
+- [Advanced patterns](Comprehensions_Advanced.md) - mixing hashes and direct
   addresses, computed contexts, per-row `MAP VAR` generation, customized
   destinations.
-- [Solvers](Solvers.md) — full solver function reference.
-- The [Complex Table example](../example_applications/complex_table/Complex-Tabular-Application.js)
+- [Solvers](Solvers.md) - full solver function reference.
+- The Complex Table example (`example_applications/complex_table/Complex-Tabular-Application.js`)
   builds a complete `RecipeWorkflowComprehensions` tree with `OnSave` and
   `OnApprovalAction.{Submit,Approve}` contexts off the Recipe section and the
   FruitGrid recordset.

package/docs/Comprehensions_Advanced.md

@@ -1,11 +1,11 @@
-# Comprehensions — Advanced patterns
+# Comprehensions - Advanced patterns
 
 This document goes deeper than [Comprehensions](Comprehensions.md):
 
-- **Hash vs. address arguments** — when to write `BookGUID` (bare symbol),
+- **Hash vs. address arguments** - when to write `BookGUID` (bare symbol),
   `"AppData.Bundle.BookGUID"` (string address), `getvalue("...")` (explicit
   lookup), and when to mix them.
-- **Computed contexts** — `IF`/ternary results as the `Context` argument so a
+- **Computed contexts** - `IF`/ternary results as the `Context` argument so a
   single solver routes between `OnApprovalAction.Submit` and
   `OnApprovalAction.Approve`.
 - **Per-row generation** with `MAP VAR` over a recordset.
@@ -13,22 +13,22 @@ This document goes deeper than [Comprehensions](Comprehensions.md):
 - **Resetting between solves**.
 
 The complete worked example for everything here lives at
-[`example_applications/complex_table/Complex-Tabular-Application.js`](../example_applications/complex_table/Complex-Tabular-Application.js)
-— if you only read one thing, read that file. This page explains the *why* behind
+`example_applications/complex_table/Complex-Tabular-Application.js`
+- if you only read one thing, read that file. This page explains the *why* behind
 the patterns it uses.
 
-## Argument resolution — hashes, addresses, and quoted strings
+## Argument resolution - hashes, addresses, and quoted strings
 
 The solver expression parser treats each argument to `addComprehensionEntity`
 the same way it would treat any other function argument:
 
 | Argument form | What happens |
 |---|---|
-| `BookGUID` | **Bare symbol** — resolved from the form's manifest. Looked up first by descriptor hash, then by address against the marshal destination. |
-| `Record.GUID` / `AppData.Bundle.X` | **Dotted symbol** — resolved as an address (the parser does NOT need quotes around addresses). |
-| `"OnSave"` / `"Book"` | **Quoted string** — taken literally, no resolution. |
-| `getvalue("AppData.X.Y")` | **Explicit lookup** — useful when you want to force address-resolution semantics on a value built up from other solvers. |
-| `IF(...)` / `CONCAT(...)` | **Nested function call** — the inner function's return value becomes the argument. |
+| `BookGUID` | **Bare symbol** - resolved from the form's manifest. Looked up first by descriptor hash, then by address against the marshal destination. |
+| `Record.GUID` / `AppData.Bundle.X` | **Dotted symbol** - resolved as an address (the parser does NOT need quotes around addresses). |
+| `"OnSave"` / `"Book"` | **Quoted string** - taken literally, no resolution. |
+| `getvalue("AppData.X.Y")` | **Explicit lookup** - useful when you want to force address-resolution semantics on a value built up from other solvers. |
+| `IF(...)` / `CONCAT(...)` | **Nested function call** - the inner function's return value becomes the argument. |
 
 In practice you mix freely:
 
@@ -60,10 +60,10 @@ the parser to look the symbol up. The first three arguments are almost always
 literal strings (Context, Entity name) plus one resolved value (GUID); the
 fourth is almost always a literal Property; the fifth is almost always resolved.
 
-## Computed contexts — routing with `IF`
+## Computed contexts - routing with `IF`
 
 The `Context` argument is a manyfest address. It's also just a string that the
-function uses to walk a nested object — which means a *computed* string works
+function uses to walk a nested object - which means a *computed* string works
 fine. The complex_table example routes between `OnApprovalAction.Submit` and
 `OnApprovalAction.Approve` based on a `Proprietary` boolean:
 
@@ -83,7 +83,7 @@ Both `Submit` and `Approve` branches sit under `OnApprovalAction`, which lets
 downstream code key off `Object.keys(comprehension.OnApprovalAction)` to discover
 which actions fired this solve.
 
-The same trick scales to richer routing — e.g. context-per-environment:
+The same trick scales to richer routing - e.g. context-per-environment:
 
 ```js
 `addComprehensionEntity(
@@ -111,7 +111,7 @@ the row bound to a name you choose (`row` is the convention). Combined with
 { Ordinal: 210, Expression: `MAP VAR row FROM FruitData.FruityVice : addComprehensionEntity("OnSave", "Fruit", row.name, "Calories", row.nutritions.calories)` }
 ```
 
-Inside the body, `row.X.Y` resolves against each row in turn — so you get
+Inside the body, `row.X.Y` resolves against each row in turn - so you get
 deep-property access without writing per-row solvers.
 
 After the solve runs against the bundled FruityVice data, the comprehension at
@@ -141,13 +141,13 @@ row, you have two reasonable options:
 
 ## Customizing the destination
 
-Each metacontroller has a `comprehensionDestinationAddress` property —
-mirroring the existing `viewMarshalDestination` knob — that controls where
+Each metacontroller has a `comprehensionDestinationAddress` property -
+mirroring the existing `viewMarshalDestination` knob - that controls where
 `addComprehensionEntity` writes. The default is `AppData.FormEntityComprehensions`.
 
 ### Option 1: in the application constructor
 
-This is what the [complex_table example](../example_applications/complex_table/Complex-Tabular-Application.js)
+This is what the complex_table example (`example_applications/complex_table/Complex-Tabular-Application.js`)
 does. After `super()` (which registers the metacontroller view via
 `PictFormApplication`), set the destination directly:
 
@@ -240,7 +240,7 @@ missing-or-emptied destination by re-materializing it on the next write.
 
 ## Full reference: the complex_table sample config
 
-The [complex_table example](../example_applications/complex_table/Complex-Tabular-Application.js)
+The complex_table example (`example_applications/complex_table/Complex-Tabular-Application.js`)
 exercises every pattern on this page in one application. The relevant pieces:
 
 ```js
@@ -290,6 +290,6 @@ comprehensions -- reach for the meadow-integration toolchain directly:
 - `meadow-integration comprehensionintersect` to merge two comprehensions.
 - The `Comprehension` object's `Object.assign` semantics for in-code merges.
 
-See [meadow-integration: Comprehensions](https://github.com/stevenvelozo/meadow-integration/blob/main/docs/comprehensions.md)
+See [meadow-integration: Comprehensions](https://github.com/fable-retold/meadow-integration/blob/main/docs/comprehensions.md)
 for those tools. The solver helper is purpose-built for "as I edit this form,
 build the comprehension that will save it."

package/docs/Layouts.md

@@ -170,7 +170,7 @@ an array of cells.
 | Cell property | Type | Description |
 |---------------|------|-------------|
 | `Label` | string | Header text |
-| `ColumnSpan` | number | Number of data columns this cell spans (default 1) — this is how you "cluster" |
+| `ColumnSpan` | number | Number of data columns this cell spans (default 1) - this is how you "cluster" |
 | `CSSClass` | string | Optional class applied to the `<th>` |
 
 ```json
@@ -201,7 +201,7 @@ of the table (before the data columns). Each entry describes one label column.
 | Property | Type | Description |
 |----------|------|-------------|
 | `Name` | string | Header text for the label column |
-| `Template` | string | A Pict template resolved per row — the row record is at `Record.Value`, the row index at `Record.Key` |
+| `Template` | string | A Pict template resolved per row - the row record is at `Record.Value`, the row index at `Record.Key` |
 | `RowNumber` | boolean | When `true`, the label is the 1-based row number |
 | `SourceAddress` | string | An app-data address of a pre-slotted array; element `[rowIndex]` is the label |
 | `Cluster` | boolean | When `true`, consecutive equal labels collapse into one cell with `rowspan` |
@@ -217,14 +217,14 @@ Provide exactly one of `Template`, `RowNumber`, or `SourceAddress` per entry.
 ]
 ```
 
-`Cluster: true` is what produces the "merged cell" look — a column of repeated
+`Cluster: true` is what produces the "merged cell" look - a column of repeated
 values (e.g. a class section) renders as a single tall cell spanning its run
 of rows. Any label column may be clustered; there is no "prime" label column.
 
 ### Dynamic Columns
 
 `DynamicColumns` generates table columns at runtime from **another array** in
-the form data — for example, one grade column per assignment. Each entry is a
+the form data - for example, one grade column per assignment. Each entry is a
 generator:
 
 | Property | Type | Description |
@@ -233,7 +233,7 @@ generator:
 | `HashTemplate` | string | Template producing each column's unique descriptor hash |
 | `NameTemplate` | string | Template producing each column's header text |
 | `InformaryDataAddressTemplate` | string | Template producing the per-row data address the cell binds to |
-| `HeaderGroupTemplate` | string | Optional — template producing a cluster label; auto-adds a clustered super-header row |
+| `HeaderGroupTemplate` | string | Optional - template producing a cluster label; auto-adds a clustered super-header row |
 | `DataType` | string | Data type for the generated descriptors |
 | `PictForm` | object | `PictForm` block merged onto each generated descriptor (e.g. `InputType`) |
 | `InsertAt` | string/object | `"End"` (default), `"Start"`, or `{ "After": "<hash>" }` |
@@ -256,7 +256,7 @@ Inside each template the **source row** is the record (`Record.Field`).
 
 Dynamic columns are **non-destructive**: when a source row is removed the
 generated column disappears, but the underlying row data at the
-`InformaryDataAddress` is left untouched — re-adding the source row brings the
+`InformaryDataAddress` is left untouched - re-adding the source row brings the
 column back with its data intact. The columns re-resolve automatically as the
 source array changes; no manual refresh call is needed.
 
@@ -272,7 +272,7 @@ controls where:
 
 | Value | Behavior |
 |-------|----------|
-| `"right"` | Default — controls in a trailing column |
+| `"right"` | Default - controls in a trailing column |
 | `"left"` | Controls in a leading column, before the data columns |
 | `"hidden"` | No editing controls (read-only style table) |
 
@@ -283,7 +283,7 @@ controls where:
 ### Suppressing the Default Header Row
 
 Set `SuppressDefaultColumnHeaderRow: true` to omit the prime column-name row
-entirely — useful when custom `Headers` rows fully describe the columns.
+entirely - useful when custom `Headers` rows fully describe the columns.
 
 ### Selectable Rows & Columns
 
@@ -315,8 +315,8 @@ array lives in the marshalled form data it round-trips with save / load.
 
 ### Column Sorting
 
-`ColumnSorting: true` (off by default) injects a clickable sort control — a
-`<span>` carrying a sort SVG glyph from Pict's icon registry — into every
+`ColumnSorting: true` (off by default) injects a clickable sort control - a
+`<span>` carrying a sort SVG glyph from Pict's icon registry - into every
 prime header cell.
 
 ```json

package/docs/Pict_Section_Form_Architecture.md

@@ -32,25 +32,8 @@ The framework follows several key principles:
 
 The view layer consists of two primary classes:
 
-```
-┌─────────────────────────────────────────────────────────────────┐
-│                    PictFormMetacontroller                        │
-│   - Manages multiple form sections                               │
-│   - Orchestrates data marshaling                                 │
-│   - Controls solver execution                                    │
-│   - Handles initial bundle loading                               │
-└─────────────────────────────────────────────────────────────────┘
-                              │
-                              │ manages
-                              ▼
-┌─────────────────────────────────────────────────────────────────┐
-│                    PictViewDynamicForm                           │
-│   - Represents a single form section                             │
-│   - Maintains section manifest instance                          │
-│   - Handles input provider lifecycle                             │
-│   - Manages group and row structures                             │
-└─────────────────────────────────────────────────────────────────┘
-```
+<!-- bespoke diagram: edit diagrams/views.mmd or .hints.json, then: npx pict-renderer-graph build modules/pict/pict-section-form/docs -->
+![Views](diagrams/views.svg)
 
 **PictViewDynamicForm** extends `pict-view` and represents a single form section.
 It maintains:
@@ -95,29 +78,24 @@ for export and editing.
 
 ### Rendering Flow
 
-```
-1. Application instantiates PictFormMetacontroller
-2. For each Section in manifest:
-   a. PictViewDynamicForm is created
-   b. ManifestFactory parses descriptors into groups and rows
-   c. MetatemplateGenerator creates layout templates
-3. Forms are rendered to DOM using template hierarchy
-4. Solvers are executed (expressions resolve values)
-5. Input providers initialize UI controls
-6. Event handlers attach for changes
-```
+1. The application instantiates the `PictFormMetacontroller`.
+2. For each section in the manifest, a `PictViewDynamicForm` is created,
+   `ManifestFactory` parses its descriptors into groups and rows, and
+   `MetatemplateGenerator` builds the layout templates.
+3. The forms render to the DOM through the template hierarchy.
+4. Solvers execute - expressions resolve their values.
+5. Input providers initialize the UI controls.
+6. Event handlers attach for change detection.
 
 ### Data Change Flow
 
-```
-1. User modifies input value
-2. dataChanged() called on PictViewDynamicForm
-3. Informary marshals specific input from DOM to AppData
-4. Input providers run onDataChange hooks
-5. Application.solve() executes all solvers
-6. Metacontroller marshals all sections back to view
-7. Input providers run onDataMarshalToForm hooks
-```
+1. The user modifies an input value.
+2. `dataChanged()` is called on the `PictViewDynamicForm`.
+3. Informary marshals that input from the DOM into `AppData`.
+4. Input providers run their `onDataChange` hooks.
+5. `Application.solve()` executes all solvers.
+6. The metacontroller marshals every section back to the view.
+7. Input providers run their `onDataMarshalToForm` hooks.
 
 ### Marshal Operations
 
@@ -131,20 +109,8 @@ to map form elements to their corresponding data addresses.
 
 Templates are rendered in a strict hierarchy:
 
-```
-Form Container
-└── Section (for each)
-    ├── Section Prefix
-    └── Group (for each)
-        ├── Group Prefix
-        └── Row (for each)
-            ├── Row Prefix
-            ├── Input (for each)
-            │   └── Input Template (by InputType or DataType)
-            └── Row Postfix
-        └── Group Postfix
-    └── Section Postfix
-```
+<!-- bespoke diagram: edit diagrams/template-hierarchy.mmd or .hints.json, then: npx pict-renderer-graph build modules/pict/pict-section-form/docs -->
+![Template Hierarchy](diagrams/template-hierarchy.svg)
 
 Templates support three levels of customization:
 1. **View-specific** - Templates specific to a single view instance

package/docs/README.md

@@ -73,17 +73,10 @@ npm install pict-section-form
 - [Providers](Providers.md) - Provider reference
 - [Layouts](Layouts.md) - Layout types and customization
 
-## Example Applications
-
-- [simple_form](examples/simple_form/) - Basic form with solvers and visibility control
-- [simple_table](examples/simple_table/) - Minimal tabular layout example
-- [gradebook](examples/gradebook/) - Advanced tabular recordsets: stacked headers, row labels, dynamic columns, selection, sorting
-- [complex_table](examples/complex_table/) - Full-featured with charts and entity bundles
-
 ## Related Packages
 
-- [pict](https://github.com/stevenvelozo/pict) - Core application framework
-- [pict-view](https://github.com/stevenvelozo/pict-view) - View base class
-- [pict-provider](https://github.com/stevenvelozo/pict-provider) - Provider base class
-- [manyfest](https://github.com/stevenvelozo/manyfest) - Schema definitions
-- [fable](https://github.com/stevenvelozo/fable) - Service infrastructure
+- [pict](https://fable-retold.github.io/pict/) - Core application framework
+- [pict-view](https://fable-retold.github.io/pict-view/) - View base class
+- [pict-provider](https://fable-retold.github.io/pict-provider/) - Provider base class
+- [manyfest](https://fable-retold.github.io/manyfest/) - Schema definitions
+- [fable](https://fable-retold.github.io/fable/) - Service infrastructure

package/docs/Solvers.md

@@ -213,10 +213,10 @@ aggregate values from arrays:
 
 ### Tabular Row & Column Styling
 
-These functions style a whole row or whole column of a tabular group — every
+These functions style a whole row or whole column of a tabular group - every
 cell across or down. The highlight pair toggles a CSS class on a `1` / `0`
 flag; the color pair sets (`1`) or clears (`0`) an inline background color.
-None of them touch form data — they are purely presentational and re-applied
+None of them touch form data - they are purely presentational and re-applied
 on each solve.
 
 | Function | Description |
@@ -265,7 +265,7 @@ presentation.
 The `Context` argument is treated as a manyfest address, so dotted contexts
 like `"OnApprovalAction.Approve"` produce nested context branches. Successive
 calls accumulate properties on the same record. See [Comprehensions](Comprehensions.md)
-for the basic walkthrough and [Comprehensions — Advanced](Comprehensions_Advanced.md)
+for the basic walkthrough and [Comprehensions - Advanced](Comprehensions_Advanced.md)
 for computed contexts, `MAP VAR` patterns, and customized destinations.
 
 #### Comprehension Example
@@ -422,4 +422,4 @@ Use in solvers:
 - [Architecture](Pict_Section_Form_Architecture.md) - Solver system internals
 - [Input Types](Input_Types.md) - Input visibility control
 - [Comprehensions](Comprehensions.md) - `addComprehensionEntity` basics
-- [Comprehensions — Advanced](Comprehensions_Advanced.md) - Computed contexts, `MAP VAR`, customized destinations
+- [Comprehensions - Advanced](Comprehensions_Advanced.md) - Computed contexts, `MAP VAR`, customized destinations

package/docs/Templates.md

@@ -7,35 +7,8 @@ Templates can be customized at multiple levels to achieve any desired appearance
 
 Templates are rendered in a strict hierarchical order:
 
-```
-Form Level
-├── -Template-Form-Container-Header
-├── -Template-Form-Container-Wrap-Prefix
-│
-└── For each Section:
-    ├── -Template-Form-Container
-    │
-    └── -Template-Wrap-Prefix
-        ├── -Template-Section-Prefix
-        │
-        └── For each Group:
-            ├── -Template-Group-Prefix
-            │
-            └── For each Row:
-                ├── -Template-Row-Prefix
-                │   ├── For each Input:
-                │   │   └── -Template-Input-InputType-{type}
-                │   │      OR -Template-Input-DataType-{type}
-                │   │      OR -TabularTemplate-*
-                │   └── -Template-Row-Postfix
-                │
-                └── -Template-Group-Postfix
-        │
-        └── -Template-Section-Postfix
-    └── -Template-Wrap-Postfix
-│
-└── -Template-Form-Container-Wrap-Postfix
-```
+<!-- bespoke diagram: edit diagrams/template-hierarchy-2.mmd or .hints.json, then: npx pict-renderer-graph build modules/pict/pict-section-form/docs -->
+![Template Hierarchy](diagrams/template-hierarchy-2.svg)
 
 ## Template Resolution
 

package/docs/_cover.md

@@ -7,5 +7,16 @@
 - Expression solvers for calculated fields and conditional logic
 - Extensible input types and flexible templates
 
-[GitHub](https://github.com/stevenvelozo/pict-section-form)
+[GitHub](https://github.com/fable-retold/pict-section-form)
 [Get Started](#pict-section-form)
+
+<!-- docuserve:examples:start -->
+| Example | Complexity | Launch |
+|---------|------------|--------|
+| [Change Tracking](examples/change%5Ftracking/README.md) | Intermediate | [Launch](examples/change%5Ftracking/index.html) |
+| [Dynamic Analysis](examples/dynamic%5Fanalysis/README.md) | Advanced | [Launch](examples/dynamic%5Fanalysis/index.html) |
+| [Gradebook](examples/gradebook/README.md) | Intermediate | [Launch](examples/gradebook/index.html) |
+| [NDT Field Test](examples/ndt%5Ffield%5Ftest/README.md) | Advanced | [Launch](examples/ndt%5Ffield%5Ftest/index.html) |
+| [Scope Mathematics](examples/scope%5Fmathematics/README.md) | Intermediate | [Launch](examples/scope%5Fmathematics/index.html) |
+| [Simple Table](examples/simple%5Ftable/README.md) | Basic | [Launch](examples/simple%5Ftable/index.html) |
+<!-- docuserve:examples:end -->