Carried product financial configs id generation

Verification Boundary

The assertions run compatibility adapters for earlier product shapes. Their historical contract is distinct from the current catalogue contract.

What This Suite Proves

The carried assertions exercise id generation for the earlier product financial configs shape through compatibility adapters. They supply engineering evidence without proving the current configuration contract.

What It Does Not Prove

These assertions do not prove workspace enforcement, transactional rollback, concurrent writes or deployed behavior. Current-contract acceptance requires a separate binding.

Real Dependencies and Test Doubles

The functions under test are real JavaScript or compiled service code. Inputs and surrounding contexts are fixtures; PostgreSQL and external applications are absent.

Must Not Be Doubled

Keep the function under test and its actual return or refusal behavior real. Do not treat a fixture assertion as database, permission or lifecycle proof.