CPDataKit v0.2.0 - Explicit contracts for schema, tensor, and mapping workflows

CPDataKit v0.2.0 - Explicit contracts for schema, tensor, and mapping workflows

This feature release extends CPDataKit's solver-neutral data boundary without adding scientific
inference. It makes external contracts easier to author and review, documents a stable tensor-valued
encoding, and adds an explicit JSON mapping path for command-line workflows.

Highlights

• Create and validate schemas with make_field_schema, make_profile_schema, and validate_schema.
• Serialize, write, and render schema contracts with schema_to_json, write_schema, and
  describe_schema.
• Declare optional tensor components in row-major order while retaining explicit shape rules.
• Pass a strict mapping file to validate, summary, convert, or plot with --mapping.
• Preserve no-inference behavior: mapping targets must be declared and unit conversions must be
  explicit.
• Add Hypothesis coverage for malformed nested fields and HDF5 tensor round trips.
• Include pinned reproducible package builds and CodeQL Python scanning in the maintenance gates.

Verification

The merged release preparation passed 60 local tests, Ruff checks, package build and Twine checks,
the full Windows/Ubuntu Python 3.10-3.13 CI matrix, and CodeQL Python analysis with no findings.

Scope

CPDataKit remains a schema and data-quality toolkit. It does not read ODB or DAMASK DADF5, run a
solver or UMAT, infer physical conventions, certify scientific correctness, or claim external
downstream adoption without a documented user or project.