Hubert Gancarczyk 838cbc5706 feat(cli): failure block, step timings and a JUnit reporter for argent flow ...

The terminal block is a slot system, not a template: code + message is
mandatory and the rest (context window, expected/actual, candidates,
screen, reads, artifact paths) appears only when it applies, which is
what lets one renderer serve six very different failures. Step lines
gain a duration only when the server sent one, so a pre-timing
tool-server renders byte-identically.

--reporter junit:<path> maps each STEP to a testcase, because per-failure
attribution in the checks UI is the entire value of JUnit in CI. A
report-file write failure warns and leaves the verdict alone - failing a
build on argent's own I/O would make the reporter a source of flake.

Everything the renderers read is clamped first: the failure object can
arrive from a remote argent link server.

2026-08-24 11:00:35 +02:00

..

src

feat(cli): failure block, step timings and a JUnit reporter for argent flow

2026-08-24 11:00:35 +02:00

test

test: stop tests binding machine-wide resources they do not own (#714)

2026-08-19 23:06:48 +02:00

package.json

chore: bump version to 0.22.0 (#891)

2026-08-21 19:33:57 +02:00

tsconfig.json

feat(telemetry): derive distinct_id from a stable host fingerprint (#444)

2026-07-07 16:28:29 +02:00

tsconfig.test.json

feat: add telemetry (#274)

2026-06-19 18:22:34 +02:00

vitest.config.ts

feat: add telemetry (#274)

2026-06-19 18:22:34 +02:00