Bug Description
After following a workflow to create, implement, test, commit, and push a user story, the Status of the User Story in the corresponding MD file was stale, still showing as "Read for Review".
I was caught by surprise when 1 day later, after having finished with the user story and dealing with another topic, after the conversation was compacted, I was presented with the message "Story is ready for @dev implementation."
Then, when I inquired with the agent to double-check the Story status, it confirmed the issue and updated the Story status, as follows:
I am now asking myself if it should really mark the user Story as "Done", since it said the Story was ready for @devops to push, create PR, etc.
Steps to Reproduce
- Just say you need to have something implemented and explain what it is.
- The agent will start the Spec Pipeline for a brownfield project. Start answering the questions.
- Have the user story implemented and tested.
- Ask the agent if there is anything left. It will tell you that it is all set. Acknowledge it.
- Start working on something else, like fixing a bug or other enhancements.
- When it resumes from a "Conversation compact", the agent tells you that Story was "Ready for review".
Expected Behavior
In step #6 above, I would expect the previous conversation (before the compacting) to resume, and not be "warned" that the Story I was working on the day before was "Ready for Review" when it was actually "Done".
Actual Behavior
Story status is "Ready for Review" when it was actually "Done".
Error Output
Affected Area
Core Framework (.aiox-core/core/)
AIOX Version
5.0.4
Operating System
macOS (Apple Silicon)
Node.js Version
25.9.0:q!
Priority
Medium - Minor impact, workaround available
Checklist
Bug Description
After following a workflow to create, implement, test, commit, and push a user story, the Status of the User Story in the corresponding MD file was stale, still showing as "Read for Review".
I was caught by surprise when 1 day later, after having finished with the user story and dealing with another topic, after the conversation was compacted, I was presented with the message "Story is ready for @dev implementation."
Then, when I inquired with the agent to double-check the Story status, it confirmed the issue and updated the Story status, as follows:
I am now asking myself if it should really mark the user Story as "Done", since it said the Story was ready for @devops to push, create PR, etc.
Steps to Reproduce
Expected Behavior
In step #6 above, I would expect the previous conversation (before the compacting) to resume, and not be "warned" that the Story I was working on the day before was "Ready for Review" when it was actually "Done".
Actual Behavior
Story status is "Ready for Review" when it was actually "Done".
Error Output
Affected Area
Core Framework (.aiox-core/core/)
AIOX Version
5.0.4
Operating System
macOS (Apple Silicon)
Node.js Version
25.9.0:q!
Priority
Medium - Minor impact, workaround available
Checklist