Improve strict sync-eval caching and harden primitive semantics

- fix strict cache root eviction so cached graphs do not accumulate after LRU eviction
- harden strict sync-eval caching with loader/env reuse and cache/overlay cleanup
- extract cache and overlay machinery into a dedicated module to simplify runtime structure
- broaden sync predicate and digest primitive behavior for byte-vectors and refresh help text
- add focused primitive integration tests and update the package version to 1.1.3

Author: thiennamdinh

.github/workflows/all.yml

@@ -15,14 +15,16 @@ jobs:
     runs-on: ubuntu-latest
     permissions: write-all
     steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
       - name: Install dependencies
         run: |
           sudo apt update
           sudo apt install -y llvm-dev libclang-dev clang
       - name: Install rust
         uses: moonrepo/setup-rust@v1
-      - name: Checkout code
-        uses: actions/checkout@v4
+      - name: Cache Rust build artifacts
+        uses: Swatinem/rust-cache@v2
       - name: Build project
         run: cargo build
       - name: Test project
@@ -65,6 +67,8 @@ jobs:
           push: false
           load: false
           tags: ghcr.io/${{ github.repository }}/journal-sdk:ci
+          cache-from: type=gha,scope=journal-sdk-docker
+          cache-to: type=gha,mode=max,scope=journal-sdk-docker
       - name: Build and push multi-arch Docker images
         if: github.ref == 'refs/heads/main'
         uses: docker/build-push-action@v6
@@ -77,3 +81,5 @@ jobs:
             ghcr.io/${{ github.repository }}/journal-sdk:${{ steps.version.outputs.value }}
           labels: |
             org.opencontainers.image.source=https://github.com/${{ github.repository }}
+          cache-from: type=gha,scope=journal-sdk-docker
+          cache-to: type=gha,mode=max,scope=journal-sdk-docker

CHANGELOG

@@ -2,6 +2,14 @@
 The purpose of this changelog is to document new features and breaking changes that are most likely to affect developers
 ------------------------------------------------------------------------------------------------------------------------
 
+--- v1.2.0 (2026.03.29) ---
+
+- Fix strict sync-eval cache root eviction so cached graphs do not accumulate after LRU eviction
+- Reuse strict sync-eval state more efficiently and split cache/overlay code into a dedicated module
+- Allow `sync-null?`, `sync-pair?`, `sync-stub?`, and `sync-digest` to operate cleanly on byte-vectors
+- Add primitive integration sanity tests and refresh primitive help text
+- Remove stale profiling/debug instrumentation after validating cache behavior
+
 --- v1.1.0 (2026.03.08) ---
 
 - Add `system-time-utc` and `system-time-unix` primitives for UTC/unix conversion

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "journal-sdk"
-version = "1.1.2"
+version = "1.2.0"
 edition = "2024"
 
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
@@ -28,6 +28,7 @@ sha2 = "0.10.8"
 libc = "0.2"
 log = "0.4.21"
 env_logger = "0.10"
+lru = "0.12.5"
 crystals-dilithium = "1.0.0"
 pqcrypto = "0.17.0"
 tokio = { version = "1.0", features = ["time", "rt", "rt-multi-thread", "macros"] }

Dockerfile

@@ -1,6 +1,8 @@
-# --- Build ---
+# syntax=docker/dockerfile:1.7
 
-FROM alpine:3.23.3 AS builder
+# --- Build base ---
+
+FROM alpine:3.23.3 AS chef
 
 ARG RUST_LOG=info
 ARG CUSTOM_SETUP=""
@@ -17,19 +19,50 @@ RUN set -eu; \
       rm -f /tmp/custom-setup.sh; \
     fi
 
-# Install OS dependencies
-RUN apk update
-RUN apk add cargo
-RUN apk add clang
-RUN apk add clang-dev
-RUN apk add openssl-dev
-RUN apk add build-base
-RUN apk add linux-headers
+RUN apk update && apk add --no-cache \
+    build-base \
+    cargo \
+    clang \
+    clang-dev \
+    linux-headers \
+    openssl-dev
+
+RUN --mount=type=cache,target=/root/.cargo/registry \
+    --mount=type=cache,target=/root/.cargo/git \
+    cargo install cargo-chef --locked
 
-# Build SDK
 WORKDIR /srv
-COPY . . 
-RUN cargo build --release
+
+# --- Dependency planning ---
+
+FROM chef AS planner
+
+COPY . .
+
+RUN cargo chef prepare --recipe-path recipe.json
+
+# --- Dependency build ---
+
+FROM chef AS cacher
+
+COPY --from=planner /srv/recipe.json recipe.json
+
+RUN --mount=type=cache,target=/root/.cargo/registry \
+    --mount=type=cache,target=/root/.cargo/git \
+    --mount=type=cache,target=/srv/target \
+    cargo chef cook --release --recipe-path recipe.json
+
+# --- Application build ---
+
+FROM chef AS builder
+
+COPY . .
+
+RUN --mount=type=cache,target=/root/.cargo/registry \
+    --mount=type=cache,target=/root/.cargo/git \
+    --mount=type=cache,target=/srv/target \
+    cargo build --release && \
+    cp /srv/target/release/journal-sdk /tmp/journal-sdk
 
 # --- Deploy ---
 
@@ -48,7 +81,7 @@ RUN set -eu; \
 
 COPY --from=builder /usr/lib/libgcc_s.so.1 /usr/lib/
 COPY --from=builder /usr/lib/libstdc++.so.6* /usr/lib/
-COPY --from=builder /srv/target/release/journal-sdk .
+COPY --from=builder /tmp/journal-sdk ./journal-sdk
 
 ENTRYPOINT ["./journal-sdk"]
 

README.md

@@ -90,13 +90,14 @@ There is only one structural constraint on the form of the record: for a record
 
 `(lambda (*sync-state* query) (cons ... *sync-state*))`
 
-The `*sync-state*` parameter is the root node of the record while the `query` parameter is the expression provided through the `/interface` endpoint.
-The function returns a Scheme pair where the first item is the response to the `/inferface` call and the second item is the new root node.
+At request time, the journal supplies the current record root as the `*sync-state*` argument and also exposes `(sync-state)` as a primitive that returns the current session root as a `sync-node`.
+The `query` parameter is the expression provided through the `/interface` endpoint.
+The function returns a Scheme pair where the first item is the response to the `/interface` call and the second item is the new root node.
 For example, the default function is the following:
 
 `(lambda (*sync-state* query) (cons (eval query) *sync-state*))`
 
-This function simply evaluates any user query.
+This function simply evaluates any user query against the current state binding.
 From this highly generic and permissive functionality, it is possible to construct arbitrarily specific and controlled interfaces.
 The [./lisp](./lisp) folder provides some examples.