ContinuityDB v0.9.2

What's Changed

• Release v0.9.2: fix retry identity, adapters, ingestion and search budgets by @deva-prakash-j in #13

Full Changelog: v0.9.1...v0.9.2

ContinuityDB v0.9.1

Stability patch: fourteen reviewed findings fixed

• Storage integrity: transactional canonical-write recovery, concurrent idempotency, non-destructive rebuild, fresh captures after expiry, and WAL-aware inspection.
• Access and lifecycle: local HTTP/MCP request boundaries, configured capture-policy parity, branch-safe lineage, exact OIDC issuer identifiers.
• Client correctness: root-registration integrity, OpenCode tenant/owner/sensitivity preservation and recall on every model request, managed Windows upgrades.
• Code graphs: Unicode-correct Java/Spring offsets and invalidation of older extraction caches.

Verification

381 source tests passed with no failures/skips locally; final Node22/24 CI, container and Linux/macOS/Windows native gates passed. Real Codex generated-configuration and OpenCode multi-round client probes, binary/semantic smoke checks, and a 12-check synthetic v0.9.0→v0.9.1 preservation/recovery exercise passed. Production dependency audit reported zero known vulnerabilities.

Native assets below include checksums and GitHub build provenance. No new dependencies or automatic capture behavior are introduced.

Upgrade notes

Stop all writers and back up the entire vault before upgrading, including SQLite/WAL and canonical files. Record-only JSONL exports do not contain all feedback, audit or pending recovery state. Do not mix older writers with v0.9.1.

A committed filesystem projection failure reports CANONICAL_PROJECTION_PENDING, committed: true, recovery_pending: true. Restore filesystem availability, reopen a writable vault, and retry with the original idempotency key. Do not manufacture a replacement capture for an already committed write. Low-level writeCanonical callers must use a memory transaction; normal capture/propose/commit APIs manage this automatically.

Missing canonical files now stop a rebuild rather than deleting durable state. Previously orphaned v0.9.0 files are not silently classified or removed. Rollback requires the full pre-upgrade snapshot, not only an older binary. Process interruption was tested; physical power-loss durability is not newly claimed.

Detailed migration and coverage · Fix PR #12

ContinuityDB main build 42e55507f36f

What's Changed

• Release v0.9.2: fix retry identity, adapters, ingestion and search budgets by @deva-prakash-j in #13

Full Changelog: v0.9.1...main-42e55507f36fd4767ba7d2df9e7c3a62240272c6

ContinuityDB main build 1bbc25d32256

What's Changed

• fix: release v0.9.1 with fourteen stability corrections by @deva-prakash-j in #12

Full Changelog: v0.9.0...main-1bbc25d322560dd4a94f6c50a8340ede54075ed8

ContinuityDB v0.9.0

Full Changelog: v0.8.0...v0.9.0

ContinuityDB main build 88f6632a0b21

Full Changelog: v0.8.0...main-88f6632a0b216082067f2352173ebb008e485573

ContinuityDB v0.8.0

What's Changed

• feat: add zero-touch OpenCode project memory by @deva-prakash-j in #10

Full Changelog: v0.7.0...v0.8.0

ContinuityDB main build 12878bea2afc

What's Changed

• feat: add zero-touch OpenCode project memory by @deva-prakash-j in #10

Full Changelog: v0.7.0...main-12878bea2afcca39972c1445864354c243b6cf6c

ContinuityDB v0.7.0

What's Changed

• feat: zero-instruction ContinuityDB integrations by @deva-prakash-j in #9

Full Changelog: main-9eafbfc9ad2456256d07b0d401cb1c25c03ebc51...v0.7.0

ContinuityDB main build 9eafbfc9ad24

What's Changed

• docs: prepare GitHub organic launch by @deva-prakash-j in #2

Full Changelog: main-f1e78a646c9e537bb4714d7c00bc6116f361d0ba...main-9eafbfc9ad2456256d07b0d401cb1c25c03ebc51