The documented one-liner did not work. `uvx <pkg>` looks for a console script
whose name equals the package name; ours were `transistorsoft-loganalyzer` and
`loganalyzer`, so it failed with "The executable
`transistorsoft-loganalyzer` was not found".

Nothing local could have caught it. Locally you always invoke `loganalyzer`
directly, and the wheel installed and ran correctly the whole time — the defect
lived entirely in the gap between the distribution name and the script name,
which only appears when resolving from a registry. Publishing 0.1.0 was the test.

So the package now installs both names as aliases of the same entry point, and
the README shows all three forms: the `uvx <pkg>` shorthand, the explicit
`uvx --from … loganalyzer` (what you want when pinning a version), and
`uv tool install`, which puts plain `loganalyzer` on PATH.

Verified against a clean venv built from the 0.1.1 wheel: both console scripts
present in entry_points.txt, both analyze a real capture identically.

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