Integrate integration/worker-restore without reviving removed Worker socket/discovery paths. Keep restore candidate allocation and canonical effects deferred until activation, with registry reclamation and observer publication fences on the in-process controller. Preserve develop BackendJob/provenance, immutable Journal body capture and erasure, and Workdir diagnostics. Adapt obsolete socket fault tests to in-process publication and registry drift boundaries. Validation: root cargo check; ordinary worker, worker-runtime and standalone package tests; Server restore (43) and Journal (49) filters; mcp/server-api/runtime-api/session-store tests; optional Runtime feature check; OpenAPI and six generated TypeScript checks; Web restore unit tests (15); runner tests (21); fmt, naming and diff checks. Full workspace/Server suites, E2E, live/model and fixture generation not run.
session-store
session-store stores replayable Session history and current Worker restoration data.
Session history uses append-only JSONL; current Segment references and child/peer
registrations live separately in Worker metadata. It does not own process liveness
checks or Runtime catalog lifecycle management.
Design entry points
- [
segment_log] / [segment]: history replay and fork/compaction lineage - [
worker_session_store]: storage boundary for a Session bound to a Worker - [
worker_metadata]: current Worker state and active Segment switching - [
system_item]: records of system input presented to the model - [
capture]: Worker-independent immutable public values and bounded body transport; authorization, source I/O, and delivery lifecycle stay with the Host - [
public_snapshot] / [public_index]: public projections of stored history - [
event_trace]: diagnostic records independent of history replay