@pixerate/editor 0.223.2 → 0.223.4

package/skills/pixerate-diagram-process-flow/evals/tidy-decision.json

@@ -0,0 +1,76 @@
+{
+	"prompt": "The decision in this flowchart is hard to read: the condition and the outcomes are crammed into the node. Tidy it up.",
+	"fixture": {
+		"editor": "diagram",
+		"setup": [
+			{
+				"tool": "load_diagram_mermaid",
+				"args": {
+					"source": "flowchart LR\n  check{Has the payment been received? If yes ship, otherwise remind} --> ship[Ship order]\n  check --> remind[Send reminder]"
+				}
+			}
+		]
+	},
+	"checks": [
+		{
+			"why": "a short question in the decision (at most six words)",
+			"tool": "get_diagram",
+			"expect": {
+				"nodes": {
+					"$some": {
+						"id": "check",
+						"shape": "diam",
+						"label": {
+							"$expr": "v.trim().split(/\\s+/).length <= 6 && /\\?$/.test(v.trim())"
+						}
+					}
+				}
+			}
+		},
+		{
+			"why": "the outcomes are on the edges",
+			"tool": "get_diagram",
+			"expect": {
+				"edges": {
+					"$every": {
+						"label": {
+							"$match": [
+								"^(yes|no|paid|unpaid|received|not received)$",
+								"i"
+							]
+						}
+					}
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "rename_diagram_node",
+			"args": {
+				"id": "check",
+				"label": "Payment received?"
+			}
+		},
+		{
+			"tool": "set_diagram_edge_label",
+			"args": {
+				"id": {
+					"$read": "get_diagram",
+					"path": "edges.0.id"
+				},
+				"label": "yes"
+			}
+		},
+		{
+			"tool": "set_diagram_edge_label",
+			"args": {
+				"id": {
+					"$read": "get_diagram",
+					"path": "edges.1.id"
+				},
+				"label": "no"
+			}
+		}
+	]
+}

package/skills/pixerate-image-photo-correction/evals/neutralise-cast.json

@@ -12,9 +12,9 @@
 	},
 	"checks": [
 		{ "why": "the grey card is neutral (cast within ±4 levels)", "tool": "measure_region", "args": { "x": 12, "y": 52, "width": 16, "height": 16 }, "expect": { "cast": { "redBlue": { "$min": -4, "$max": 4 }, "greenMagenta": { "$min": -4, "$max": 4 } } } },
-		{ "why": "the card is a mid grey, not crushed or blown", "tool": "measure_region", "args": { "x": 12, "y": 52, "width": 16, "height": 16 }, "expect": { "stats": { "luminance": { "mean": { "$min": 90, "$max": 170 } } } } },
+		{ "why": "the card stays a mid grey, not crushed or blown (the task asks for neither brighter nor darker)", "tool": "measure_region", "args": { "x": 12, "y": 52, "width": 16, "height": 16 }, "expect": { "stats": { "luminance": { "mean": { "$min": 60, "$max": 200 } } } } },
 		{ "why": "no channel clips anywhere", "tool": "measure_region", "expect": { "clipping": { "highlightsPercent": { "red": { "$max": 0.5 }, "green": { "$max": 0.5 }, "blue": { "$max": 0.5 } }, "shadowsPercent": { "red": { "$max": 0.5 }, "green": { "$max": 0.5 }, "blue": { "$max": 0.5 } } } } },
-		{ "why": "the correction is a layer, not baked into the photo", "tool": "list_layers", "expect": { "layers": { "$some": { "type": "adjustment" } } } }
+		{ "why": "the correction stays adjustable: an adjustment layer or the base white balance (the develop filter), not baked into the photo", "tool": "list_layers", "expect": { "$expr": "v.layers.some((l) => l.type === 'adjustment' || (l.filters || []).some((f) => f.kind === 'develop' && (f.temperature || f.tint)))" } }
 	],
 	"solution": [
 		{ "tool": "measure_region", "args": { "x": 12, "y": 52, "width": 16, "height": 16 } },

package/skills/pixerate-image-product-photo/evals/grounding-shadow.json

@@ -8,7 +8,7 @@
 		"shapes": [{ "shape": "rect", "x": 40, "y": 25, "width": 40, "height": 40, "color": [30, 90, 160] }]
 	},
 	"checks": [
-		{ "why": "the product is on its own layer, cut to its shape", "tool": "list_layers", "expect": { "layers": { "$some": { "type": "pixel", "bounds": { "x": { "$min": 39, "$max": 41 }, "y": { "$min": 24, "$max": 26 }, "width": { "$min": 39, "$max": 42 }, "height": { "$min": 39, "$max": 42 } } } } } },
+		{ "why": "the product is on its own layer, cut to its shape: by its pixels, or by its mask (masked, not erased)", "tool": "list_layers", "expect": { "layers": { "$some": { "type": "pixel", "$in": [{ "bounds": { "x": { "$min": 39, "$max": 41 }, "y": { "$min": 24, "$max": 26 }, "width": { "$min": 39, "$max": 42 }, "height": { "$min": 39, "$max": 42 } } }, { "mask": { "paintedBounds": { "x": { "$min": 39, "$max": 41 }, "y": { "$min": 24, "$max": 26 }, "width": { "$min": 39, "$max": 42 }, "height": { "$min": 39, "$max": 42 } } } }] } } } },
 		{ "why": "a live drop shadow on that layer", "tool": "list_layers", "expect": { "layers": { "$some": { "effects": { "$expr": "v && JSON.stringify(v).includes('drop-shadow')" } } } } }
 	],
 	"solution": [

package/skills/pixerate-rich-text/SKILL.md

@@ -21,6 +21,14 @@ Errors, namespacing (`doc-1__find_text`) and `run_commands` batching are covered
 `pixerate-agent-tools` skill. Chart type, axis and colour choices are covered by
 `pixerate-chart`; the same spec fields apply to charts in a document.
 
+## Workflow skills
+
+For these jobs, load the workflow skill too: it has the method, the checks between steps and
+the pitfalls, and uses the tools below.
+
+- `pixerate-rich-text-report`: a title and heading hierarchy, lists, tables, charts and a consistency pass.
+- `pixerate-rich-text-revise`: proofreading, renaming terms with exceptions, tightening, minimal edits.
+
 ## Working method
 
 1. **Read.** `get_text` (`format: "markdown"` shows headings, lists and tables compactly;

package/skills/pixerate-rich-text-report/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: pixerate-rich-text-report
+description: The report and structured document workflow in the Pixerate rich text editor - outlining before writing, one title and a heading hierarchy, consistent heading case, short paragraphs, lists for steps and items, tables for comparisons, charts in the document, and a final read-through for structure and consistency. Use when asked to write, structure, format, outline or tidy a report, memo, proposal, brief, article, documentation page or meeting notes, add headings, lists or a table, or make a document consistent, or when get_text, set_block_type, edit_table or insert_chart are available. Load with pixerate-rich-text, which lists every tool.
+metadata:
+  kind: workflow
+  reference: pixerate-rich-text
+---
+
+# Structuring a report
+
+A report is read by skimming first: the title, the headings and the first lines decide whether
+anyone reads the rest. So the structure carries the message: one title, sections with headings
+one level below, steps and items as lists, comparisons as tables, figures as charts. Get the
+structure right, then the words, then check consistency.
+
+This skill is the method. `pixerate-rich-text` has the full tool reference; positions come from
+`get_text` with `blocks: true` or from `find_text`, never from counting characters.
+
+## Goal and quality bar
+
+- One `heading` level 1 for the title; sections at level 2, subsections at level 3; no skipped
+  levels.
+- Headings consistent in case (sentence case unless the house style says otherwise) and short.
+- Steps as an ordered list, items as a bulleted list; comparisons with more than two attributes
+  as a table with a header row; numbers that show a trend as a chart.
+- Short paragraphs, each with one point; the summary first.
+- Nothing the author wrote is lost unless they asked for it to go.
+
+## Inputs to confirm
+
+- **Purpose and reader:** what decision or knowledge the document serves.
+- **Sections** the user expects, or a template.
+- **House style:** heading case, numbering, how dates and numbers are written.
+
+## Working method
+
+1. **Read.** `get_text` with `blocks: true`: every block's `type`, `from`, `to` and `text`.
+   **Check:** you can name the title, the sections and the body of each.
+2. **Outline.** Decide the heading hierarchy and which runs of paragraphs are really lists or
+   tables before changing anything.
+3. **Set the structure** with `set_block_type` on each block's range: `heading` with `level`,
+   `"bullet_list"`, `"ordered_list"`. Work from the blocks you read; positions shift when block types
+   change, so re-read (`get_text` `blocks`) after changes that add or remove wrapping.
+   **Check:** `get_text` `format: "html"` shows `<h1>`, `<h2>`, `<ul>` where you meant.
+4. **Tables.** `edit_table` `insertTable` (`at` the end of the paragraph it follows, `rows`,
+   `cols`, `withHeaderRow`), then `insert_text` into each cell from the last cell to the first so
+   earlier positions stay valid (cell positions from `get_text` `blocks`).
+   **Check:** the HTML has the header cells and rows in order.
+5. **Charts** for figures: `insert_chart` with the data; edit with `update_chart_in_document`.
+6. **Consistency pass.** Heading case, terms, numbers and dates written one way:
+   `find_text` to find variants, `replace_text` to fix them (see
+   `pixerate-rich-text-revise`).
+   **Check:** `find_text` for the old variants returns no matches.
+7. **Read it through** once as the reader would (`get_text`), and report what changed.
+
+## Decision table
+
+| Content | Block |
+| --- | --- |
+| Document title | `heading` level 1 (once) |
+| Section, subsection | `heading` level 2, 3 |
+| Steps in order | `"ordered_list"` |
+| Items, options, takeaways | `"bullet_list"` |
+| Things compared on several attributes | A table with a header row |
+| A trend or comparison of numbers | `insert_chart` |
+| A quotation | `blockquote` |
+| Code or commands | `"code_block"` |
+
+## Recipes
+
+**Structure a draft.** `get_text` `blocks` → `set_block_type` title `heading` level 1 → each
+section line `heading` level 2 → each run of item lines `"bullet_list"` (one call over the run's
+range).
+
+**A two-column table.** `edit_table` `{ operation: "insertTable", at, rows: 3, cols: 2,
+withHeaderRow: true }` → `get_text` `blocks` for the empty cells → `insert_text` into each cell,
+last first.
+
+## Pitfalls
+
+- **Positions from the plain text** are wrong: block boundaries count. Use `blocks` or
+  `find_text`.
+- **Stale positions** after a change that adds a list or table; re-read before the next edit.
+- **Several level-1 headings** flatten the outline; one title only.
+- **Bold paragraphs as headings** do not appear in the outline or navigation; use headings.
+- **Tables for prose** or one-column tables; use paragraphs or lists.
+- **Rewriting the author's words** while restructuring; change structure, not content, unless
+  asked.
+
+## Tools used
+
+- `get_text`, `find_text`: read the document, its blocks and positions
+- `set_block_type`, `set_text_align`: headings, lists and alignment
+- `format_text`: emphasis and links
+- `edit_table`: insert and shape tables
+- `insert_text`, `replace_range`, `replace_text`: fill cells, write and fix text
+- `insert_chart`, `update_chart_in_document`, `list_document_charts`: charts in the document
+- `undo_rich_text`: take back a step

package/skills/pixerate-rich-text-report/evals/heading-case.json

@@ -0,0 +1,48 @@
+{
+	"prompt": "The section headings are inconsistent. Make them all sentence case (first word capitalised, the rest lower case unless they are names).",
+	"fixture": {
+		"editor": "rich-text",
+		"html": "<h1>Annual review</h1><h2>RESULTS AND Findings</h2><p>Revenue grew.</p><h2>Next Steps For Acme</h2><p>Plan the launch.</p>"
+	},
+	"checks": [
+		{
+			"why": "headings in sentence case, keeping the name Acme",
+			"tool": "get_text",
+			"args": {
+				"format": "html"
+			},
+			"expect": {
+				"content": {
+					"$expr": "/<h2[^>]*>Results and findings<\\/h2>/.test(v) && /<h2[^>]*>Next steps for Acme<\\/h2>/.test(v)"
+				}
+			}
+		},
+		{
+			"why": "the body and title are unchanged",
+			"tool": "get_text",
+			"expect": {
+				"content": {
+					"$expr": "v.startsWith('Annual review') && v.includes('Revenue grew.') && v.includes('Plan the launch.')"
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "replace_text",
+			"args": {
+				"find": "RESULTS AND Findings",
+				"replace": "Results and findings",
+				"matchCase": true
+			}
+		},
+		{
+			"tool": "replace_text",
+			"args": {
+				"find": "Next Steps For Acme",
+				"replace": "Next steps for Acme",
+				"matchCase": true
+			}
+		}
+	]
+}

package/skills/pixerate-rich-text-report/evals/results-table.json

@@ -0,0 +1,93 @@
+{
+	"prompt": "Under 'Sales by region:', add a table with a header row (Region, Sales) and two rows: North 120 and South 95.",
+	"fixture": {
+		"editor": "rich-text",
+		"html": "<h2>Results</h2><p>Sales by region:</p><h2>Next steps</h2>"
+	},
+	"checks": [
+		{
+			"why": "a table with a header row and the two regions",
+			"tool": "get_text",
+			"args": {
+				"format": "html"
+			},
+			"expect": {
+				"content": {
+					"$match": "<table[^>]*>.*<th[^>]*><p>Region</p></th><th[^>]*><p>Sales</p></th>.*<td[^>]*><p>North</p></td><td[^>]*><p>120</p></td>.*<td[^>]*><p>South</p></td><td[^>]*><p>95</p></td>.*</table>"
+				}
+			}
+		},
+		{
+			"why": "placed after 'Sales by region:' and before the next section",
+			"tool": "get_text",
+			"args": {
+				"format": "html"
+			},
+			"expect": {
+				"content": {
+					"$match": "Sales by region:</p><table.*</table><h2[^>]*>Next steps"
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "get_text",
+			"args": {
+				"blocks": true
+			}
+		},
+		{
+			"tool": "edit_table",
+			"args": {
+				"operation": "insertTable",
+				"at": 26,
+				"rows": 3,
+				"cols": 2,
+				"withHeaderRow": true
+			}
+		},
+		{
+			"tool": "insert_text",
+			"args": {
+				"text": "95",
+				"at": 55
+			}
+		},
+		{
+			"tool": "insert_text",
+			"args": {
+				"text": "South",
+				"at": 51
+			}
+		},
+		{
+			"tool": "insert_text",
+			"args": {
+				"text": "120",
+				"at": 45
+			}
+		},
+		{
+			"tool": "insert_text",
+			"args": {
+				"text": "North",
+				"at": 41
+			}
+		},
+		{
+			"tool": "insert_text",
+			"args": {
+				"text": "Sales",
+				"at": 35
+			}
+		},
+		{
+			"tool": "insert_text",
+			"args": {
+				"text": "Region",
+				"at": 31
+			}
+		}
+	]
+}

package/skills/pixerate-rich-text-report/evals/structure.json

@@ -0,0 +1,106 @@
+{
+	"prompt": "Turn this into a properly structured report: the first line is the title, 'Summary', 'Results' and 'Next steps' are section headings, and the next steps should be a bulleted list.",
+	"fixture": {
+		"editor": "rich-text",
+		"html": "<p>Quarterly report</p><p>Summary</p><p>Sales grew in every region.</p><p>Results</p><p>North led with 120 orders.</p><p>Next steps</p><p>Hire two engineers</p><p>Launch in May</p>"
+	},
+	"checks": [
+		{
+			"why": "the title is the top heading",
+			"tool": "get_text",
+			"args": {
+				"format": "html"
+			},
+			"expect": {
+				"content": {
+					"$match": "^<h1[^>]*>Quarterly report</h1>"
+				}
+			}
+		},
+		{
+			"why": "the three sections are headings one level below",
+			"tool": "get_text",
+			"args": {
+				"format": "html"
+			},
+			"expect": {
+				"content": {
+					"$expr": "['Summary', 'Results', 'Next steps'].every((t) => new RegExp('<h2[^>]*>' + t + '</h2>').test(v))"
+				}
+			}
+		},
+		{
+			"why": "the next steps are a bulleted list",
+			"tool": "get_text",
+			"args": {
+				"format": "html"
+			},
+			"expect": {
+				"content": {
+					"$match": "<ul[^>]*><li[^>]*><p>Hire two engineers</p></li><li[^>]*><p>Launch in May</p></li></ul>"
+				}
+			}
+		},
+		{
+			"why": "the body text is kept",
+			"tool": "get_text",
+			"expect": {
+				"content": {
+					"$expr": "v.includes('Sales grew in every region.') && v.includes('North led with 120 orders.')"
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "get_text",
+			"args": {
+				"blocks": true
+			}
+		},
+		{
+			"tool": "set_block_type",
+			"args": {
+				"from": 1,
+				"to": 17,
+				"type": "heading",
+				"level": 1
+			}
+		},
+		{
+			"tool": "set_block_type",
+			"args": {
+				"from": 19,
+				"to": 26,
+				"type": "heading",
+				"level": 2
+			}
+		},
+		{
+			"tool": "set_block_type",
+			"args": {
+				"from": 56,
+				"to": 63,
+				"type": "heading",
+				"level": 2
+			}
+		},
+		{
+			"tool": "set_block_type",
+			"args": {
+				"from": 93,
+				"to": 103,
+				"type": "heading",
+				"level": 2
+			}
+		},
+		{
+			"tool": "set_block_type",
+			"args": {
+				"from": 105,
+				"to": 134,
+				"type": "bullet_list"
+			}
+		}
+	]
+}

package/skills/pixerate-rich-text-revise/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: pixerate-rich-text-revise
+description: The revision workflow in the Pixerate rich text editor - proofreading for spelling and grammar, renaming a term consistently while leaving quotations and names alone, tightening wordy passages, unifying how numbers, dates and terms are written, and making minimal, targeted edits that keep the author's formatting and voice, with a check that nothing else changed. Use when asked to proofread, copy-edit, revise, tighten, shorten, fix typos, rename or replace a term throughout, make wording consistent or polish a document, or when find_text, replace_text and replace_range are available. Load with pixerate-rich-text, which lists every tool.
+metadata:
+  kind: workflow
+  reference: pixerate-rich-text
+---
+
+# Revising a document
+
+Revision changes as little as possible to make the document right: each fix is a targeted
+replacement of the words that are wrong, so formatting, links and the author's voice survive.
+Find before replacing, decide which matches should change (a quotation, a name or a published
+title often should not), and check afterwards that only what you meant changed.
+
+This skill is the method. `pixerate-rich-text` has the full tool reference.
+
+## Goal and quality bar
+
+- Every error the user asked about is fixed (`find_text` for it returns no matches).
+- Only the intended text changed: the rest of the document reads exactly as before.
+- Replacements respect case (`Teh` becomes `The`), whole words (`teh` but not `tehran`) and
+  exceptions (quotations, names, titles of published works).
+- Tightened passages keep their point and the author's voice; nothing is added that was not
+  there.
+- Formatting (bold, links, headings, lists) is untouched by text fixes.
+
+## Inputs to confirm
+
+- **Scope:** spelling only, grammar and style, or a rewrite of named passages.
+- **Exceptions:** text that must stay as written (quotes, legal text, product names, titles).
+- **House style:** spelling variant (UK or US), how numbers and dates are written.
+
+## Working method
+
+1. **Read.** `get_text` (with `blocks: true` for positions).
+   **Check:** you have a list of fixes with the exact wrong text and the right text.
+2. **Find before replacing.** `find_text` for each term (`wholeWord`, `matchCase`, or `regex`
+   for families of errors); read the matches in context and decide which change.
+   **Check:** the match count is what you expect; note the occurrences to leave alone.
+3. **Replace in one call per fix.** `replace_text` with `find`, `replace`, `wholeWord: true`;
+   `matchCase: true` with one call per capitalisation (`teh` and `Teh`); `occurrence` for only
+   some matches, working from the last occurrence to the first so the numbering holds.
+   **Check:** `find_text` for the wrong text returns no matches (except the exceptions).
+4. **Rewrite a passage** with `replace_range` over exactly its range (`from` / `to` of the block
+   or a `find_text` match), keeping the surrounding text.
+   **Check:** `get_text` `blocks`: the other blocks' text is unchanged.
+5. **Consistency.** Terms, numbers and dates one way: `find_text` with a `regex` for the
+   variants, then `replace_text`.
+6. **Report** the fixes made, the matches you left and why.
+
+## Decision table
+
+| Fix | Tool and settings |
+| --- | --- |
+| A misspelling everywhere | `replace_text`, `wholeWord: true`, one call per capitalisation with `matchCase` |
+| Rename a term, with exceptions | `find_text`, then `replace_text` with `occurrence` per change, last first |
+| A family of variants (e-mail, email, E-mail) | `find_text` / `replace_text` with `regex: true` |
+| Rewrite a sentence or paragraph | `replace_range` over its exact range |
+| Insert a missing word | `insert_text` at the position from `find_text` |
+| Formatting only | `format_text` on the range; leave the words |
+
+## Recipes
+
+**Typos.** `replace_text` `{ find: "recieve", replace: "receive", wholeWord: true }`; for a word
+that starts sentences, `{ find: "Teh", replace: "The", matchCase: true, wholeWord: true }` and
+the same in lower case.
+
+**Rename except a quotation.** `find_text` "Acme Cloud" lists three matches; the second is in a
+quoted title: `replace_text` with `occurrence: 3`, then `occurrence: 1`.
+
+**Tighten the intro.** `get_text` `blocks` → `replace_range` `{ from: blocks[0].from, to:
+blocks[0].to, text }` with one sentence.
+
+## Pitfalls
+
+- **Case-insensitive replace** turns `Teh` into `the` at the start of a sentence; match case.
+- **Partial words**: without `wholeWord`, fixing `teh` breaks words containing it.
+- **Changing quotations, names or published titles** that must stay as written.
+- **`occurrence` after an earlier change** counts the remaining matches; replace from the last
+  to the first.
+- **Rewriting whole paragraphs** to fix one word loses formatting and links; replace only the
+  words.
+- **Adding content** while tightening; keep the author's point and facts.
+
+## Tools used
+
+- `get_text`, `find_text`: read the text, blocks, positions and matches
+- `replace_text`: targeted replacements, with case, whole-word, regex and occurrence
+- `replace_range`, `insert_text`: rewrite or insert at exact positions
+- `format_text`: formatting fixes without touching words
+- `undo_rich_text`: take back a step

package/skills/pixerate-rich-text-revise/evals/fix-typos.json

@@ -0,0 +1,57 @@
+{
+	"prompt": "Fix the spelling mistakes in this document without changing anything else.",
+	"fixture": {
+		"editor": "rich-text",
+		"html": "<p>We will recieve the order tomorrow. Teh team is ready.</p><p>Please recieve the parcel and check teh contents.</p>"
+	},
+	"checks": [
+		{
+			"why": "no misspellings left",
+			"tool": "find_text",
+			"args": {
+				"query": "\\b(recieve|teh)\\b",
+				"regex": true
+			},
+			"expect": {
+				"matches": {
+					"$length": 0
+				}
+			}
+		},
+		{
+			"why": "the text is otherwise unchanged, capitals kept",
+			"tool": "get_text",
+			"expect": {
+				"content": "We will receive the order tomorrow. The team is ready.\nPlease receive the parcel and check the contents."
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "replace_text",
+			"args": {
+				"find": "recieve",
+				"replace": "receive",
+				"wholeWord": true
+			}
+		},
+		{
+			"tool": "replace_text",
+			"args": {
+				"find": "Teh",
+				"replace": "The",
+				"matchCase": true,
+				"wholeWord": true
+			}
+		},
+		{
+			"tool": "replace_text",
+			"args": {
+				"find": "teh",
+				"replace": "the",
+				"matchCase": true,
+				"wholeWord": true
+			}
+		}
+	]
+}

package/skills/pixerate-rich-text-revise/evals/rename-term.json

@@ -0,0 +1,51 @@
+{
+	"prompt": "We've renamed the product from 'Acme Cloud' to 'Acme Platform'. Update the document, but leave the title of the 2019 press release (in quotes) as it was published.",
+	"fixture": {
+		"editor": "rich-text",
+		"html": "<p>Acme Cloud now supports teams.</p><p>Our 2019 press release, \u201cIntroducing Acme Cloud\u201d, launched the product.</p><p>Try Acme Cloud today.</p>"
+	},
+	"checks": [
+		{
+			"why": "renamed in the running text",
+			"tool": "get_text",
+			"expect": {
+				"content": {
+					"$expr": "v.startsWith('Acme Platform now supports teams.') && v.endsWith('Try Acme Platform today.')"
+				}
+			}
+		},
+		{
+			"why": "the published title is unchanged",
+			"tool": "get_text",
+			"expect": {
+				"content": {
+					"$match": "\u201cIntroducing Acme Cloud\u201d"
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "find_text",
+			"args": {
+				"query": "Acme Cloud"
+			}
+		},
+		{
+			"tool": "replace_text",
+			"args": {
+				"find": "Acme Cloud",
+				"replace": "Acme Platform",
+				"occurrence": 3
+			}
+		},
+		{
+			"tool": "replace_text",
+			"args": {
+				"find": "Acme Cloud",
+				"replace": "Acme Platform",
+				"occurrence": 1
+			}
+		}
+	]
+}