Skip to content

DocGuard v0.41.5

Choose a tag to compare

View all tags
@github-actions github-actions released this 17 Sep 23:40
· 88 commits to main since this release
v0.41.5
e602ec3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Automated weekly release — batches everything merged since v0.41.4.

Changed

  • fix: four tool defects from a downstream field report (#410)
  • chore: use generic project references and stop tracking .wolf/ (#411)

Changed

  • Replaced named third-party project references in source comments, tests and
    changelog history with generic terms. Field-test provenance is still recorded;
    the projects are no longer identified by name. Stopped tracking .wolf/
    (local agent working notes, never part of the published package).

Fixed

  • Stop counting a review stamp as a content change. Adding or updating
    <!-- docguard:last-reviewed --> in a spec artifact changed its registry
    digest, so the review that Freshness (FRS002) asks for immediately made the
    spec registry STALE and demanded specs --write — the tool created the work
    it then reported. That marker is now excluded from the digest source;
    docguard:version and docguard:status still re-digest, because those are
    substantive lifecycle edits. Registries written by earlier releases keep their
    trust (both digest forms are accepted); a project whose specs already carry a
    review stamp needs one docguard specs --write to settle.
  • Stop reporting a document as "review due" while it is staged in the commit
    being checked. A pre-commit hook runs guard against the very change being
    made, so an author updating AGENTS.md was told to review AGENTS.md. Being
    edited in this commit is now treated as the strongest freshness signal and
    outranks the repository-wide commit-count heuristic.
  • Stop leaving .docguard-specs.json.bak behind. specs --write regenerates a
    Git-tracked, fully derived file, so the backup was noise that DocGuard then
    reported as an undocumented config file (DCV001). DocGuard also no longer
    raises DCV001 for any .bak it wrote itself.
  • Report what specs --write actually did. It printed the pre-write differences
    under a "Differences:" heading after reporting WRITTEN, reading as though the
    drift were still outstanding; resolved differences are now labelled as resolved.
Assets 4
Loading