chore(release): v0.11.0

[ajitpratap0]

Summary

Bump binary + plugin to v0.11.0 and update CHANGELOG, ROADMAP, README badge.

Highlights since v0.10.0

Added

• Async graph pipeline — Graphiti-style WAL queue + worker pool, fast-capture path (feat(async): Graphiti-style async graph pipeline — WAL queue, worker pool, fast capture path #114)
• Typed relationship labels, subgraph retrieval, graph-proximity ranking (9th recall factor), MAGE community detection (feat(graph): typed relationship labels, subgraph retrieval, graph-proximity ranking, MAGE community detection #113)
• Full-scale benchmark suite — accumulate mode, DMR, dataset loaders, CI eval job, comparison tool (feat(eval): full-scale benchmark suite — accumulate mode, DMR, dataset loaders, CI job, comparison tool #115)
• reembed command + zero-embedding health check (fix(store): add reembed command and zero-embedding health check #112)
• Schema validation in EnsureSchema — drops+recreates vector index on mismatch (fix(schema): validate vector index property in EnsureSchema, drop+recreate on mismatch #109)
• Plugin auto-wires OpenClaw gateway for LLM access (feat(plugin): auto-wire OpenClaw gateway for LLM access #105, feat(plugin): auto-wire OpenClaw gateway for LLM access #116)
• Store entity/fact extraction (enabled by default); fact-text embeddings
• recall --valid-before/--valid-after temporal filters; --format json, --limit (feat(recall): add --format json and --limit N flags #93)
• --dedup-threshold + min content-length guard (fix(store): add min content-length guard and --dedup-threshold flag #111)
• Next.js marketing site polish (fix(web): broken footer links, duplicate titles, hero H1 spacing #118)

Fixed

• Ranking quality + store-time dedup (fix(recall): improve ranking quality & add store-time dedup #102)
• Lucene char sanitization in text search (fix(graph): sanitize Lucene special chars in text_search.search_all query #101)
• LinkMemoryToEntity read-back race (fix(graph): eliminate read-back race in LinkMemoryToEntity; fix MockStore ErrNotFound wrapping #99)
• Real LLM ping in health check (fix(health): test LLM credentials with a real ping call #98)
• Plugin store() return distinguishes dedup-update from failure (fix(plugin): distinguish store dedup-update from failure in store() return #110)
• Web footer broken links, duplicate page titles, hero H1 spacing, npm audit CVEs (fix(web): broken footer links, duplicate titles, hero H1 spacing #118)

Changed

• internal/timeutil extracted

Files touched

• cmd/openclaw-cortex/main.go — version 0.10.0 → 0.11.0
• extensions/openclaw-plugin/{index.ts,package.json,package-lock.json} — version bump
• README.md — release badge
• CHANGELOG.md — new [0.11.0] section
• ROADMAP.md — move v0.11.0 to Current, shift planned to v0.12.0

Test plan

• go build ./...
• go test -short ./... — all green
• CI must be green before merge
• After merge: tag v0.11.0, push tag, create GitHub release from CHANGELOG section

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openclaw-cortex	Ready	Preview, Comment	Apr 7, 2026 9:15am

[claude]

Review: LGTM

This is a clean release-prep PR. Checked against CLAUDE.md conventions:

• Version sync (CLAUDE.md requirement): cmd/openclaw-cortex/main.go and extensions/openclaw-plugin/index.ts both bumped to 0.11.0 — in sync. ✓
• No code logic changes — only version strings, CHANGELOG, README badge, ROADMAP. Nothing to test or lint.
• No new files in internal/ or pkg/ — test-placement rule not applicable.
• No LLM call sites touched — prompt-injection prevention not applicable.
• CHANGELOG [0.11.0] section references correct PRs (feat(recall): add --format json and --limit N flags #93–fix(web): broken footer links, duplicate titles, hero H1 spacing #118) and date (2026-04-07). ✓

No issues found. Ready to merge, tag v0.11.0, and cut the GitHub release.

[claude]

Review: LGTM

This is a release bump PR — version strings, changelog, roadmap, README badge, and a blog post. No code logic changes.

Checked:

• All version strings consistently updated to 0.11.0 across main.go, index.ts, package.json, package-lock.json, README badge, CHANGELOG, and ROADMAP
• CHANGELOG [0.11.0] compare URL correctly spans v0.10.0...v0.11.0; [Unreleased] correctly starts from v0.11.0...HEAD
• ROADMAP v0.11.0 marked Current; v0.12.0 added as new Planned section
• Blog post content consistent with CHANGELOG entries
• No new Go files, no test placement issues, no security concerns

No issues found. Ready to merge.

[claude]

Review: v0.11.0 release chore

Overall this is a clean, well-coordinated release PR. Two minor issues flagged as inline comments:

1. --sync-capture flag referenced but not implemented (web/content/blog/v0.11.0-async-graph-pipeline.mdx:68) — the upgrade notes tell users to pass this flag to opt back into synchronous capture, but the flag does not exist in any .go file. Needs either implementation or the sentence removed.

2. Missing EOF newline (eval/results_v0.10.0_post_fix.json:202) — trivial, but worth cleaning up.

Everything else checks out:

• Version consistency: binary (main.go), plugin (index.ts, package.json, package-lock.json), README badge, CHANGELOG, and ROADMAP all agree on 0.11.0.
• Scoring weights: new 9-factor formula sums to exactly 1.00 (0.45+0.08+0.05+0.10+0.08+0.07+0.07+0.05+0.05). Updated consistently across docs/ARCHITECTURE.md, web/content/docs/architecture.mdx, web/app/features/page.tsx, and web/app/playground/page.tsx.
• CHANGELOG links: all PR references (feat(recall): add --format json and --limit N flags #93, fix(health): test LLM credentials with a real ping call #98-fix(web): broken footer links, duplicate titles, hero H1 spacing #118) have matching link definitions at the bottom.
• No Go code changed beyond the version string — no error-wrapping, context propagation, or import path issues to check.
• No test files added inside internal/ or pkg/ — test placement convention respected.
• No LLM call paths modified — prompt injection surface unchanged.

[claude]

Review summary

This PR is a release-packaging commit (v0.11.0): version bumps, CHANGELOG/ROADMAP/README updates, two new blog posts, doc updates for the 9-factor scoring formula, and the v0.10.0 eval baseline file. No new Go logic is introduced.

Passes

• Go version bump (cmd/openclaw-cortex/main.go): trivial, correct.
• 9-factor weight consistency: weights sum to 1.00 in every document (0.45+0.08+0.05+0.10+0.08+0.07+0.07+0.05+0.05). README, ARCHITECTURE.md, docs/architecture.mdx, features/page.tsx, and playground/page.tsx are all aligned.
• Test placement: no test files added inside internal/ or pkg/. The convention is respected.
• Module paths: no Go imports changed; no path issues.
• Prompt-injection surface: no new LLM-calling code.
• Error wrapping / context propagation: not applicable (no new Go logic).
• Plugin/binary version sync: PLUGIN_VERSION, package.json, package-lock.json, and main.go all set to 0.11.0.
• Blog post accuracy: the --sync-capture flag reference was correctly removed in the last fixup commit.

Needs attention (inline comments posted)

1. eval/results_v0.10.0_post_fix.json vs blog post — the committed file shows LongMemEval at 100% EM, but web/content/blog/v0.10.0-eval-framework-admin-ui.mdx claims the CI floor is 80% EM. These contradict each other. Fix one or the other before merge so CI comparisons enforce the intended floor.

2. _post_fix provenance — storing retroactively-altered benchmark results as a CI baseline weakens the regression story. If the post-fix numbers are the right floor, the blog post should say so explicitly; if not, the original pre-fix results should be committed instead.

No blocking issues in the Go code. Once the eval baseline / blog-post contradiction is resolved, this is good to merge.

[claude]

Review: LGTM

This is a clean release-bump PR. Checked:

• Version consistency — main.go, index.ts, package.json, and package-lock.json all read 0.11.0, satisfying the CLAUDE.md requirement that plugin and binary versions stay in sync.
• Weight correctness — the new 9-factor formula (0.45 + 0.08 + 0.05 + 0.10 + 0.08 + 0.07 + 0.07 + 0.05 + 0.05) sums to exactly 1.00, and is consistent across every touched file (ARCHITECTURE.md, web/content/docs/architecture.mdx, features page, playground page, both blog posts).
• No Go logic changes — the only Go edit is the version string; no new code paths, error handling, or tests needed.
• No test placement violations — no test files added inside internal/ or pkg/.
• No security surface — no new LLM prompt interpolation or user-controlled input.

No issues found. ✅