Engineering reproduction checklist

Documentation status: guide — see Maturity and evidence.

A developer should be able to reproduce the engineering workflow from the site alone.

• Create a dedicated test package and manifest when tests are not production models.
• Declare a test-suite Entity that implies lgc#unit_test.
• Represent coherent test cases as declared Actions and use explicit assertions.
• Verify model loading before debugging script behavior.
• Follow configuration -> package -> manifest -> model -> concept -> object -> collection -> action -> event -> view -> persistence -> service.
• Include conceptual identifiers in logs and diagnostics.
• Test published actions, processes, async events, and view bindings as public contracts.
• Keep providers and joins bounded and measure model-level operations.
• Keep extension points capability-oriented and replaceable.
• Treat action signatures, role paths, event names, process states, and service mappings as governed compatibility surfaces.
• Re-run documentation validation, publication manifest generation, and HTML smoke build after each documentation pass.
• Preserve useful source examples, normalizing historical TXXX identifiers to XXX instead of dropping the example.