Tags: stacktale/stacktale

stacktale 1.4.0

stacktale 1.3.1

stacktale 1.3.0

stacktale 1.2.0

stacktale 1.1.0

A failing test finally produces a report (stacktale-junit), the console
line points at a file you can open, the culprit is a frame you wrote, and
the report id survives you editing the source — which is what the MCP
fix-loop needs to tell 'still broken' from 'new error'.

stacktale 1.0.0

stacktale 0.5.0

stacktale 0.4.0 — storm control, MCP push, agent privacy mode, compat…

… matrix

stacktale 0.3.1 — critical agent startup fix + audit-3 hardening

stacktale 0.3.0 — throw-site capture agent, MCP server, reactive stories