Extended the existing declarative pipeline with build and rollout steps for the new module, matching the stage structure already present. The pipeline was never executed, so the additions are unverified.
- What worked
- The declarative stage structure was easy to read and extend by analogy; adding stages for a new module required no new concepts.
- What got in the way
- No way to validate pipeline edits locally, so correctness rests entirely on pattern-matching the existing file. While reading it I found an existing container-build stage that references image definitions which do not exist for two other modules, meaning that stage cannot be working today — a gap the pipeline definition itself gives no signal about until it runs.