Feature Request
Describe the feature you'd like
- Integrate
ManifestContext into the workflow engine (issue for Milestone 4) so that a full workflow run --manifest run.json produces one unified manifest covering every step, not just a single command. Add an automatic console summary printed after every workflow run (no flag required).
- Provide five tested, real-world example workflows: reproducible research download, automated nightly publishing, batch deployment with error recovery, CI/CD integration, and failure debugging.
Why is this feature important?
A workflow without a unified audit trail is hard to debug or reproduce — this makes the whole pipeline traceable and reproducible the same way a single manifest-backed command already is, and gives concrete usage examples so the workflow engine is easy to adopt rather than purely theoretical.
Feature Request
Describe the feature you'd like
ManifestContextinto the workflow engine (issue for Milestone 4) so that a fullworkflow run --manifest run.jsonproduces one unified manifest covering every step, not just a single command. Add an automatic console summary printed after every workflow run (no flag required).Why is this feature important?
A workflow without a unified audit trail is hard to debug or reproduce — this makes the whole pipeline traceable and reproducible the same way a single manifest-backed command already is, and gives concrete usage examples so the workflow engine is easy to adopt rather than purely theoretical.