podlite-verifylisted

# Podlite Verify AI-generated markup drifts: unbalanced blocks, broken nesting, attribute values that swallow the next token. Podlite is structured, so most of these are **mechanically checkable**. Verify before delivering. Run two layers: (1) **self-check** the output against the rules below (always available, no tooling), then (2) **machine-validate** with the parser/linter when it is available. - **Companion skill:** `podlite-markup` (how to write it) - **Specification:** https://podlite.org/specification ## When to verify - Immediately after generating or editing any `.podlite` / `.pod6` content, before presenting it - When the user asks to validate, lint, check, or fix Podlite - When a renderer or parser reports an error - Before committing Podlite to a repository or knowledge base ## Layer 1: self-check rules (no tooling required) Read the produced markup and confirm each invariant. These are the errors LLMs introduce most often. | # | Check | Wrong | Right | |---|-------|-------|-------| | 1 | **Every `=begin X` has a matching `=end X`** with the same typename | `=begin code … =end pod` | `=begin code … =end code` | | 2 | **Balanced block nesting**: inner blocks close before outer | `=begin pod =begin code =end pod` | `=begin pod =begin code =end code =end pod` | | 3 | **List levels are sequential**: no skipping | `=item1` → `=item3` | `=item1` → `=item2` → `=item3` | | 4 | **Attribute values with spaces are quoted** | `:caption<Q1 sales>` | `:caption('Q1 sales