From 95a9ad45ba1a926a19803666277c2f24fbed670e Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Mon, 22 Jun 2026 08:37:22 +0000
Subject: [PATCH] feat: add schema coverage demo for max-turn-cache-misses

---
 .../schema-demo-max-turn-cache-misses.md      | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 schema-demos/schema-demo-max-turn-cache-misses.md

diff --git a/schema-demos/schema-demo-max-turn-cache-misses.md b/schema-demos/schema-demo-max-turn-cache-misses.md
new file mode 100644
index 00000000000..8043f84105e
--- /dev/null
+++ b/schema-demos/schema-demo-max-turn-cache-misses.md
@@ -0,0 +1,31 @@
+---
+description: Demonstrates the `max-turn-cache-misses` schema field
+on:
+  workflow_dispatch:
+permissions:
+  contents: read
+engine: codex
+max-turn-cache-misses: 5
+timeout-minutes: 5
+---
+
+# Schema Demo: `max-turn-cache-misses`
+
+This workflow was auto-generated to demonstrate usage of the
+`max-turn-cache-misses` field in the gh-aw frontmatter schema. It exists solely
+to achieve 100% schema feature coverage.
+
+## What `max-turn-cache-misses` Does
+
+Maximum number of consecutive AWF cache misses allowed before the API proxy
+blocks further requests.
+
+## Task
+
+Call `noop` -- this is a coverage-only demo workflow.
+
+**Important**: Always call the `noop` safe-output tool.
+
+```json
+{"noop": {"message": "Coverage demo for `max-turn-cache-misses` -- no action needed."}}
+```