Back to corpus
research noteexperiment writeup candidatescore 24

Pydantic v2 Migration - COMPLETE ✅

2. **[core/coordinates.py](core/coordinates.py:18)** - Updated: `@validator` → `@field_validator` (2 validators) - Added `@classmethod` decorators

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Status**: ✅ **COMPLETE** - All modules successfully migrated to Pydantic v2.11.5 The DLM package now fully supports Pydantic v2 with all imports working correctly and all tests passing (16/16). ### Migration Statistics - **Files Fixed**: 9 core files - **Validators Updated**: 7 instances - **Field Annotations Added**: 12 instances - **Import Errors Resolved**: 2 instances - **Test Success Rate**: 100% (16/16 tests passing) #### Core Pydantic v2 Fixes 1. **[models/generation.py](models/generation.py:3)** - Updated: `@root_validator` → `@model_validator(mode='after')` - Fixed: `text = ""` → `text: str = ""` 2. **[core/coordinates.py](core/coordinates.py:18)** - Updated: `@validator` → `@field_validator` (2 validators) - Added `@classmethod` decorators

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.