devlog-maintainer

To maintain an accurate devlog, you propagate code changes into current state files and ADR records using a trigger-based matrix. This ensures your architecture decisions and release documentation stay synchronized without rewriting the entire history.

The best way to update ADR records after a bug fix is to apply a trigger-based propagation matrix that adds required frontmatter to your records directory. This synchronizes only the backlog and capability documents that actually changed during the fix.

You can use devlog propagation in repositories lacking a standard topology, but the system will explicitly ask before bootstrapping the missing docs/devlog directory structure. It operates topology-aware to ensure changes map to the correct archival layers.

To enforce required ADR frontmatter fields during documentation maintenance, the system validates records entries against predefined schema requirements before synchronizing the current cycle state. This prevents incomplete architecture decisions from entering the devlog.

Your devlog drifts out of sync because real code changes are not automatically reflected in the correct documentation layers. Applying a structured propagation process updates current state, ADR records, and archival snapshots only where changes occurred.

You should run an index refresh or checklist verification for your devlog during version closeouts or reviews when supporting scripts are present. This validates that your structured project governance documentation accurately reflects the propagated change outcomes.