[sunilp]

Corrects README claims that do not match the 0.4.0 code. Each item with its evidence:

Claim removed or changed	Evidence
jamjet-spring-boot-starter:0.1.0-SNAPSHOT	The module's artifactId is jamjet-runtime-spring-boot-starter (jamjet-spring-boot-starter/pom.xml). Maven Central metadata lists 0.1.1, 0.2.0, 0.3.1, 0.4.0 for it and only 0.1.0 for the old name. Now dev.jamjet:jamjet-runtime-spring-boot-starter:0.4.0.
jamjet-runtime-instrument:0.1.0-SNAPSHOT	Published release is 0.4.0 (maven-metadata.xml).
Cloud SDK and cloud starter at 0.2.0	Both are at 0.4.0 in the reactor and on Maven Central.
"Any storage backend (H2, Postgres, SQLite)"	JamjetAutoConfiguration.stateBackend accepts only in-memory and warns and falls back otherwise. JamjetServer.createBackend throws on anything else. JdbcStateBackend exists in core (H2/PostgreSQL per its javadoc) but neither the starter nor the server uses it. No SQLite code exists.
"Kill the process, restart, resume. Zero code changes"	DurabilityContext is a thread-local with an in-memory LinkedHashMap. The crash-recovery example writes its own checkpoint file. README now says so.
"1M concurrent agents"	No benchmark or code backs it. Replaced with the verifiable fact that WorkerPool uses a virtual-thread-per-task executor.
Comparison table against Spring AI, LangChain4j, Koog, ADK	Competitor claims are not verifiable from this repo. Table removed.
Server "same API surface as the Rust runtime"	Not checked against the Rust runtime. Replaced with "in-memory storage only".
Module table missing jamjet-agent and jamjet-agent-spring-boot-starter	Both are modules in the root pom and published at 0.4.0. Added.
examples/spring-boot-comparison dependency row	Same wrong artifact and SNAPSHOT version. Fixed.

Example poms (second commit): crash-recovery, latency-comparison and real-agent moved from 0.1.0-SNAPSHOT to 0.4.0. spring-boot-comparison/new-way moved from starter 0.1.0 (not on Central) to 0.4.0. Each of these four compiles against Central with a clean local repo (mvn compile). spring-boot-comparison/old-way pinned jamjet-spring-boot-autoconfigure:0.1.2, which does not exist on Central (only 0.1.0 does); it now pins 0.1.0, but it still does not compile because its code calls a sidecar client API that 0.1.0 does not have. It is a reference-only project and I left the code as is.

Module READMEs checked: jamjet-agent-spring-boot-starter (0.4.0, no issues), other examples have no coordinate or backend claims beyond the one fixed. Note: several example pom.xml files still pin 0.1.0-SNAPSHOT; not changed here since this PR is README-only.

No CI workflow runs on docs-only changes if path filters apply; status noted below once checked.

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 16d0c27d-4d69-4e25-a43f-eefdc51a46d6

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}