maestro-session-seal

To seal a completed workflow session, the system validates readiness by confirming the session is running or paused, ensures no active runs remain, and verifies that all required review gates are satisfied before updating the lifecycle state.

Knowledge reconciliation in long-running coding sessions is the process of reviewing candidate knowledge receipts, surfacing duplicates and conflicts, and supporting promotion, retention, or supersession decisions to preserve validated durable knowledge.

DAG-based progression advances by sealing the completed session state, updating the lifecycle, and evaluating linked dependencies to recommend the next dep-ready session that can safely start in the workflow.

Yes, session sealing and lifecycle updates require the Maestro CLI to inspect the session ledger, process knowledge review and promotion receipts, and execute sealed state updates for DAG progression.

If active runs remain, session readiness checks will fail and prevent sealing, as the workflow requires no active runs and satisfied verification gates before reconciling durable knowledge candidates and advancing state.

Yes, you can review durable knowledge candidates before sealing by evaluating receipts, surfacing duplicates and conflicts, and making promotion, retention, or supersession decisions to reconcile knowledge during the end-of-run review.