@bendyline/gilde 0.1.37 → 0.1.39

package/data/craftbook-templates/in/invitation-design/versions/1.0.2/craftbook.json

@@ -0,0 +1,140 @@
+{
+  "id": "invitation-design",
+  "name": "Design the Invitations",
+  "description": "Produce the invitation the day deserves and get the facts beyond doubt: the date, time, venue, and RSVP instructions checked letter-for-letter against the event record — because a beautiful card with the wrong date is the classic disaster. Locks the fact checklist and the look brief FIRST, then designs the print-ready invitation, then proofs every fact against the record before anything reaches a printer. Use for party invitations, designing the invites, birthday and anniversary invitations, and 'make the invitation printable'.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Lock the facts (ceremoniemeester) — fact checklist from the event record, look brief → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Design the invitation (designer) — print-ready invitation with every fact copied from the record → gated on `invitations/invitation.html` (html-page)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "design the invitations",
+    "make the party invites",
+    "invitation for the party",
+    "printable invitation",
+    "invites for the celebration"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Lock the facts",
+      "description": "fact checklist from the event record, look brief",
+      "prompt": "Lock the facts before any design. Step 1: read event.json from the workspace — the occasion, date, time, venue, host, and RSVP instructions — and guests.json for who the invitation must speak to. Step 2: confirm the look brief with the owner — the mood of the day, colors or motifs that matter, and anything the honoree would hate. Step 3: write the fact checklist: date, time, venue, and RSVP line exactly as the event record has them, character for character — the invitation may be creative about everything except these. Step 4: write an acceptance-criteria checklist ('every fact matches event.json exactly', 'the RSVP instruction is present and actionable — who to tell, how, by when', 'the file is print-ready — @page setup, honest margins, one sheet', 'the look fits the brief'). Call write_task_note with the occasion + the fact list + checklist and write {{workPath}}/scope.md.\n\nThe deliverable `{{workPath}}/scope.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "ceremoniemeester",
+      "advanceWhen": {
+        "file": "{{workPath}}/scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "design"
+    },
+    {
+      "id": "design",
+      "name": "Design the invitation",
+      "description": "print-ready invitation with every fact copied from the record",
+      "prompt": "Design the invitation as one print-ready HTML file at invitations/invitation.html. Step 1: lay out the card — the occasion first, then the facts from the locked checklist, copied from event.json, never retyped from memory. Step 2: the RSVP line — who to tell, how, and by when, exactly as the record has it. Step 3: art direction per the brief — set type, color, and ornament with intent; where the look wants imagery, use the project's image capabilities or tasteful drawn ornament. Step 4: make it print-ready — an @page rule with size and margins, print styles, everything on one sheet. Step 5: proof the facts one final time against event.json before completing. Call write_task_note with the file path and the four facts as printed.",
+      "suggestedRole": "designer",
+      "advanceWhen": {
+        "file": "invitations/invitation.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "invitations/invitation.html",
+            "bytes": 800
+          },
+          {
+            "kind": "htmlLint",
+            "file": "invitations/invitation.html"
+          },
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "invitations/invitation.html"
+          },
+          {
+            "kind": "contains",
+            "file": "invitations/invitation.html",
+            "pattern": "RSVP",
+            "flags": "i",
+            "label": "RSVP line"
+          },
+          {
+            "kind": "contains",
+            "file": "invitations/invitation.html",
+            "pattern": "@page|@media\\s+print",
+            "flags": "i",
+            "label": "print CSS"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "invitations/invitation.html"
+            }
+          }
+        ],
+        "onReject": "design",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Open invitations/invitation.html and event.json side by side and verify every criterion from {{workPath}}/scope.md: the date, the time, the venue, and the RSVP instruction each match the event record exactly — read them character by character, this is the check the whole book exists for — the RSVP line is actionable, the file is print-ready with proper page setup on one sheet, and the look honors the brief. Write PASS/FAIL per fact and per criterion; on any mismatch, quote both versions and loop back to design.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"design\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "invitations/invitation.html"
+        }
+      ],
+      "next": "design"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true
+    }
+  ],
+  "version": "1.0.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/in/invitation-design/versions/1.0.2/test.json

