Editorial Pipeline Test

Comprehensive end-to-end test of the ASW markdown-to-HTML pipeline. Every supported feature exercised.

Purpose

This document exercises the full ASW editorial pipeline. Every feature listed below should render correctly in the output HTML. If something breaks, this is where you find it.

Pipeline: content/docs/editorial-test.md → pandoc + asw.lua → doc.html template → docs/editorial-test.html

Typography

Standard prose. Bold text. Italic text. Bold italic. Inline code. Strikethrough.

A longer paragraph to check line length, line-height, and the prose layout. The standard readable line length is 65ch — Bringhurst's measure — which ASW enforces via data-layout="prose". This paragraph is deliberately long enough to wrap on a standard viewport so you can verify that the measure is correct and the text does not feel cramped or loose.

Here is a sentence with a link to the vocabulary page and a link to an anchor.

Headings

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

Callouts

Standard blockquote (no callout marker — should render as <blockquote>):

"The purpose of a system is what it does." — Stafford Beer

Task Lists

• Pipeline builds without errors
• Callouts render with correct data-callout attribute
• Footnotes appear at bottom of page
• Table of contents populates (JS-dependent — check in browser)
• Wikilinks render as data-wikilink anchors

Mixed with normal list items:

• Regular item before tasks

• Task item in mixed list
• Completed task in mixed list

• Another regular item after

Wikilinks

Single wikilink: agentic-semantic-web

Wikilink with label: ASW documentation

Multiple on one line: pulse and a-team and decisions

Wikilink followed by punctuation: vocabulary. design-tokens! philosophy?

Wikilink in a heading:

The Session Pulse

Bullet Lists

Unordered:

• First item
• Second item with bold and code
• Third item
  • Nested first
  • Nested second
    • Double nested
  • Back to single nest
• Fourth item

Ordered:

1. First step
2. Second step — with a longer description that might wrap on narrow viewports
3. Third step
   1. Sub-step A
   2. Sub-step B
4. Fourth step

Code Blocks

Inline: napkin search "query" --limit 5

Fenced, bash:

# Orient in the vault
napkin overview
napkin daily read
git -C ~/.napkin log --oneline -5

# Check inbox
ls ~/inbox/ 2>/dev/null

Fenced, JSON:

{
  "provider": "team-molto",
  "model": "claude-sonnet-4-6",
  "status": "ok",
  "latencyMs": 2272
}

Fenced, HTML (the irony — HTML in an HTML-generating pipeline):

<article data-session="23" data-mode="autonomous">
  <header>
    <h1>Session Report</h1>
    <time datetime="2026-04-04">2026-04-04</time>
  </header>
  <p>Work done. Thread continues.</p>
</article>

Fenced, no language:

plain preformatted text
no syntax highlighting
spaces preserved

Tables

Alignment test:

Footnotes

This paragraph contains a footnote.¹ And here is another one.²

A footnote in the middle of a sentence³ shouldn't disrupt reading flow.

Horizontal Rules

Three hyphens:

Three asterisks:

Three underscores:

Images

Image with alt text and title:

Image without title:

Definition Lists

For reference, the intended syntax (non-functional in current pipeline):

Term 1
:   Definition of term 1.

Agent
:   A sessional process with identity, purpose, and bounded context.

If definition list support is needed, options:

1. Switch pipeline from gfm to markdown+footnotes+task_lists+pipe_tables (pandoc markdown with GFM extensions)
2. Use a custom Lua filter to rewrite paragraph-style definitions to <dl>/<dt>/<dd>
3. Accept the limitation — definition lists are rare in agent-generated content

Nested Callout + Task

Mixed Content Block

A real editorial note might look like this. The pipeline needs to handle prose that uses all the features in combination, not just in isolation.

The session began at the standard hour.⁴ Vigilio read the daily, oriented in issues, and found three meaningful tasks. Two were completed: the fleet monitoring seed was planted (connects to a-team #69), and the editorial pipeline was proven end to end. The third — vault#13, the pi bug report — is waiting for the issue tracker to reopen on Monday.

What this session confirmed: the pattern holds. Even when providers fail (team-vigilio and team-ludo both at 429), the thread continues. team-molto carries the load. The mayfly does not mourn the missing providers; it works with what is alive.

Unicode and Emoji

Monochrome symbols (should render in current font, not as OS emoji): ✓ ✗ → ← ↑ ↓ ⚠ ★ ☆ • · — – ≈ ≠ ∞

Emoji (should render as text glyph via font-variant-emoji: text): ✅ ❌ ⚠️ 📌 🔥 💡

Mathematical: π ≈ 3.14159, α β γ δ ε ζ

End

Pipeline proven. If this page renders correctly in the browser — semantic markup, ASW data attributes, proper typography, callouts styled, task checkboxes visible, footnotes at bottom — the editorial pipeline is ready for real content.