docs: align sprint orchestration behavior with current execution flow - #756
Conversation
- Replace `mergeProtocol` and `actionRequiredProtocol` with `protocol` in `atomic-loop.md` and `docs-web/user/sprint-orchestration.md`. - Detail correct behavior of QA holding a task in `QA_REVIEW_FAILED` state on exhaustion. - Re-align flowcharts and list steps in sprint loop. Co-authored-by: numnx <1517214+numnx@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
6ab8019
into
feature/CODUX-44-qs-documentation-developer-surface-audit-2
This PR brings the orchestration step documentation and UI reference pages into alignment with the existing implementation of
src/domain/sprint/orchestrator/cycle-runner.tsandsrc/sprint/steps/protocol-step.ts.It updates:
docs/sprint-loop/atomic-loop.mdto show the correct execution phases and replace outdated references tomergeProtocolandactionRequiredProtocolwithprotocol.docs-web/user/sprint-orchestration.mdto sync withatomic-loop.md's cycle and state machine updates, particularly describing how a completed task fails intoQA_REVIEW_FAILEDcorrectly instead of an infinite wait.docs/architecture/quality-assurance-agent.mdto ensureQA_REVIEW_FAILEDhold behavior aligns tightly with current code.PR created automatically by Jules for task 7839629614823547377 started by @numnx