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

..

cas.ts

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

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

collect-refs.ts

wip: Phase 1 protocol + CAS types for Merkle call stack

2026-05-12 01:35:45 +00:00

hash.ts

feat: Phase 3 — engine read path + runtime context builder

2026-05-09 08:00:24 +00:00

index.ts

feat: Phase 3 — engine read path + runtime context builder

2026-05-09 08:00:24 +00:00

merkle.ts

fix: content node refs field + thread head update

2026-05-09 08:53:02 +00:00

nodes.ts

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

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

reachable.ts

fix: content node refs field + thread head update

2026-05-09 08:53:02 +00:00

types.ts

feat(cas,reactor): create @uncaged/workflow-cas and @uncaged/workflow-reactor

2026-05-09 11:11:33 +08:00