The run named the output directory and, sometimes, the map. It never mentioned
digest.md, digest.json or aliases.local.json — so the three facts the workflow
actually depends on were left to be discovered by browsing the folder:

  background-geolocation-car.log.gz: 6729 records, 2 segment(s), 4 unknown (0.1%)
    → loganalyzer-out/background-geolocation-car.log/
        digest.md            redacted — safe to share
        digest.json          full precision
        map.html             full precision — opened
        aliases.local.json   full precision — un-redacts digest.md
    opened 1 map tab(s)

The point of this tool is that a customer sends back digest.md and nothing else.
That only works if the output says which file that is, and says plainly that
aliases.local.json travelling alongside it would undo the redaction. The
annotations adapt: no map.html line under --no-map, locations.geojson appears
under --locations, and "opened" only when a tab was actually opened.

Tested by writing all five artifacts and asserting every one is named, that the
two load-bearing phrases appear, and that nothing full-precision is ever
described as shareable.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>