Give conversation runs the intent journal via JournalOnly sessions (N3 WP2)

Browse Source

Why: the product conversation path had zero mid-turn durability
(llm_direct ran without Session — intents, recovery pairing, and
side-effect replay semantics never applied). Transcript-as-authority
would have frozen the assembled prefix, so the journal is wired in
JournalOnly mode: recovery runs against the transcript, the context
stays on the ctxasm pipeline, and recovered outcomes inject as a
system note.
Evidence: go test -count=1 ./... green;
TestDirectRunPairsAfterKillSeed (crash-window transcript gets the
crashInterrupted pair, run proceeds) and
TestDirectRunSeedsStoreHistoryOnce (history appears exactly once in
every request, never enters the journal); the forged-marker and
harness suites pass unchanged.
Impact: conversation runs now journal tool intents and recover them on
the next run; no transparent resume (sealed interrupted stays; the
user keeps chatting). Opening the transcript fails soft (falls back to
the old no-session behavior).
Refs: Agent-Native#31, Agent-Squad#35, N3 plan WP2

...

This commit is contained in:

weichen

2026-10-07 15:26:27 +00:00

parent 7a6a6075c2

commit 9f3fdb26e2

5 changed files with 153 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

deps/agent-native

Vendored

+1 -1

Submodule deps/agent-native updated: cb21ec4e2a...79e1a8fa85

deps/agent-squad

Vendored

+1 -1

Submodule deps/agent-squad updated: 931e5ae410...90077b6601