Release v0.2.0: Add build, serve, and manifest support

New features:
- `longecho build` generates static sites from ECHO archives
- `longecho serve` provides local HTTP preview
- Manifest support (manifest.json/yaml) for archive configuration
- Hierarchical archive support with sub-source discovery

Changes:
- Restructure docs: point MkDocs to spec/ directory
- Remove outdated docs/ in favor of spec/ as single source of truth
- Add JSON schema for manifest validation
- Add Jinja2 templates for site generation
- Expand test coverage (114 tests, 78% coverage)

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

Author: queelius

CLAUDE.md

@@ -4,52 +4,88 @@ Guidance for Claude Code when working with this repository.
 
 ## Project Status
 
-**longecho is specification-only.** No implementation exists yet.
+**Alpha.** Core functionality implemented and tested (78% coverage, 114 tests).
 
 ## What longecho Is
 
 longecho provides:
 
-1. **Documentation** — Explains and motivates the ECHO philosophy
-2. **Validator** — Checks if a directory is ECHO-compliant (`longecho check`)
+1. **Documentation** — Explains and motivates the ECHO philosophy (`spec/`)
+2. **Validator** — Checks ECHO compliance (`longecho check`)
+3. **Discovery** — Finds ECHO sources (`longecho discover`, `longecho search`)
+4. **Site Builder** — Generates unified static sites (`longecho build`)
+5. **Dev Server** — Previews archives locally (`longecho serve`)
 
-That's it. longecho is not an orchestrator, not a format mediator, not a registry.
+## Commands
 
-## What longecho Is NOT
+```bash
+longecho check ~/path       # Is this directory ECHO-compliant?
+longecho discover ~/        # Find ECHO-compliant directories
+longecho search ~/ "query"  # Search README descriptions
+longecho info ~/path        # Show detailed source info
+longecho formats            # List recognized durable formats
+longecho build ~/archive    # Generate static site
+longecho serve ~/archive    # Preview via HTTP
+```
+
+## Architecture
 
-- **Not an orchestrator** — Toolkits (ctk, btk, persona-tk, stone-tk) invoke themselves
-- **Not a format mediator** — Each toolkit defines its own input/output formats
-- **Not a registry** — Each toolkit's own README documents its compliance
+```
+src/longecho/
+├── __init__.py      # Public API exports
+├── checker.py       # ECHO compliance checking
+├── discovery.py     # Source discovery and search
+├── manifest.py      # Manifest loading/validation
+├── build.py         # Static site generation
+├── serve.py         # HTTP server for preview
+├── cli.py           # Typer CLI interface
+└── templates/       # Jinja2 HTML templates
+```
 
 ## Key Principles
 
 1. **ECHO philosophy** — Self-describing data with README.md + durable formats
-2. **Minimal scope** — longecho is docs + validator only
-3. **Standalone toolkits** — persona-tk and stone-tk work independently
+2. **Graceful degradation** — Archives work without longecho; longecho adds convenience
+3. **Standalone toolkits** — ctk, btk, etc. work independently; longecho unifies their outputs
 
 ## Documentation Structure
 
 ```
 spec/
 ├── ECHO.md              # ECHO philosophy (standalone)
-├── LONGECHO.md          # Validator specification
-├── PERSONA-TK.md        # Persona toolkit spec (standalone)
-├── STONE-TK.md          # Stone toolkit spec (standalone)
-├── TOOLKIT-ECOSYSTEM.md # List of existing toolkits
+├── LONGECHO.md          # Tool specification
+├── MANIFEST-SCHEMA.md   # Manifest format spec
+├── PERSONA-TK.md        # Persona toolkit spec
+├── STONE-TK.md          # Stone toolkit spec
+├── TOOLKIT-ECOSYSTEM.md # List of toolkits
 └── INTERVIEW-INSIGHTS.md # Design decisions
 ```
 
-## Expected Commands (When Implemented)
+## Development
 
 ```bash
-longecho check ~/path    # Is this directory ECHO-compliant?
-longecho discover ~/     # Find ECHO-compliant directories
-longecho search ~/       # Search README descriptions
+# Install with dev dependencies
+pip install -e ".[dev,full]"
+
+# Run tests
+pytest tests/ -v
+
+# Run with coverage
+pytest tests/ --cov=src/longecho --cov-report=term-missing
+
+# Type checking
+mypy src/longecho/
+
+# Linting
+ruff check src/longecho/
 ```
 
