are-update

Incremental documentation updates target only changed files by reading a version file and executing background updates, avoiding full rebuilds and manual rework for changed codebase files.

Background documentation updating runs without blocking active development by executing updates in the background, polling progress logs for real-time status, and summarizing results after completion.

Yes, you can run a documentation update without committing changes first by using the --uncommitted flag to process uncommitted changes in your codebase.

You can preview documentation changes before applying updates by using the --dry-run flag to simulate the incremental update process and review expected results without modifying files.

Monitoring progress for background codebase documentation updates is handled by polling progress logs, which show real-time status and ETA estimates while the background execution runs.

You can trace and diagnose issues during incremental documentation updates by using the --trace flag to output detailed diagnostic information during the background execution process.