The pipeline docs still described pipeline.ts as pseudocode and the
validation module as unwritten. Both have been implemented and run.
- CLAUDE.md: replace the "no executable pipeline yet" description with
the actual module flow, plus the two invariants worth preserving
(resumability via headword diffing, raw responses saved before parsing)
- DATA_PIPELINE.md: mark the seven implemented modules, add a module
responsibility map and the CLI flag table, drop the resolved warning
about hardcoded prompt values
- roadmap.md: check off phase 3 tasks 3.2/3.3/3.4, record where the
build diverged from the plan, note that validate.ts is stricter than
its own spec
- STATUS.md: phase 3 is data work now, not code work
Also records two open issues: the systemic difficulty-ordering rejection
cause, and the hard-tier shortfall pending a full run.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
da9cdbfa1b