-## Expected Tech Stack
+## Tech Stack
 
-- Python 3.8+
-- pytest for testing
-- black/flake8/mypy for code quality
+- Python 3.9+
 - Typer for CLI
+- Rich for terminal output
+- Jinja2 for templates
+- pytest for testing
+- mypy for type checking
+- ruff for linting

README.md

@@ -1,17 +1,20 @@
 # longecho
 
-ECHO philosophy documentation and compliance validator.
+ECHO philosophy documentation, compliance validator, and static site builder.
 
 ## Status
 
-**Incubating.** Specifications are being developed. No implementation yet.
+**Alpha.** Core functionality implemented and tested.
 
 ## What This Is
 
 longecho provides:
 
 1. **Documentation** — Explains and motivates the ECHO philosophy
 2. **Validator** — Checks if a directory is ECHO-compliant
+3. **Discovery** — Finds and searches ECHO sources
+4. **Site Builder** — Generates unified static sites from archives
+5. **Dev Server** — Previews archives via HTTP
 
 ## The ECHO Philosophy
 
@@ -24,31 +27,69 @@ A directory is ECHO-compliant if it has a README and uses durable formats. That'
 
 See [spec/ECHO.md](spec/ECHO.md) for the full philosophy.
 
-## Commands (Planned)
+## Installation
+
+```bash
+pip install longecho
+
+# With optional dependencies for YAML manifests
+pip install longecho[full]
+```
+
+## Commands
 
 ```bash
 # Check if a directory is ECHO-compliant
 longecho check ~/my-data/
 
-# Find ECHO-compliant directories (optional)
+# Find ECHO-compliant directories
 longecho discover ~/
 
-# Search README descriptions (optional)
+# Search README descriptions
 longecho search ~/ "conversations"
+
+# Show detailed info about a source
+longecho info ~/my-data/
+
+# List recognized durable formats
+longecho formats
+
+# Build a static site from an ECHO archive
+longecho build ~/my-archive/
+
+# Serve an archive via HTTP for preview
+longecho serve ~/my-archive/ --port 8000
 ```
 
-## What longecho Is NOT
+## Boundaries
 
-- **Not an orchestrator** — Toolkits invoke themselves
-- **Not a format mediator** — Each toolkit defines its own interfaces
-- **Not a registry** — Toolkits document their own compliance
+**longecho unifies, but doesn't orchestrate toolkits.** Each toolkit (ctk, btk, etc.) exports its own ECHO-compliant archive independently. longecho's `build` command combines these into a unified browsable site, but doesn't invoke or manage the toolkits themselves.
+
+**longecho doesn't mediate formats.** There is no central interchange format. Each toolkit defines its own input/output formats.
+
+**longecho doesn't maintain a registry.** If a toolkit is ECHO-compliant, its own README documents that fact.
 
 ## Documentation
 
 | Document | What it covers |
 |----------|----------------|
 | [spec/ECHO.md](spec/ECHO.md) | ECHO philosophy |
-| [spec/LONGECHO.md](spec/LONGECHO.md) | Validator specification |
-| [spec/PERSONA-TK.md](spec/PERSONA-TK.md) | Persona toolkit spec (standalone) |
-| [spec/STONE-TK.md](spec/STONE-TK.md) | Stone toolkit spec (standalone) |
-| [spec/TOOLKIT-ECOSYSTEM.md](spec/TOOLKIT-ECOSYSTEM.md) | List of existing toolkits |
+| [spec/LONGECHO.md](spec/LONGECHO.md) | Tool specification |
+| [spec/MANIFEST-SCHEMA.md](spec/MANIFEST-SCHEMA.md) | Manifest format for archives |
+| [spec/TOOLKIT-ECOSYSTEM.md](spec/TOOLKIT-ECOSYSTEM.md) | List of ECHO-compliant toolkits |
+
+## Development
+
+```bash
+# Install with dev dependencies
+pip install -e ".[dev,full]"
+
+# Run tests
+pytest tests/ -v
+
+# Type checking
+mypy src/longecho/
+
+# Linting
+ruff check src/longecho/
+```