agent-context-keeper

Delta-based synchronization updates the agent context by applying only changed sections triggered by file saves, ensuring all agents operate on current state without rebuilding the entire context.

Conflict resolution and locking mechanisms prevent race conditions by enforcing frontmatter metadata, token budgets, and dirty-flag lifecycles when multiple agents update context simultaneously.

Context refresh is triggered by commit, pull, file-save, and manual orchestrator triggers, applying delta changes to maintain timely and accurate agent state updates.

Dirty-flag driven workflows with changelogs and audit trails ensure all context updates are auditable, keeping agents aligned and enforcing frontmatter metadata during synchronization.

Delta-based synchronization minimizes work by applying only changed sections to the .agent context, enforcing token budgets and frontmatter metadata for safe, auditable updates.

Full context rebuilds are unnecessary when delta sync can apply changed sections from code edits, managing dirty flags and conflicts to ensure agents operate on current state safely.