Validate a pipeline application change

Goal

Turn a pipeline application edit into one coherent, verifiable repository change that is ready for managed publication.

Prerequisites

• an onboarded application repository;
• a checked-in Rust serde record type;
• a pipeline manifest and its transform code;
• focused tests for the changed behavior.

Steps

1. Confirm the Rust schema change is additive, keeps stable identity fields, and gives newly persisted fields compatible serde defaults or optionality.
2. Check that every persisted row has a stable dataset reference and primary key.
3. Validate the pipeline TOML with the repository's manifest test target.
4. Run the transform's focused test with a bounded timeout.
5. Regenerate any reference artifact owned by the repository and run its drift check.
6. Open one pull request containing schema, manifest, transform, tests, and docs.

For this monorepo, the focused commands follow this shape:

timeout 300 rac cargo test -p <changed-crate>
node docs/scripts/gen-route-reference.mjs --check

Use the commands supplied by an external application's repository when its layout differs.

Expected result

The manifest parses and lowers, the transform test passes, generated references match their sources, and the pull request shows the intended route and dataset changes together.

Failure modes

Reference

Continue with Build a vertical and Scaffold a narrow app.