Merge pull request #20 from iscc/develop

Release 0.0.4

Author: titusz

.claude/agent-memory/update-state/MEMORY.md

@@ -43,8 +43,8 @@ Codepaths, patterns, and key findings accumulated across CID iterations.
 - `crates/iscc-jni/java/src/main/java/io/iscc/iscc_lib/IsccLib.java` — Java class (subpath:
     `iscc_lib/`); has META_TRIM_META as `public static final int`
 - `crates/iscc-ffi/src/lib.rs` line 3 — module docstring says "10 `gen_*_v0` functions"
-- `crates/iscc-lib/benches/benchmarks.rs` — 237 lines; docstring says "9 gen\_\*\_v0" (stale);
-    missing `bench_sum_code` function; `criterion_group!` lists 11 benches (no bench_sum_code)
+- `crates/iscc-lib/benches/benchmarks.rs` — 277 lines; docstring says "all 10 gen\_\*\_v0"; has
+    `bench_sum_code` (64KB+1MB using NamedTempFile); `criterion_group!` lists 12 benches
 
 ## Recurring Patterns
 
@@ -59,17 +59,14 @@ Codepaths, patterns, and key findings accumulated across CID iterations.
 - **Target may change**: always re-read target.md diff when doing incremental review; symbol counts
     and spec requirements can increase
 
-## Current State (assessed-at: 580793c)
+## Current State (assessed-at: 6cfae5e)
 
-- **Target**: 32 Tier 1 symbols — all 7 bindings COMPLETE ✅; README ✅; Per-crate READMEs ✅;
-    Documentation ✅
-- **Iteration 15**: Howto guides (PASS) — all 6 howto guides now have `### Sum-Code` subsections
-    with working code examples; `uv run zensical build` verified ✅
-- **Remaining gap**: Benchmarks partially met — `gen_sum_code_v0` has no criterion benchmark;
-    `benchmarks.rs` docstring says "9 gen\_\*\_v0" (stale). Target requires benchmarks for all 10.
-- **Issues**: Only #16 remains (feature flags for minimal builds, low priority)
+- **TARGET DONE**: All target.md criteria met ✅; CI 11/11 SUCCESS ✅
+- **Iteration 16**: bench_sum_code (PASS) — added 10th criterion benchmark for gen_sum_code_v0;
+    `benchmarks.rs` docstring updated to "all 10"; `tempfile` crate added as workspace dev-dep
+- **Issues**: Only #16 remains (feature flags for minimal builds, low priority, GitHub issue filed)
 - **v0.0.3 released**: tags `v0.0.3` and `packages/go/v0.0.3`; all registries
-- **CI latest**: Run 22559996288 — all 11 CI jobs SUCCESS
+- **CI latest**: Run 22560748212 — all 11 CI jobs SUCCESS
 
 ## Go Package Tier 1 Coverage (32/32 — COMPLETE)
 
@@ -100,6 +97,6 @@ constants** (MetaTrimName, MetaTrimDescription, MetaTrimMeta, IoReadSize, TextNg
     pattern precisely; partial allocation failure handled (free iscc before returning null)
 - **9 vs 10 distinction**: data.json has 9 conformance sections (no gen_sum_code_v0 vectors);
     iscc-lib has 10 gen functions. Test/conformance docstrings correctly say "9"; user-facing docs
-    say "10". Benchmarks file is stale at "9"
-- **gen_sum_code_v0 benchmark**: uses file I/O (not in-memory) — needs temp files with 64KB/1MB
-    payloads; follow `bench_data_code` pattern but use `tempfile` crate or `env::temp_dir()`
+    and benchmarks file say "10"
+- **gen_sum_code_v0 benchmark**: uses NamedTempFile (tempfile crate); temp files created outside
+    criterion closure so file setup is not measured; cleanup via Drop

.claude/context/state.md

@@ -1,16 +1,16 @@
-<!-- assessed-at: 580793c -->
+<!-- assessed-at: 6cfae5e458a67a4146431cd651d8636f7bb3b2fc -->
 
 # Project State
 
-## Status: IN_PROGRESS
+## Status: DONE
 
-## Phase: Documentation complete; gen_sum_code_v0 benchmark missing
+## Phase: All target criteria met; CI green
 
-Iteration 15 completed the final documentation gap: all 6 per-language howto guides now have a
-`### Sum-Code` subsection with working code examples for `gen_sum_code_v0`. CI remains all-green
-(11/11 jobs SUCCESS). The only remaining target gap is that `crates/iscc-lib/benches/benchmarks.rs`
-still says "9 gen\_\*\_v0" and has no `bench_sum_code` criterion function — the target requires
-criterion benchmarks for all Rust `gen_*_v0` functions, and there are now 10.
+All sections of `target.md` are fully satisfied. The `bench_sum_code` criterion benchmark added in
+iteration 16 completed the final gap — all 10 `gen_*_v0` functions now have Rust criterion
+benchmarks. CI is all green (11/11 jobs SUCCESS). The only open item is issue #16 (feature flags for
+minimal builds), which is low priority, has a GitHub issue filed, and is **not** part of the
+`target.md` acceptance criteria.
 
 ## Rust Core Crate
 
