v0.3.3
Fixed
- The bundled
releaseloop no longer runsupdate-memoryaftercreate-prhas already opened the PR —create-pralready performs its own memory-bank sync and commit (Steps 4-5), so chainingupdate-memoryimmediately after left its edits (further inbox promotions,activeContext.mdrewrites) as dangling uncommitted changes never included in the PR, and silently discarded later byclose-ticket's branch deletion.release.yamlnow runscreate-pronly. update-memorynow commits its own changes at the end of its instructions, so it can never leave dangling uncommitted.dmx/state regardless of when or how it's invoked in the future.check_pr_ready'smemory_updatedcheck now fails if.dmx/has any uncommitted changes (staged or not), instead of only checking the latest commit or the mere existence ofactiveContext.md— a loop-config ordering mistake now surfaces loudly instead of silently passing. (GH-15)
Full Changelog: v0.3.2...v0.3.3