dcdpr / jp / 24186717595

67%

Build Type

push

github

Committed by web-flow

Commit Message

enhance(cli, conversation): Improve `conversation print` replay fidelity (#527)

`jp conversation print` now produces output that more faithfully
represents what was displayed during the original query session.

Custom tool argument formatters (`ParametersStyle::Custom`) previously
produced no output during replay, because their rendered content was
never persisted — it was only computed at execution time and discarded.
The formatter output is now captured and stored in event metadata
(base64-encoded under the `rendered_arguments` key) when a tool is
approved. `jp conversation print` reads this stored content and
re-renders it, so the custom display appears in replay exactly as it did
when the tool ran.

Typewriter delays are disabled for replay. Content that streams token by
token during a live query is printed instantly when replaying with `jp
conversation print`, which is the expected behaviour for reading back a
recorded conversation.

By default, each turn is now rendered using the configuration that was
active when it was created (reconstructed from the per-turn
`PartialAppConfig` stored in the event stream). A new `--current-config`
flag overrides this and applies the current workspace configuration to
all turns instead:

```
jp conversation print --current-config
```

The rendering logic is also unified into a shared `render` module
(`ChatRenderer`, `StructuredRenderer`, `ToolRenderer`, `TurnRenderer`),
used by both the live query stream and conversation replay.

---------

Signed-off-by: Jean Mertz <git@jeanmertz.com>

Coverage Stats

248 of 319 new or added lines in 11 files covered. (77.74%)

7 existing lines in 4 files now uncovered.

20303 of 31514 relevant lines covered (64.43%)

395.56 hits per line