TapirusDB v1.0.2

TapirusDB v1.0.2

This version brings the storage corrections, transactional AI document memory,
native SDKs and browser workspace from the current development line into one
versioned distribution. Publication status is recorded by the GitHub release
and package registries, independently of this source document.

Local AI data and source retrieval

• Store source text, supplied embeddings, tags and namespace/session fields.
• Combine BM25, vector similarity, recency and importance with source IDs and score components.
• Use indexed memory lifecycle operations, revision checks, batches, TTL and configurable budgets.
• Keep SQL and document-memory changes in the same transaction; use independent session ownership when needed.

Native SDKs and browser workspace

• Node.js and Python use native Rust bindings, bound SQL parameters and native database files.
• Python requires 3.10+ and includes migration, document-agent and retrieval-evaluation tools.
• The Rust WASM workspace opens and downloads native files and restores committed browser snapshots from IndexedDB.
• Browser copies are unencrypted. Native page encryption is optional.

Distribution changes

• The engine, workspace crates, native package manifests, WASM metadata and installer defaults use 1.0.2.
• A remote-pager trait coercion was replaced after the declared Rust 1.85 minimum failed a real compile check; the full-featured core now compiles with Rust 1.85 locally on Windows.
• Build-only SDK runs produce Python packages and a multi-platform npm tarball for review.
• The exact npm tarball is installed in a fresh consumer before it is eligible for registry publication.
• CLI archives have adjacent SHA-256 manifests, source/build records and a dependency inventory.
• The release workflow requires all five native targets, installs packaged CLIs on their matching hosts, and checks every archive before and after draft upload. These are publication gates, not evidence that a hosted run has succeeded.
• Registry publication is separate and manual. It requires a matching version tag and an already public GitHub release. Manual SDK runs default to build-only.
• The Linux/amd64 container is also published only by a separate manual workflow after the public release exists. A local Docker smoke test passed; that is not evidence of a public image.

Scope and evidence

The pre-tag hosted CI run for commit 8080302 passed all 28 jobs on 30 October 2026. The tag-triggered build and publication checks are separate; their results must be inspected before treating release assets as verified.

TapirusDB supports a documented SQL subset and selected vector, graph and JSON
APIs. It has its own file format and is not a SQLite drop-in. Namespace/session
filters are application filters; enforce access control in the application.

Historical benchmark claims are withdrawn. See
release validation, the
AI memory contract, and
security boundary for the covered behaviour and limits.
The core Rust crate forbids explicit unsafe code; the C ABI has a separate
unsafe boundary. No general latency, resource, crash-safety or certification
guarantee is implied.

Existing Homebrew and Winget manifests describe historical 1.0.1 distributions.
Update their URLs and actual archive digests only after the 1.0.2 assets exist.