Automated release: version and notes generated from pull requests merged since 1.5.2.
--plan FILEon every tool: the dry run written as a plan (tool, argv, fingerprinted inputs, commands, expected output, verify steps) thatrender.py FILEexecutes later, refusing if an input changed since the plan was made and running the verify steps (probe,checkfor a platform) afterwards. "Plan → user confirms → execute" is one round trip (issue #189 C).- feat: --plan FILE writes the dry run as a plan that render.py executes (#196)
What's Changed
- feat: --plan FILE writes the dry run as a plan that render.py executes (#189 C) by @claude[bot] in #196
Full Changelog: v1.5.2...v1.6.0