gavrielc 102ce80fda Fix a2a in_reply_to stamp: publish through outbound.db, not module state ...

The active batch's inReplyTo lived in module-level state in current-batch.ts,
but the nanoclaw MCP server runs as a separate stdio subprocess from the poll
loop, so getCurrentInReplyTo() always read null there. The a2a reply stamp was
therefore dead — only the host peer-affinity fallback kept replies routing.

Publish the stamp through session_state in outbound.db (both processes already
open it): the poll loop writes it at batch start and clears it in the existing
finally; the MCP tools read it with an updated_at staleness guard so a stamp
left behind by a killed container isn't reused. Delete current-batch.ts and
reseed core.test.ts via the DB so it reflects the real process boundary.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-04 16:07:49 +03:00

..

scripts

docs: add v1→v2 action-items analysis + SDK signal probe tool

2026-04-20 01:00:04 +03:00

src

Fix a2a in_reply_to stamp: publish through outbound.db, not module state

2026-07-04 16:07:49 +03:00

bun.lock

chore(container): bump claude-code, agent SDK to latest

2026-06-30 22:27:46 +03:00

package.json

chore(container): bump claude-code, agent SDK to latest

2026-06-30 22:27:46 +03:00

tsconfig.json

chore: delete v1 reference code

2026-04-18 14:23:47 +03:00