@@ -0,0 +1,124 @@
+{
+  "schemaVersion": 1,
+  "title": "Design the Invitations — facts beyond doubt",
+  "objective": "Measure whether the invitation-design craftbook produces a print-ready invitation whose date, time, venue, and RSVP line match the seeded event record exactly — fact conservation is the class bar.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "can you design the invitatons for sofias party? event details are all in the project — something warm, printable",
+  "setup": {
+    "projectName": "Sofia's Tenth Birthday",
+    "about": "Event planner project for Sofia's 10th birthday. The event record is workspace/event.json and the guest list is workspace/guests.json; the invitation goes under workspace/invitations.",
+    "missionObjectives": "The invitation's facts must match the event record exactly — a beautiful card with the wrong date is the classic disaster. No live services, no real credentials.",
+    "files": [
+      {
+        "path": "event.json",
+        "content": "{\n  \"occasion\": \"Sofia's 10th birthday\",\n  \"honoree\": \"Sofia Alvarez\",\n  \"date\": \"Saturday, August 15, 2026\",\n  \"startTime\": \"2:00 PM\",\n  \"endTime\": \"5:00 PM\",\n  \"venue\": \"Willow Bend Park, Pavilion 3\",\n  \"venueAddress\": \"200 Riverbank Rd, Halstead\",\n  \"host\": \"the Alvarez family\",\n  \"theme\": \"backyard science fair — bright colors, rockets, magnifying glasses\",\n  \"rsvp\": {\n    \"to\": \"Marta Alvarez\",\n    \"by\": \"August 8, 2026\",\n    \"phone\": \"555-0142\"\n  }\n}\n"
+      },
+      {
+        "path": "guests.json",
+        "content": "{\n  \"guests\": [\n    { \"name\": \"Nils Bergman\", \"age\": 10 },\n    { \"name\": \"Ada Okonkwo\", \"age\": 9 },\n    { \"name\": \"Theo Reyes\", \"age\": 10 },\n    { \"name\": \"June Castellano\", \"age\": 11 },\n    { \"name\": \"Omar Haddad\", \"age\": 10 }\n  ],\n  \"note\": \"mostly classmates — invitations go home in backpacks, so they must print well in one sheet\"\n}\n"
+      }
+    ],
+    "worker": {
+      "name": "Isa",
+      "role": "Designer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "invitations/invitation.html is a print-ready, one-sheet invitation whose date, time, venue, and RSVP instructions are conserved verbatim from event.json.",
+    "deliverables": [
+      {
+        "path": "invitations/invitation.html",
+        "kind": "html-page",
+        "minBytes": 1500,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "invitations/invitation.html"
+          },
+          {
+            "kind": "contains",
+            "file": "invitations/invitation.html",
+            "pattern": "@page|@media\\s+print",
+            "flags": "i",
+            "label": "print CSS"
+          },
+          {
+            "kind": "contains",
+            "file": "invitations/invitation.html",
+            "pattern": "RSVP",
+            "flags": "i",
+            "label": "RSVP line present"
+          },
+          {
+            "kind": "valuesSubsetOf",
+            "file": "invitations/invitation.html",
+            "sourceFiles": [
+              "event.json"
+            ],
+            "pattern": "((?:January|February|March|April|May|June|July|August|September|October|November|December)\\s+\\d{1,2},?\\s+\\d{4})",
+            "minMatches": 1,
+            "label": "every printed date exists in the event record"
+          },
+          {
+            "kind": "valuesSubsetOf",
+            "file": "invitations/invitation.html",
+            "sourceFiles": [
+              "event.json"
+            ],
+            "pattern": "(\\d{1,2}:\\d{2}\\s*[AP]M)",
+            "minMatches": 1,
+            "label": "every printed time exists in the event record"
+          },
+          {
+            "kind": "contains",
+            "file": "invitations/invitation.html",
+            "pattern": "Willow Bend Park",
+            "label": "venue named"
+          },
+          {
+            "kind": "contains",
+            "file": "invitations/invitation.html",
+            "pattern": "Pavilion 3",
+            "label": "venue detail conserved"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "invitations/invitation.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "correctness",
+        "description": "Date, time, venue, and RSVP instructions match event.json exactly — no retyped-from-memory drift."
+      },
+      {
+        "name": "elegance",
+        "description": "Type, color, and ornament are set with intent and fit a tenth birthday's science-fair theme."
+      },
+      {
+        "name": "print readiness",
+        "description": "Page setup, margins, and one-sheet layout would survive a home printer."
+      },
+      {
+        "name": "tone fit",
+        "description": "Warm and festive for classmates and parents alike — not corporate, not cluttered."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "fact conservation",
+    "print-ready output",
+    "theme fit"
+  ]
+}

package/data/craftbook-templates/in/invoice-generator/versions/1.0.2/craftbook.json

@@ -0,0 +1,122 @@
+{
+  "id": "invoice-generator",
+  "name": "Invoice Generator",
+  "description": "Generate a clean, professional, print-ready invoice from billing details — sender/recipient, line items with quantity and rate, subtotal, tax, total, invoice number, dates, and payment instructions. Scopes the required fields and the tax/total math FIRST (a wrong total is the one unforgivable invoice bug), then builds a polished single-file HTML invoice with an itemized table and correctly computed totals. Use for freelancer/contractor billing, one-off invoices, and invoice templates.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Scope the invoice (planner) — required fields, line items, and the tax/total math rules → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Build the invoice (developer) — render invoice.html with an itemized table and correct totals → gated on `invoice.html` (html-page)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "generate an invoice",
+    "make an invoice",
+    "create a bill",
+    "freelance invoice",
+    "invoice template",
+    "billing document"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the invoice",
+      "description": "required fields, line items, and the tax/total math rules",
+      "prompt": "Nail down the data and the math before formatting. Step 1: list the required fields — sender (name, address, contact), recipient (bill-to), invoice number, issue date, due date, and payment terms. Step 2: enumerate the line items, each with description, quantity, unit rate, and line amount (quantity x rate). Step 3: define the money math EXACTLY: subtotal = sum of line amounts; tax = subtotal x tax rate (or none); discount if any; total = subtotal - discount + tax. State the currency and rounding (2 decimals). Step 4: capture payment instructions (bank/transfer/links) and any notes. Step 5: write an acceptance-criteria checklist ('all required header fields present', 'every line item has qty, rate, and qty x rate amount', 'subtotal equals the sum of line amounts', 'tax computed from the stated rate', 'total = subtotal - discount + tax and is arithmetically correct', 'currency + dates + invoice number shown', 'payment instructions present'). Write the field list + math rules + checklist via write_task_note AND to {{workPath}}/scope.md. No HTML yet.\n\nThe deliverable `{{workPath}}/scope.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "planner",
+      "advanceWhen": {
+        "file": "{{workPath}}/scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build the invoice",
+      "description": "render invoice.html with an itemized table and correct totals",
+      "prompt": "Build the invoice as a single self-contained invoice.html (inline CSS with print @page rules). Step 1: render a header with the sender block, a bill-to block, and an invoice-meta block (invoice number, issue date, due date, terms). Step 2: render the line items as a bordered table with columns Description | Qty | Rate | Amount, computing each Amount as qty x rate. Step 3: render a totals block beneath the table: Subtotal (sum of amounts), Discount (if any), Tax (subtotal x rate, with the rate shown), and a visually emphasized Total = subtotal - discount + tax. COMPUTE the arithmetic correctly and format all money to 2 decimals in the stated currency. Step 4: add a payment-instructions section and any notes, plus a clean, professional visual style that prints to one page. Step 5: double-check the totals add up before finishing. On a loop-back, fix ONLY the named gaps (most commonly an arithmetic error). Write the path + the computed total via write_task_note.",
+      "suggestedRole": "developer",
+      "advanceWhen": {
+        "file": "invoice.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "invoice.html",
+            "bytes": 800
+          },
+          {
+            "kind": "htmlLint",
+            "file": "invoice.html"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "invoice.html"
+            }
+          }
+        ],
+        "onReject": "build",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "QA the invoice against the locked criteria — and RE-DO THE MATH yourself. Step 1: open/render invoice.html. Step 2: independently recompute each line Amount (qty x rate), the Subtotal (sum of amounts), the Tax (subtotal x stated rate), and the Total (subtotal - discount + tax); compare to what the invoice shows — any mismatch is an automatic FAIL. Step 3: check EACH remaining criterion: all header fields present (sender, bill-to, invoice number, issue + due dates, terms), itemized table with qty/rate/amount columns, currency and 2-decimal formatting, payment instructions present, prints cleanly to one page. Step 4: write PASS/FAIL per criterion; on any arithmetic mismatch, state the correct figure and loop back to fix.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"build\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "invoice.html"
+        }
+      ],
+      "next": "build"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true
+    }
+  ],
+  "version": "1.0.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/in/invoice-generator/versions/1.0.2/test.json

