Slice 6: SKILL.md restructure + integration

[qwerkilo]

Parent

#1 — context2html Framework

What to build

Restructure SKILL.md from a monolithic 5-step linear workflow into a two-layer document:

1. Example flow — the familiar Steps 0-5, now calling framework APIs internally
2. Framework API reference — listing ComponentRegistry, TemplateRenderer, ThemeProvider with usage patterns

Key changes:

• The "Example flow" section replaces manual instructions ("copy component code block from components/NN-name.md") with API calls ("call registry.get_component(id) to retrieve component code")
• The "Framework API" section is concise — just the signatures, what each method returns, and a one-line description
• D1-D5 humanization rules stay as-is (they are content rules, not API concerns)
• All hard constraints and gotchas remain (they are project invariants, not workflow steps)

Integration verification:

• Use the framework APIs to regenerate examples/0001-demo-report.html — this proves the end-to-end workflow works
• Run validate-report.py on the regenerated demo — it should pass all 21 checks

Acceptance criteria

• SKILL.md has a ## Example flow section with the 5-step workflow
• SKILL.md has a ## Framework API section with registry/renderer/theme signatures
• The example flow references the three framework APIs instead of manual copy-paste instructions
• examples/0001-demo-report.html regenerated via framework APIs passes validate-report.py
• All 376 existing tests still pass
• SKILL.md is still readable and actionable by a new agent session

Blocked by

• Slice 2: Component Registry + metadata pilot (component #26) #3 (Component Registry)
• Slice 3: Template zones + Renderer #4 (Template Renderer)
• Slice 4: Theme Provider #5 (Theme Provider)