@@ -118,47 +118,45 @@ criterion benchmarks for all Rust `gen_*_v0` functions, and there are now 10.
 - `docs/c-ffi-api.md` has `iscc_gen_sum_code_v0` + `IsccSumCodeResult` struct documented ✅
 - `docs/index.md` lists `gen_sum_code_v0` in function table ✅
 - `docs/architecture.md` references `gen_sum_code_v0` ✅
-- All 6 howto guides now have `### Sum-Code` subsections with working code examples ✅
-    - `docs/howto/rust.md` — `gen_sum_code_v0(Path::new(...))` ✅
-    - `docs/howto/python.md` — `gen_sum_code_v0("example.bin")` ✅
-    - `docs/howto/nodejs.md` — `gen_sum_code_v0("example.bin")` ✅
-    - `docs/howto/wasm.md` — `gen_sum_code_v0(data)` (Uint8Array, no path) ✅
-    - `docs/howto/java.md` — `IsccLib.genSumCodeV0("example.bin", 64, false)` ✅
-    - `docs/howto/go.md` — `iscc.GenSumCodeV0("example.bin", 64, false)` ✅
-- `uv run zensical build` exits 0 (verified by review agent) ✅
+- All 6 howto guides have `### Sum-Code` subsections with working code examples ✅
+- `uv run zensical build` exits 0 ✅
 
 ## Benchmarks
 
-**Status**: partially met
+**Status**: met
 
-- Criterion benchmarks exist for the original 9 `gen_*_v0` functions + `bench_data_hasher_streaming`
-    - `bench_cdc_chunks` (4KB/64KB/1MB)
-- pytest-benchmark comparison: `benchmarks/python/bench_iscc_core.py` and `bench_iscc_lib.py`
-- Speedup factors published in `docs/benchmarks.md`
-- `Bench (compile check)` CI job verifies all benchmark targets compile
-- **MISSING**: `crates/iscc-lib/benches/benchmarks.rs` file docstring says "9 gen\_\*\_v0 ISCC
-    functions" (stale) and has no `bench_sum_code` criterion function. Target requires criterion
-    benchmarks for all Rust `gen_*_v0` functions; there are now 10.
+- Criterion benchmarks exist for all 10 `gen_*_v0` functions:
+    - `bench_meta_code`, `bench_text_code`, `bench_image_code`, `bench_audio_code`,
+        `bench_video_code`, `bench_mixed_code`, `bench_data_code`, `bench_instance_code`,
+        `bench_iscc_code`, `bench_sum_code` (64KB + 1MB throughput using `NamedTempFile`) ✅
+- File docstring updated to "all 10 `gen_*_v0` ISCC functions" ✅
+- `bench_data_hasher_streaming` + `bench_cdc_chunks` additional benchmarks ✅
+- pytest-benchmark comparison: `benchmarks/python/bench_iscc_core.py` and `bench_iscc_lib.py` ✅
+- Speedup factors published in `docs/benchmarks.md` ✅
+- `Bench (compile check)` CI job passes ✅
 
 ## CI/CD and Publishing
 
 **Status**: met
 
 - **All 11 CI jobs SUCCESS** on latest push; latest CI run: **PASSING** ✅