@@ -0,0 +1,100 @@
+{
+  "schemaVersion": 1,
+  "title": "Invoice Generator smoke eval",
+  "objective": "Self-contained smoke eval for the Invoice Generator craftbook using the html-page generic harness.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "Can you biuld us a little page for this? The content notes are in source/page-content.md. Save it as index.html — one file, nothing fancy needed on our end.",
+  "setup": {
+    "projectName": "Invoice Generator Eval",
+    "about": "Self-contained eval project for invoice-generator. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/index.html.",
+    "missionObjectives": "Use the Invoice Generator craftbook/template, read the seeded local fixtures, and write index.html without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Invoice Generator Eval Brief\n\nClient: Boreal Desk, a home-office accessories company.\nAudience: operations leads who need an artifact they can use this week.\n\nFixed source facts for grounding:\n- The returns desk pilot covered 18 SKUs.\n- Median first response improved from 18 hours to 6 hours.\n- Preventable refund leakage fell from 14.2% to 8.9%.\n- The top unresolved complaint is status silence after photo submission.\n- Required next actions are automated status emails, barcode-exception training, and a weekly Finance exception export.\n\nUse these facts when the task asks for prose, analysis, copy, UI content, or test data. Do not use live web services, real credentials, or current outside data.\n\nCraftbook under test: invoice-generator - Invoice Generator.\n"
+      },
+      {
+        "path": "source/page-content.md",
+        "content": "# Boreal Desk Support Board\n\nBuild content around a support operations board. Required labels: Open issues, Status silence, Response time, Refund leakage, Next action. Required metric text: 18 hours to 6 hours and 14.2% to 8.9%.\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Developer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "index.html is a source-grounded self-contained HTML page/tool.",
+    "deliverables": [
+      {
+        "path": "index.html",
+        "kind": "html-page",
+        "minBytes": 3000,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "index.html"
+          },
+          {
+            "kind": "jsParses",
+            "file": "index.html"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "Boreal|Support Board|returns",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "18\\s*hours|6\\s*hours|14\\.2%|8\\.9%",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "button|input|filter|tab|card|section|nav",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "index.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "structure",
+        "description": "Layout and hierarchy fit the content; sections are scannable and coherent."
+      },
+      {
+        "name": "grounding",
+        "description": "Seeded source content is used faithfully — no invented facts or dropped requirements."
+      },
+      {
+        "name": "interactivity",
+        "description": "Controls and states the page claims to offer actually work."
+      },
+      {
+        "name": "polish",
+        "description": "Styling is intentional and responsive rather than unstyled or broken."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "self-contained UI",
+    "source grounding",
+    "responsive structure"
+  ]
+}