live-state-orchestrator

To keep project state files in sync after a milestone, you need to update governed context files like plan progress, durable memory, and handoff status. This synchronization prevents project drift by recording actual milestone progress and resolving open problems.

Handoff lifecycle management for parallel sessions enforces active, consumed, and archived transitions for handoff files. It uses a mandatory pre-close check to prevent overwriting newer work and ensures concurrency safety across collaborators.

Resolve file paths from a context manifest by checking the project's CONTEXT-MANIFEST.md file. This manifest-based path resolution identifies canonical state files, checks for drift and lock files, and stops when evidence or ownership is unclear.

You need to update project context files and durable memory after significant fixes, completed rollout phases, or session closure. This preserves durable lessons, marks resolved problems, and prepares the project state for the next collaborator.

Project state synchronization relies on docs/context/CONTEXT-MANIFEST.md for path resolution and governance. Without this manifest file, the concurrency-aware governance workflow cannot validate evidence or safely update canonical state files.

Project state synchronization stops when evidence or ownership is unclear to enforce evidence-aware status changes and concurrency safety. This pre-close validation prevents overwriting newer parallel work and maintains handoff lifecycle integrity.