history

Curvature consolidates migration and analysis state

id: LK-20260716-curvature-project-structure
date: 2026-07-16
sequence: 97
type: refactor
compatibility: compatible
component: `labkit_CurvatureMeasurement_app` | `1.4.2 -> 1.4.3`
scope: Image Measurement
scope: App structure

Context

Curvature split static metadata across files, exposed four generic lifecycle functions including a filename-encoded migration, and stored five computation tasks/results under +appState. Session restoration also read the nested portable source path directly.

Decision and rationale

Use one project specification with a version-aware migration entry. Runtime V2 calls Migrate(project,fromVersion) for each missing version; Curvature keeps only the actual version-1 transformation. Put fit and length task/result shapes beside the analysis functions that consume them.

Changes

Consolidated product metadata and requirements in definition.m.
Consolidated project creation, validation, and the v1 source migration in projectSpec.m.
Moved decoded-image reconstruction to root createSession.m.
Moved all five generic state helpers to +analysisRun.
Removed separate metadata and lifecycle files.
Replaced direct portable-reference access with the Runtime path accessor.
Kept managed anchor editing, scale calibration, curve fitting, length measurement, overlay rendering, and exports unchanged.

User and data impact

Opening current or version-1 projects, tracing/removing anchors, calibrating scale, fitting curvature, measuring length, and exporting results behave unchanged. Developers now find every durable-version rule in one file and every numerical result/task next to the numerical implementation.

Compatibility and migration

The current payload stays at version 2. Version-1 inputs.source is still moved to inputs.sources exactly once. No new payload migration is introduced.

Validation

Unit tests cover current project/session construction, v1 migration, fit and length numerics, physical/pixel scales, densification, invalid points, result tables, and deterministic task fingerprints. The hidden GUI suite covers image loading, anchor editing guidance, managed interactions, viewport behavior, scale calibration, results, and save/load.

Evidence

Known limitations and follow-up

Other versioned Apps still use filename-per-step migrations and will move to one project entry during their own behavior audits.