context-health

Context health validation detects missing, empty, or broken context files and memory references to prevent downstream failures. It checks the existence and non-emptiness of AGENTS.md, memory/MEMORY.md, ERROR_LOG.md, and PENDING_LOG.md at session-open or project bootstrap.

Validating memory references for broken links requires checking references to features and branches within your memory files. This process detects broken references, flags missing branches, and identifies whether your MEMORY.md is monolithic or index-style to ensure context integrity before you begin work.

You should run a context integrity check during session-open, project bootstrap, or when starting work on a new or rarely visited project. This timing ensures essential context files and memory references are valid before proceeding, preventing downstream failures caused by stale or missing context.

Context health validation works for both monolithic MEMORY.md files and index-style memory structures. The validation process actively flags the memory style being used and checks all internal references for broken links and missing branches, ensuring context integrity regardless of the memory format.

A CONTEXT_OK status means all context file existence, non-emptiness, and memory reference checks have passed successfully. A CONTEXT_STALE status indicates problems were found, returning detailed issues about missing files, empty context documents, or broken memory references that need resolution.