Tell agent how to properly test reference doc updates

Author: st0012

AGENTS.md

@@ -268,6 +268,53 @@ Use Red, Green, Refactor approach:
 3. Check output in `_site/` directory
 4. Check coverage: `bundle exec rake coverage`
 
+### Modifying Markup Reference Documentation
+
+When editing markup reference documentation, such as `doc/markup_reference/markdown.md` and `doc/markup_reference/rdoc.rdoc`:
+
+1. **Always verify rendering** - After making changes, test that the content renders correctly using Ruby:
+
+   For Markdown files:
+
+   ```ruby
+   ruby -r rdoc -r rdoc/markdown -e '
+   md = RDoc::Markdown.new
+   doc = md.parse("YOUR CONTENT HERE")
+   formatter = RDoc::Markup::ToHtml.new(RDoc::Options.new)
+   puts formatter.convert(doc)
+   '
+   ```
+
+   For RDoc files:
+
+   ```ruby
+   ruby -r rdoc -e '
+   parser = RDoc::Markup::Parser.new
+   doc = parser.parse("YOUR CONTENT HERE")
+   formatter = RDoc::Markup::ToHtml.new(RDoc::Options.new)
+   puts formatter.convert(doc)
+   '
+   ```
+
+2. **Watch for rendering issues:**
+   - Backtick escaping (especially nested code blocks)
+   - Tilde characters being interpreted as strikethrough
+   - Special characters in examples
+   - Anchor links pointing to correct headings
+
+3. **Known RDoc Markdown limitations:**
+   - Only triple backticks for fenced code blocks (no tildes, no quad-backticks)
+   - Tilde fences (`~~~`) conflict with strikethrough syntax
+   - Use 4-space indentation to show literal code fence examples
+
+4. **Full verification**: Generate documentation and inspect the HTML output:
+
+   ```bash
+   bundle exec rake rerdoc
+   # Inspect the generated HTML file directly
+   grep -A5 "your content" _site/path/to/file.html
+   ```
+
 ### Modifying Themes/Styling
 
 When making changes to theme CSS or templates (e.g., Darkfish or Aliki themes):