build(deps): take splimes 1.0.0 from crates.io; drop the temporary patch

splimes 1.0.0 is published (tag v1.0.0, f8b3052: the release/1.0 commit
1bee9dd that the patch pinned, plus a GPU time-precision fix and docs; the
API WeftDB uses is identical). The root `[patch.crates-io]` that pointed
`splimes` at the git commit is deleted, and Cargo.lock resolves splimes 1.0.0
from the crates.io registry with its checksum. There is no git source left in
the lockfile, so `cargo deny check` (sources) and `cargo package --workspace`
pass again; the crates.io tarball's src/ is byte-identical to the v1.0.0 tag.

`cargo update -p splimes` also re-picked windows-sys 0.59 over 0.61 on seven
dependency edges and unicode-width 0.1 over 0.2 on one, all versions already in
the lock and unrelated to splimes; only the splimes entry is changed here, and
`cargo metadata --locked` accepts the lockfile as is.

CHANGELOG no longer says WeftDB builds through a temporary patch, and the
ROADMAP's "splimes 1.0 is released" item is done.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: physics515

CHANGELOG.md

@@ -27,8 +27,7 @@ While the project is pre-1.0, minor version bumps may contain breaking changes.
 - **`splimes` moved to its own repository** ([basic-automation/splimes](https://github.com/basic-automation/splimes))
   and is now a crates.io dependency. It is released on its own schedule, and a stable
   WeftDB waits on a stable splimes.
-- **splimes 0.1 → 1.0.** WeftDB depends on `splimes = "1"`, built against the
-  `release/1.0` commit through a temporary `[patch.crates-io]` until 1.0.0 is on
+- **splimes 0.1 → 1.0.** WeftDB depends on `splimes = "1"`, resolved to 1.0.0 from
   crates.io. splimes' [migration guide](https://github.com/basic-automation/splimes/blob/main/MIGRATING.md)
   lists the results that change; through WeftDB:
   - large inputs keep their method (0.1 swapped cubic for quadratic from 2,500 input

Cargo.lock

@@ -93,8 +93,3 @@ codegen-units = 1
 
 [profile.test]
 debug = 1
-
-# TEMPORARY: splimes 1.0.0 is not on crates.io yet. Pin the release/1.0 commit so the
-# migration can be built and tested; delete this section once 1.0.0 is published.
-[patch.crates-io]
-splimes = { git = "https://github.com/basic-automation/splimes", rev = "1bee9dd5493f830a9eded00812522725faac68b7" }

Cargo.toml

@@ -772,12 +772,11 @@ report → API/format freeze → **1.0**.
 
 ### Hot path & data model *(must land before the freeze)*
 
-- [ ] **splimes 1.0 is released**, and WeftDB depends on it. The interpolation engine is
-  its own crate ([basic-automation/splimes](https://github.com/basic-automation/splimes),
-  0.1.0 published 2026-10-05) with its own 1.0 criteria; a stable WeftDB can't promise a
-  stable API on top of an unstable engine. *WeftDB is migrated to the 1.0 API, built
-  against the `release/1.0` commit through a temporary `[patch.crates-io]` in the root
-  `Cargo.toml`; done once 1.0.0 is on crates.io and the patch is gone.*
+- [x] **splimes 1.0 is released**, and WeftDB depends on it. The interpolation engine is
+  its own crate ([basic-automation/splimes](https://github.com/basic-automation/splimes))
+  with its own 1.0 criteria; a stable WeftDB can't promise a stable API on top of an
+  unstable engine. *splimes 1.0.0 was published to crates.io on 2026-10-05, and WeftDB
+  depends on it from the registry (`splimes = "1"`, no patch or git source).*
 
 - [ ] **Measurement bulk ingest routed through the `.weftseg` seal** — the legacy `batch_capture_measurements` path is super-linear (see [Immediate next actions](#immediate-next-actions))
 - [ ] **B-tags** — per-measurement tags/labels; a data-model change that must precede the API/format freeze