-- URL: https://github.com/iscc/iscc-lib/actions/runs/22559996288
+- URL: https://github.com/iscc/iscc-lib/actions/runs/22560748212
 - Jobs: Version consistency, Rust (fmt, clippy, test), Python 3.10 (ruff, pytest), Python 3.14
     (ruff, pytest), Python (ruff, pytest), Node.js (napi build, test), WASM (wasm-pack test), C FFI
     (cbindgen, gcc, test), Java (JNI build, mvn test), Go (go test, go vet), Bench (compile check) —
     all success ✅
 - v0.0.3 released to all registries; OIDC trusted publishing for crates.io; Maven Central GPG
-    configured; npm via NPM_TOKEN
+    configured; npm via `NPM_TOKEN`
 
 ## Next Milestone
 
-**Add `bench_sum_code` criterion benchmark for `gen_sum_code_v0`:**
+**Target fully met.** All `target.md` acceptance criteria are satisfied and CI is green.
+
+The only remaining tracked item is **issue #16** — feature flags for embedded/minimal builds (low
+priority, GitHub issue filed at https://github.com/iscc/iscc-lib/issues/16). This is an enhancement
+outside the current target scope. The CID loop may either:
+
+1. Implement issue #16 as a low-priority follow-on
+2. Declare target completion and stop the loop
 
-`crates/iscc-lib/benches/benchmarks.rs` has benchmarks for 9 `gen_*_v0` functions but not the tenth
-(`gen_sum_code_v0`). The target requires criterion benchmarks for all Rust `gen_*_v0` functions. Add
-a `bench_sum_code` function (using a temp file with 64KB and 1MB payloads, matching the pattern from
-`bench_data_code`) and register it in `criterion_group!`. Also update the file docstring from "9" to
-"10". After that, only issue #16 (feature flags for minimal builds, low priority) remains.
+No blocking work remains.

Cargo.lock

@@ -10,7 +10,7 @@ members = [
 ]
 
 [workspace.package]
-version = "0.0.3"
+version = "0.0.4"
 edition = "2024"
 rust-version = "1.85"
 authors = ["Titusz Pan <tp@py7.de>"]

Cargo.toml

@@ -98,7 +98,7 @@ npm install @iscc/lib
 <dependency>
   <groupId>io.iscc</groupId>
   <artifactId>iscc-lib</artifactId>
-  <version>0.0.3</version>
+  <version>0.0.4</version>
 </dependency>
 ```
 

README.md

@@ -22,7 +22,7 @@ to create a composite identifier that exhibits similarity-preserving properties
 <dependency>
   <groupId>io.iscc</groupId>
   <artifactId>iscc-lib</artifactId>
-  <version>0.0.3</version>
+  <version>0.0.4</version>
 </dependency>
 ```
 

crates/iscc-jni/README.md

@@ -6,7 +6,7 @@
 
     <groupId>io.iscc</groupId>
     <artifactId>iscc-lib</artifactId>
-    <version>0.0.3</version>
+    <version>0.0.4</version>
     <packaging>jar</packaging>
 
     <name>iscc-lib</name>

crates/iscc-jni/java/pom.xml

@@ -1,6 +1,6 @@
 {
   "name": "@iscc/lib",
-  "version": "0.0.3",
+  "version": "0.0.4",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",

crates/iscc-napi/package.json

@@ -20,7 +20,7 @@ Add the Maven dependency to your `pom.xml`:
 <dependency>
   <groupId>io.iscc</groupId>
   <artifactId>iscc-lib</artifactId>
-  <version>0.0.3</version>
+  <version>0.0.4</version>
 </dependency>
 ```
 

docs/howto/java.md

@@ -17,14 +17,14 @@ static methods on the `IsccLib` class. The native library is loaded automaticall
     <dependency>
       <groupId>io.iscc</groupId>
       <artifactId>iscc-lib</artifactId>
-      <version>0.0.3</version>
+      <version>0.0.4</version>
     </dependency>
     ```
 
 === "Gradle"
 
     ```groovy
-    implementation 'io.iscc:iscc-lib:0.0.3'
+    implementation 'io.iscc:iscc-lib:0.0.4'
     ```
 
 ## Quick Example