Release 0.5.2

Documentation and reporting only. Neither capture layer changes, and an
application that upgrades sees no behaviour difference outside `rake
audit_log:coverage`'s output.

`audit_log:coverage` now leads its finding with a count and sorts the table list
alphabetically -- `23 untracked tables: ...` rather than `Untracked tables: ...`,
in name order rather than catalog order. Both are for the reader of a CI log,
where that list is the part that scrolls: shown from the tail a forty-table wall
reads as a handful of findings, and creation order is not what somebody scanning
for the table they just added is using. The sort lives in `Coverage#missing`
rather than at the point of display, and the count is spelled in the shared
example in `audit_log/rspec` as well, because that message is a second rendering
of the same finding and this class exists so the two cannot disagree about it.

The install template's `unaudited_tables` block gains commented examples for
Active Storage, Ahoy, PaperTrail's `versions` and the PostGIS reference tables.
They stay commented and they stay in the HOST's initializer rather than becoming
gem defaults, because the four defaults are tables no application could want
audited and these are not: `active_storage_attachments` records who attached
which file to which record, which is a real auditor question in a document-heavy
app, and a default exemption there means coverage never asks it again, silently,
in every adopting app. Hence the note beside that group -- three adjacent
commented lines invite uncommenting all three, and that one is a decision rather
than tidying up a red build.

`--exclude` is now documented as space-separated in the `audit_log:trigger`
options table. It is a Thor `type: :array`, so `--exclude=a,b` arrives as a
single column name `a,b`, matches nothing, and leaves both columns in the diff
while the generator reports success.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: ksouthworth

CHANGELOG.md

@@ -5,6 +5,42 @@ versioning follows [SemVer](https://semver.org/spec/v2.0.0.html).
 
 ## Unreleased
 
+## 0.5.2 — 2026-09-09
+
+Documentation and reporting only. No behaviour change to either capture layer.
+
+### Changed
+
+- **`audit_log:coverage` leads its finding with a count, and sorts the tables.**
+  `23 untracked tables: ...` rather than `Untracked tables: ...`, alphabetically
+  rather than in catalog order. Both are for the reader of a CI log, where that
+  list is the part that scrolls: shown from the tail, a forty-table wall reads as
+  a handful of findings, and creation order is not what somebody scanning for the
+  table they just added is using.
+
+  The sort is in `AuditLog::Coverage#missing`, so the rake task, the
+  capture-disabled report and any host calling `missing` directly share it. The
+  count is spelled in the shared example in `audit_log/rspec` too — that message
+  is a second rendering of the same finding, and this class exists so the two
+  cannot disagree.
+
+- **The install template's `unaudited_tables` block carries commented examples**
+  for Active Storage, Ahoy, PaperTrail's `versions` and the PostGIS reference
+  tables (`us_lex`, `us_gaz`, `us_rules`, `spatial_ref_sys`).
+
+  They stay commented, and they stay in the host's initializer rather than
+  becoming gem defaults. The four defaults are tables no application could want
+  audited; `active_storage_attachments` records who attached which file to which
+  record, which is a real auditor question in a document-heavy app, and a default
+  exemption would mean coverage never asks it again — silently, in every adopting
+  app. That is the one thing the forcing function exists to prevent, so the group
+  carries a note saying so.
+
+- **`--exclude` is documented as space-separated** in the `audit_log:trigger`
+  options table. It is a Thor `type: :array`, so `--exclude=a,b` arrives as one
+  column name `a,b`, matches nothing, and leaves both columns in the diff while
+  the generator reports success.
+
 ## 0.5.1 — 2026-09-01
 
 ### Changed

README.md

@@ -219,7 +219,7 @@ command, and the reasoning for any of it is linked rather than inline.
 
 ```ruby
 # Gemfile
-gem "audit_log", git: "https://github.com/web-ascender/audit-log", tag: "v0.5.1"
+gem "audit_log", git: "https://github.com/web-ascender/audit-log", tag: "v0.5.2"
 ```
 
 A private repo, so `bundle` needs credentials for the company GitHub org. Pin to

lib/audit_log/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module AuditLog
-  VERSION = "0.5.1"
+  VERSION = "0.5.2"
 end