@render-policy/a2ui 0.1.5 → 0.1.7

package/README.md

@@ -71,7 +71,9 @@ const markdown = createA2uiMarkdownRenderer({ guard }); // share the guard with
 ```
 
 This is the compatibility path, and it is weaker than a fragment: the HTML is serialized here and
-parsed again by the renderer. Where you render `Text` yourself, use `guard.renderText()`.
+parsed again by the renderer. Where you render `Text` yourself, use `guard.renderText()`, or the
+`Text` and `Image` components of [`@render-policy/react/a2ui`](../react#a2ui-text-and-image) and
+[`@render-policy/angular/a2ui`](../angular#a2ui-text-and-image), which are built on the guard.
 
 ## Proofs
 
@@ -81,5 +83,7 @@ carries Markdown images, raw HTML and links; a button calls `openUrl('javascript
 no request reaches a host outside the allowlist, the token assembled by `formatString` never leaves,
 and nothing opens. The same messages without the guard are the control: they make those requests.
 
-Not covered yet: a static scan of A2UI messages for literal hazards (planned as `mcp-app-lint`
-rules), and A2UI cases in the evil-Markdown corpus. A2UI v1.0 follows when that version is stable.
+For CI, [`mcp-app-lint --a2ui`](../mcp-app-lint#a2ui-rules) scans recorded A2UI message streams
+for the same hazards before anything renders. The evil-Markdown corpus has 24 A2UI cases
+([`corpus/evil-a2ui.json`](../../corpus/evil-a2ui.json)) that any A2UI renderer can run through a
+corpus adapter. A2UI v1.0 follows when that version is stable.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@render-policy/a2ui",
-  "version": "0.1.5",
+  "version": "0.1.7",
   "description": "Render-policy checks for A2UI (v0.9) surfaces: image, media, icon and openUrl values checked after data binding, and the catalog's Text contract (no HTML, images or links) enforced.",
   "license": "MIT",
   "type": "module",