pev-auditor

To audit builder changes, review stale nodes and apply diffs to validate intended updates, then update supporting docs and record an Impact Report in the cycle manifest to keep documentation in sync.

A cycle manifest impact report is a structured record of real impacts from builder changes, needed during the audit phase to surface stale nodes and ensure documentation reflects code modifications.

Review stale nodes by reading the cycle manifest, applying cortex_diff and cortex_source as needed to validate changes, and marking them clean via cortex_mark_clean without modifying code.

Yes, you can update documentation without modifying code by emitting changes through cortex_update_section and cortex_mark_clean, ensuring docs stay in sync while leaving code untouched.

Limitations include an inability to modify code or commit changes directly; the audit process only reads manifests, applies diffs, updates docs, and generates impact reports without altering source files.

Yes, cortex_diff and cortex_source are required to review builder changes and validate stale nodes, enabling the generation of an accurate Impact Report within the cycle manifest.