morning-review

Automating morning review workflows involves orchestrating executive summary display, lifecycle advancement, and backlog item handling for overnight Cortex sessions. This process assesses completed, deferred, and failed features while emitting structured events for auditing.

Lifecycle advancement for completed and deferred features works by reading overnight state, morning reports, and plan documentation to satisfy gating logic. It coordinates auto-close actions and updates backlog items across grouped feature rounds.

Handling deferred questions requires prompting for user answers during the morning review and persisting responses to deferred feature markdown files. This ensures unresolved questions from overnight sessions are captured and documented for future reference.

Backlog updates and PR merge steps integrate into the morning report workflow by locating the integration branch, updating tickets, and guiding post-merge actions. This creates audit-ready artifacts across lifecycle and backlog logs for traceability.

Yes, overnight state, morning report, and plan documentation are required inputs to run an automated morning review. These documents satisfy gating logic and provide the session verdicts, counts, and duration needed for executive summary display.