Maven

kami/Maven

Files

T

claude 4d97280d74 a turn hands back its trace id, and one wire op corrects it (V-630)

The correction is the only supervised signal in the box, so the cost of
giving one has to be near zero. That means the surface needs the trace id of
the turn it is showing, which it had no way to learn: handleText returns one
string and the trace was written after the reply left.

The id rides back on ChatReply through the same context sink querySource
uses, so the mic, telegram and the web keep the one signature they share.
CorrectTurn takes a trace id and an optional target, which is deliberately
reach-agnostic: nothing about it assumes a browser.

store.ErrNoSuchTrace gets a wire twin. A turn past the retention bound is
gone, and that is the expected outcome of correcting an old turn, not a
broken database.

2026-08-06 19:45:37 +04:00

api.go

a turn hands back its trace id, and one wire op corrects it (V-630)

2026-08-06 19:45:37 +04:00

capture_test.go

Add meeting capture with explicit start and stop (#253 )

2026-08-01 05:08:08 +04:00

client.go

a turn hands back its trace id, and one wire op corrects it (V-630)

2026-08-06 19:45:37 +04:00

coreapi.go

a turn hands back its trace id, and one wire op corrects it (V-630)