Levi Neely 3d9eca97b2 fix: close streaming fence before ending block on call/default events ... The event handler was emitting [[[end]]] to close an assistant block without first closing an open streaming fence (code block). This left the log in a state where a [[[call:...]]] block appeared nested inside an unclosed assistant block, triggering a log structure violation. Now the call and default cases close streamingFence (like the tool case already did) before writing the [[[end]]] marker.		2026-08-07 09:05:39 +02:00
..
cache.go	fs: restructure package into logical files	2026-08-04 11:27:28 +02:00
ctl.go	refactor: extract format package, ctl dispatcher, and log structure validator	2026-08-07 08:59:07 +02:00
handlers.go	refactor: extract format package, ctl dispatcher, and log structure validator	2026-08-07 08:59:07 +02:00
lifecycle.go	refactor: eliminate Manager type, use package-level session registry	2026-08-04 13:55:45 +02:00
log_validator.go	refactor: extract format package, ctl dispatcher, and log structure validator	2026-08-07 08:59:07 +02:00
log_validator_test.go	refactor: extract format package, ctl dispatcher, and log structure validator	2026-08-07 08:59:07 +02:00
newroot.go	fsedsl: HandlerCtx composes context.Context — no more context.Background() in handlers	2026-08-07 07:42:41 +02:00
spec.go	namespace audit: remove prompt.prev, state, offset, context, tail	2026-08-07 08:19:54 +02:00
types.go	fix: close streaming fence before ending block on call/default events	2026-08-07 09:05:39 +02:00