feat(examples): add content-generator example demonstrating Prompt Dependency Resolution

This example demonstrates the full workflow of generating InfoTech primers
using MarkiTect's Prompt Dependency Resolution infrastructure.

Features demonstrated:
- Artifact creation and storage with content-based addressing
- PromptTemplate with @{macro} resolution across multiple spaces
- Automatic dependency tracking and graph construction
- Provenance tracing from outputs back to inputs
- Visualization export (Mermaid format)
- Incremental execution with change detection

Files added:
- generate_primers.py: Complete working example
- README.md: Quick start guide and architecture overview
- TUTORIAL.md: Comprehensive 500+ line tutorial
- templates/generate-primer.md: Template with macros
- artifacts/topics/: ETL and Microservices topic definitions
- artifacts/guidelines/: Authoring rules and research protocol
- prepdr/: Original manual system (preserved for reference)

Example output:
- Generates 2 primers (ETL, Microservices)
- Creates 8 artifacts across 4 information spaces
- Records 8 dependency edges in SQLite database
- Exports dependency graph visualization

Run with: cd examples/content-generator && python generate_primers.py

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

examples/content-generator/templates/generate-primer.md

@@ -0,0 +1,59 @@
+---
+id: generate-primer-v1
+name: GeneratePrimerTemplate
+artifact_type: template
+description: PromptTemplate for generating InfoTech primers with dependency resolution
+version: 1.0.0
+---
+
+# Generate InfoTech Primer
+
+You are conducting foundational research and authoring an InfoTech Primer.
+
+**Your Task:** Produce a complete, publication-ready InfoTech Primer for the given topic, following the authoring rules exactly.
+
+## Topic Specification
+
+@{topic}
+
+## Authoring Guidelines
+
+@{authoring_rules}
+
+## Research Protocol
+
+When researching this topic, follow this systematic approach:
+
+@{research_prompt}
+
+---
+
+## Output Requirements
+
+Generate a complete primer document with the following structure:
+
+1. **Definition** (2-4 sentences, precise and unambiguous)
+2. **Context** (domain positioning and architectural level)
+3. **Core Concepts** (bullet points, one concept per line)
+4. **Scope and Non-Scope** (explicit inclusions and exclusions)
+5. **Practical Implications** (design consequences, not tutorials)
+6. **Formal Standards and Authoritative Sources** (with links)
+7. **Related Concepts** (one-line descriptions)
+
+**Constraints:**
+- Follow declarative, neutral tone
+- No metaphors, marketing language, or tutorials
+- Target length: 600-1,000 words
+- Include at least one authoritative source
+- Use consistent terminology throughout
+
+**Validation:**
+Before finalizing, verify:
+- [ ] All required sections are present
+- [ ] Definition is precise and unambiguous
+- [ ] Scope boundaries are explicit
+- [ ] At least one authoritative source is linked
+- [ ] No tutorial or marketing content
+- [ ] Language follows declarative style rules
+
+Generate the primer now.