v1.5.0

What's changed

appmap-review: the compare is a command, not a shell script

The skill used to carry about 60 lines of bash for the compare. It pulled each revision's gold traces out of git, then ran appmap archive, appmap restore, and appmap compare, with comments about each CLI trap. On Windows the agent had to translate all of it to PowerShell. That is now one command:

node "${CLAUDE_SKILL_DIR}/assets/review.mjs" compare --base <rev> [--head <rev> | --fresh | --uncommitted]

It needs only git, Node, and the AppMap CLI. It prints how many traces changed, were added, and were removed, plus the SQL, API, and scanner-finding counts. It also prints where change-report.json and the diff diagrams are, and the git diff to run for the source side of the review.

Head	Flag
a commit	--head <rev> (default HEAD)
fresh recordings, before blessing	--fresh
baselines blessed but not committed	--uncommitted

• A first baseline, where the base has no gold traces, works. Every head trace shows as new.
• The workspace is <system temp>/appmap-review and is cleared on every run. --workspace DIR puts it elsewhere. The helper refuses to clear a non-empty directory it did not create.
• In a monorepo, pass --dir packages/<name>/gold_traces.

On a real project, the command produced the same change report and diff diagrams as the old shell recipe. It has tests, but it has not been run on Windows yet.

appmap-gold-traces

• The release flow's review step now says to run the review with --fresh.
• The engine also looks for the AppMap CLI at ~/.appmap/bin/appmap.exe on Windows.

Upgrading

Nothing to change in projects. Manifests and committed baselines stay valid.

Full changelog: v1.4.0...v1.5.0