Legacy migration record

This section records the completed reconstruction method and the disposition of legacy capabilities. It is historical evidence, while the concept and reference sections describe the current product.

Each capability was reconsidered at an explicit module seam rather than copied directory by directory:

1. Record existing behaviour and tests.
2. Confirm the behaviour that should survive.
3. Define the module interface and invariants.
4. Reuse, adapt, rewrite, or retire the legacy implementation.
5. Verify the interface with acceptance and conformance tests.
6. Update current documentation to describe the accepted result.

The capability inventory maps that work to the implemented modules. Wayfinder issues documents the issue contract used during reconstruction.