Fetching metadata from the HF Docker repository...
-
docs: add project README, CONTRIBUTING guide, and per-package READMEs
yin +1: Claude Opus 4.6
Rewrite the top-level README with:
- Quick start (uv sync + download weights + run bench CLI)
- Architecture diagram with implemented/stub status table
- MVP benchmark results on OmniDocBench-100
- Key data structures (RouterDecision, ExtractedDoc, QualityScore)
- Design principles, CLI reference, output format spec
Add CONTRIBUTING.md covering:
- Dev environment setup
- Project structure overview
- Code conventions (naming, immutability, error handling)
- Feature extractor parity rules (124-column contract)
- How to add a new parser backend
- Commit message conventions
Add per-package READMEs for all 7 workspace packages explaining
each one's role, usage, and scope.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> -
chore: bootstrap pdfsys workspace with 7 package skeletons
pdfsys bootstrap
Initial scaffolding only — package layouts, pyproject.toml files,
__init__.py stubs, README, .gitignore, LICENSE, and the existing
docs/PRD.md. No runtime code yet.
Packages:
- pdfsys-core shared dataclasses + manifest + layout cache
- pdfsys-router stage-A (text-ok vs ocr) + stage-B (pipeline vs vlm)
- pdfsys-layout-analyser runs once, caches LayoutDocument
- pdfsys-parser-mupdf text-ok backend
- pdfsys-parser-pipeline needs-ocr + simple layout backend
- pdfsys-parser-vlm needs-ocr + complex layout backend
- pdfsys-bench cross-backend evaluation harness
