xiaoju 1e9900bed3 feat(#194): Phase 2 — Engine layer Merkle call stack wiring ...

- Protocol: AgentFnResult = string | { output, childThread }, RoleOutput.childThread,
  ThreadContext.bundleHash for parent state lookup
- Runtime: create-workflow normalizes AgentFnResult, propagates childThread in RoleOutput
- Engine: ExecuteThreadOptions.parentStateHash, appendStateForStep writes childThread,
  putStartNode uses parentStateHash
- workflowAsAgent: reads parent head state from threads.json, passes parentStateHash
  to child, returns { output, childThread: rootHash }
- Integration test: 4 cases verifying bidirectional Merkle links (306 lines)

Phase 2 of #194 (Merkle Call Stack). Closes #196.

小橘 <xiaoju@shazhou.work>

2026-05-12 02:10:06 +00:00

..

engine.test.ts

feat(#194): Phase 2 — Engine layer Merkle call stack wiring

2026-05-12 02:10:06 +00:00

extract-refs.test.ts

refactor: simplify ExtractFn to (schema, contentHash)

2026-05-11 07:54:09 +00:00

gc-mark-sweep.test.ts

feat(#194): Phase 1 — parentState / childThread in CAS nodes

2026-05-12 01:42:10 +00:00

merkle-call-stack.test.ts

feat(#194): Phase 2 — Engine layer Merkle call stack wiring

2026-05-12 02:10:06 +00:00

threads-index.test.ts

feat: Phase 2 — engine write path (CAS nodes + threads.json)

2026-05-09 07:53:44 +00:00