update-docs

Automating documentation updates based on code changes is achieved by detecting git diffs and sequentially applying read-before-write updates to affected API docs and guides. This workflow tracks progress using a backlog to ensure reliability and avoid mid-run failures.

Generating release notes for a new firmware version is handled using a release-aware mode that regenerates release artifacts. This mode updates breaking changes, README files, and changelogs based on detected differences since the previous release tag.

A sequential backlog-tracked workflow keeps documentation consistent by running exactly one doc-area subagent at a time. This ordered execution ensures clear progress visibility and prevents mid-run failures when updating API docs or feature notes.

Updating API docs and guides without regenerating full release artifacts is supported through standalone doc updates. This mode scopes updates strictly to git diffs, targeting only the affected documentation areas rather than running the complete release process.

Manually scoping documentation areas when fixing firmware docs is not required. The workflow is change-driven, automatically detecting what changed since the previous tag and targeting only the impacted guides, API docs, and feature notes.

Ordered execution for doc areas is used to guarantee reliable documentation updates. By processing one subagent at a time with read-before-write operations, the workflow maintains consistency across API docs, release notes, and changelogs without interruption.