release: prepare v0.4.1

Author: awksedgreep

CHANGELOG.md

@@ -10,13 +10,37 @@ capability document remains authoritative for a particular binary pairing.
 See the [compatibility statement](docs/COMPATIBILITY.md) and
 [upgrade guide](docs/UPGRADE.md).
 
-<!-- release-target: 0.4.0 -->
+<!-- release-target: 0.4.1 -->
 
 ## [Unreleased]
 
-Documentation on `main` now follows the `v0.4.0` source tag. The workspaces
-remain version `0.4.0` until the next release version is selected. No package
-or archive is published merely because this section changes.
+No changes recorded after `0.4.1`.
+
+## [0.4.1] — 2026-08-08
+
+### Added
+
+- A dedicated deferred-work index covering every non-shipped PromQL,
+  MetricsQL, LogsQL, trace-query, and TraceQL row by stable ID, with links to
+  its authoritative matrix, regressions, SQL recipes, evidence, findings, and
+  resumption prerequisites.
+
+### Changed
+
+- Reworked the root and signal-server READMEs as current product entry points
+  while retaining the complete 216-row query record in the maintained
+  matrices and evidence documents.
+- Updated compatibility, artifact, upgrade, testing, server, and release
+  documentation to distinguish source tags, workflow candidates, and complete
+  published artifact sets.
+- Linked the release tool against its own bundled SQLite so macOS artifact
+  identity verification does not depend on Apple's restricted system SQLite.
+
+### Compatibility
+
+- Storage data ABI 1, SQL-surface generation 1, batch/frame formats, and the
+  minimum `0.4.0` extension/server pairing remain unchanged. This patch does
+  not intentionally remove or reinterpret a public storage or query surface.
 
 ## [0.4.0] — 2026-08-08
 
@@ -154,7 +178,8 @@ Hardened statement atomicity, savepoints, multi-process series identity,
 attached schemas, transactional drop, filesystem compaction, deadlock
 avoidance, extreme timestamps, and performance parity.
 
-[Unreleased]: https://github.com/awksedgreep/timeless-libsql/compare/v0.4.0...HEAD
+[Unreleased]: https://github.com/awksedgreep/timeless-libsql/compare/v0.4.1...HEAD
+[0.4.1]: https://github.com/awksedgreep/timeless-libsql/compare/v0.4.0...v0.4.1
 [0.4.0]: https://github.com/awksedgreep/timeless-libsql/compare/v0.3.0...v0.4.0
 [0.3.0]: https://github.com/awksedgreep/timeless-libsql/releases/tag/v0.3.0
 [0.2.0]: https://github.com/awksedgreep/timeless-libsql/releases/tag/v0.2.0

Cargo.lock

@@ -17,7 +17,7 @@ default-members = [
 resolver = "2"
 
 [workspace.package]
-version = "0.4.0"
+version = "0.4.1"
 edition = "2021"
 license = "MIT"
 

Cargo.toml

@@ -22,6 +22,11 @@ Build from source until a later tag publishes all intended archives and the
 complete outer `SHA256SUMS`. Do not construct a download URL from the examples
 below or treat the existence of `v0.4.0` as binary availability.
 
+The `0.4.1` source line removes that known macOS link dependency by building
+the release tool with bundled SQLite. This is a packaging fix, not a
+publication claim: a `v0.4.1` tag must still complete all four native jobs and
+the outer checksum gate before its workflow artifacts form a complete set.
+
 The standalone dbhealth extension is intentionally not in this bundle. Build
 `dbhealth-ext` separately from compatible source when it is required.
 

docs/ARTIFACTS.md

@@ -15,8 +15,8 @@ constants that enforce the handshake.
 
 | Contract key | Current value | Meaning |
 |---|---:|---|
-| `extension_workspace` | `0.4.0` | Current tagged extension/core/dbhealth source line. |
-| `server_workspace` | `0.4.0` | Current tagged metrics/logs/traces server source line. |
+| `extension_workspace` | `0.4.1` | Current extension/core/dbhealth source line. |
+| `server_workspace` | `0.4.1` | Current metrics/logs/traces server source line. |
 | `extension_data_abi` | `1` | Stored/public telemetry data compatibility generation. |
 | `sql_surface_version` | `1` | Advertised public SQL inventory generation. |
 | `extension_minimum_server` | `0.4.0` | Oldest server accepted by the current extension document. |

docs/COMPATIBILITY.md

@@ -81,7 +81,7 @@ primitives, not a claim that TraceQL is implemented.
 
 | area | current state | next decision |
 |---|---|---|
-| Native release packaging | `v0.4.0` Linux candidates passed; macOS failed because the release tool linked against Apple's restricted system SQLite; no complete checksum set or GitHub Release exists. | Make the release tool independent of Apple's restricted SQLite, validate both macOS architectures, and use a new immutable tag. |
+| Native release packaging | `v0.4.0` Linux candidates passed; macOS failed because the release tool linked against Apple's restricted system SQLite; no complete checksum set or GitHub Release exists. The `0.4.1` source line now bundles SQLite into the release tool. | Validate both macOS architectures and the complete outer checksum gate from a new immutable tag; publication remains unproven until that run passes. |
 | Remaining Python benchmark utilities | The production extension/API/query/SQL/crash harnesses are Rust, but the exact remaining scripts are inventoried in [TESTING.md](../TESTING.md#tooling-migration-status). | Port one bounded harness at a time while retaining fixture, completed-work, percentile, storage, cleanup, and RSS contracts. |
 | Competitive baselines | Current evidence measures correctness, regression, SQLite controls, public storage work, and endpoint tails. It does not claim VictoriaMetrics, VictoriaLogs, or Jaeger performance parity. | Add pinned, same-fixture competitive measurements when they become a priority; do not weaken current gates in the process. |
 | Higher-order Elixir interfaces | The Rust servers own the data plane; the query release report contains the control-plane recommendations. | Inventory and redesign downstream Elixir interfaces in their own repositories and goal, without moving query/storage work back into Elixir. |

docs/DEFERRED_WORK.md

@@ -6,11 +6,12 @@ not turn the server binaries into readers for an unrelated Rust block-store
 directory; that conversion belongs to the higher-order product that owns the
 legacy format and must write through the public Timeless batch/SQL contracts.
 
-The current source line is `0.4.0`, and `v0.4.0` is tagged from validated
-`main`. That tag has no complete published native artifact set: its Linux
+The current source line is `0.4.1`. The preceding `v0.4.0` tag has no complete
+published native artifact set: its Linux
 candidate bundles passed, its macOS packaging jobs failed, and no outer
 checksum set or GitHub Release was published. Build the matching extension and
-servers from source, or wait for a later complete release; do not mix a
+servers from source, or use a later complete release recorded in the
+[artifact guide](ARTIFACTS.md); do not mix a
 workflow-retained candidate with another version. The earlier `v0.3.0` tag
 predates the capability handshake and is not a valid extension peer for a
 `0.4.x` server.

docs/UPGRADE.md

@@ -8,7 +8,7 @@ members = [
 resolver = "2"
 
 [workspace.package]
-version = "0.4.0"
+version = "0.4.1"
 edition = "2021"
 license = "MIT"