Release prep docs for issue 198 (#199)

* Add release prep docs and blog for issue 198

* version updates

Author: eviltester

apps/api/CHANGELOG.md

@@ -1,5 +1,16 @@
 # @anywaydata/api
 
+## 2.4.0
+
+### Minor Changes
+
+- n-wise generation and ui tidy
+
+### Patch Changes
+
+- Updated dependencies
+  - @anywaydata/core@1.4.0
+
 ## 2.3.0
 
 ### Minor Changes

apps/api/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anywaydata/api",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "type": "module",
   "private": false,
   "bin": {

apps/cli/CHANGELOG.md

@@ -1,5 +1,16 @@
 # @anywaydata/cli
 
+## 0.4.0
+
+### Minor Changes
+
+- n-wise generation and ui tidy
+
+### Patch Changes
+
+- Updated dependencies
+  - @anywaydata/core@1.4.0
+
 ## 0.3.0
 
 ### Minor Changes

apps/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anywaydata/cli",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "type": "module",
   "private": false,
   "bin": {

apps/mcp/CHANGELOG.md

@@ -1,5 +1,16 @@
 # @anywaydata/mcp
 
+## 2.4.0
+
+### Minor Changes
+
+- n-wise generation and ui tidy
+
+### Patch Changes
+
+- Updated dependencies
+  - @anywaydata/core@1.4.0
+
 ## 2.3.0
 
 ### Minor Changes

apps/mcp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anywaydata/mcp",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "type": "module",
   "private": false,
   "bin": {

docs-src/blog/2026-06-12-release-prep-combinatorial-grid-workflows.md

@@ -0,0 +1,211 @@
+---
+slug: release-prep-combinatorial-grid-workflows
+title: "Release Prep: Stronger Combinatorial Generation and Faster Grid Workflows"
+authors: [alan]
+tags: [release, feature, combinatorial, schema, import, export, ux]
+date: 2026-06-12T10:00
+---
+
+The next release is centered on one theme: faster paths from existing data to realistic, constrained, exportable test sets.
+
+This release adds broader combinatorial generation, schema authoring improvements, better import/export controls, and a few high-value grid usability upgrades.
+
+<!-- truncate -->
+
+## 1. N-wise combinatorial generation, not just pairwise
+
+The biggest addition is that combinatorial generation now goes beyond pairwise.
+
+Instead of stopping at 2-wise coverage, you can now choose stronger coverage levels for enum-driven schemas and compare strategies before generating.
+
+Example schema:
+
+```text
+Browser: Chrome,Firefox,Safari
+Device: Desktop,Tablet,Mobile
+Locale: en-GB,en-US,fr-FR
+Theme: Light,Dark
+```
+
+With this schema you can choose:
+
+- `2-wise` to cover every pair of enum values
+- `3-wise` to cover every triplet
+- stronger levels when you need more interaction coverage
+
+This is especially useful when pairwise is too light, but full Cartesian generation would explode the row count.
+
+Docs:
+
+- [N-Wise Testing](/docs/test-data/n-wise-testing)
+- [Pairwise Testing](/docs/test-data/pairwise-testing)
+
+![N-wise combinations dialog](/img/release-198/n-wise-generation.png)
+
+## 2. Schema constraints with PICT-style `IF ... THEN ...`
+
+Schema constraints make generated combinations more realistic by filtering out invalid rows.
+
+Example:
+
+```text
+Priority
+enum("High","Medium","Low")
+Status
+enum("Open","Queued","Closed")
+Escalated
+enum("Yes","No")
+
+IF [Priority] = "High" THEN [Status] = "Open";
+IF [Priority] IN {"High","Medium"} THEN [Escalated] = "Yes";
+```
+
+This means:
+
+- high-priority items must be open
+- high and medium priorities must be escalated
+
+Constraints work well with enum-heavy decision tables and combinatorial generation, giving you more realistic output without manually cleaning results afterward.
+
+Docs:
+
+- [Schema Definition](/docs/test-data/Schema-Definition)
+
+## 3. Grid to Enum Schema for turning existing tables into generators
+
+If you already have representative data in the main grid, you can now turn that grid into an enum schema automatically.
+
+Example grid:
+
+```text
+Browser,Device,Theme
+Chrome,Desktop,Light
+Firefox,Mobile,Dark
+Chrome,Tablet,Dark
+```
+
+Generated schema:
+
+```text
+Browser
+enum("Chrome","Firefox")
+Device
+enum("Desktop","Mobile","Tablet")
+Theme
+enum("Light","Dark")
+```
+
+This is one of the most practical workflow improvements in the release because it shortens the path from imported examples to reusable generation rules.
+
+Docs:
+
+- [Data Grid Editable](/docs/test-data/data-grid-editable)
+
+![Grid to enum schema in the app](/img/release-198/grid-to-enum-schema.png)
+
+## 4. PICT-style inline enum definitions such as `Name: values`
+
+Schema text now fits more naturally with compact PICT-style authoring.
+
+Example:
+
+```text
+Browser: Chrome,Firefox,Safari
+Theme: Light,Dark
+Priority: enum("High","Medium","Low")
+Owner: person.fullName
+```
+
+That means you can mix:
+
+- raw inline enum values
+- explicit `enum(...)`
+- other command-based field definitions
+
+This makes it easier to paste or adapt schemas from existing combinatorial models instead of rewriting them into a stricter two-line format.
+
+Docs:
+
+- [Schema Definition](/docs/test-data/Schema-Definition)
+
+## 5. Import trimming controls for cleaner amend and import workflows
+
+Imported files and clipboard data can now be normalized during import.
+
+You can trim:
+
+- every imported field value
+- only selected fields
+
+Example selected fields list:
+
+```text
+Name, Email
+```
+
+This helps when imported files contain accidental whitespace around values, but you do not want to aggressively rewrite every column.
+
+Docs:
+
+- [Import From File](/docs/editing-data/import-from-file)
+
+![Import trim settings](/img/release-198/import-trim-settings.png)
+
+## 6. File export settings for line endings and BOM
+
+Downloads now support file transport settings without changing the preview text shown in the browser.
+
+You can configure:
+
+- `LF` or `Windows (CR/LF)` line endings
+- optional UTF-8 `BOM`
+
+This is useful when exporting for spreadsheets, Windows tooling, or downstream systems that are sensitive to file encoding details.
+
+Docs:
+
+- [Exporting Data](/docs/editing-data/exporting-data)
+
+![Download encoding settings](/img/release-198/export-encoding-settings.png)
+
+## 7. Right-click context menu in the main data grid
+
+The editable grid now has a right-click context menu for common grid actions.
+
+This keeps more of the workflow close to the current selection and makes the app feel more like a direct data-work surface rather than a form with a grid attached to it.
+
+Docs:
+
+- [Data Grid Editable](/docs/test-data/data-grid-editable)
+
+## 8. Always-visible total row counts in the data grid
+
+The main grid now shows total row counts, and filtered views also show how many rows remain visible.
+
+Examples:
+
+```text
+Total rows: 125
+```
+
+```text
+Total rows: 125 | Filtered Visible: 12
+```
+
+It is a small change, but it removes friction during import checks, filtered analysis, and post-generation review.
+
+Docs:
+
+- [Data Grid Editable](/docs/test-data/data-grid-editable)
+
+## Why should you care?
+
+Taken together, these features make the tool better at moving through the whole workflow:
+
+1. start with imported or hand-edited data
+2. convert it into a schema
+3. add constraints
+4. generate the right amount of combinatorial coverage
+5. export in the format and file encoding you actually need
+
+The release adds more generation power, reduces setup time, and cleanup time around that generation.

docs-src/docs/020-editing-data/020-import-from-file.md

@@ -20,4 +20,42 @@ The data will then be loaded into the Data Grid for editing via the grid, and sh
 
 Once a file format tab has been selected it is also possible to drag and drop a file on to the GUI to start an import.
 
-e.g. if `CSV` tab is chosen then the Drop Zone will read `[Drag And Drop .csv File Here]`, allowing you to drag and drop a file to this area to trigger an import.
+e.g. if `CSV` tab is chosen then the Drop Zone will read `[Drag And Drop .csv File Here]`, allowing you to drag and drop a file to this area to trigger an import.
+
+## Import settings
+
+The `Import settings` disclosure lets you normalize imported data before it is loaded into the grid.
+
+### Trim every imported value
+
+Enable trimming when your source file contains accidental leading or trailing whitespace in cells.
+
+Example:
+
+```text
+" Alice "," active "
+```
+
+Imported with trim enabled becomes:
+
+```text
+"Alice","active"
+```
+
+### Trim only selected fields
+
+If you only want to normalize certain columns, turn on selected-field trimming and provide a comma-separated list of field names.
+
+Example field list:
+
+```text
+Name, Email
+```
+
+This is useful when:
+
+- imported identifiers should keep whitespace exactly as-is
+- human-entered fields such as `Name` or `Email` need cleanup
+- you are preparing imported data for amend workflows and want more predictable matches
+
+The trim settings apply to both file import and clipboard import.

docs-src/docs/020-editing-data/040-exporting-data.md

@@ -15,6 +15,24 @@ When a tab has been selected the download button will change to match the format
 
 Pressing the download button will start a conversion of the data in the grid to the specific format.
 
+### File transport settings
+
+Downloads also support file-only transport settings:
+
+- line endings: `LF` or `Windows (CR/LF)`
+- optional UTF-8 `BOM`
+
+These settings are useful when:
+
+- a Windows tool expects `CR/LF`
+- a spreadsheet or editor works better with BOM-prefixed UTF-8 files
+- you want the downloaded file to match the target toolchain without changing the on-screen preview text
+
+Example:
+
+- preview text can stay normal `LF` text in the browser
+- downloaded `.csv` can use `CR/LF` plus `Include BOM`
+
 ## Exporting to Clipboard
 
 To export to clipboard either: