chore: prepare v1.0.6 release

Align the Rust, Python, WASM, Conda, docs, and lockfile version markers to 1.0.6 so the published artifacts and release automation agree on a single release number.

Add a proper 1.0.6 changelog entry in both CHANGELOG.md and the docs release notes, covering the pre-push gate, expanded Rust and WASM surface, benchmark refresh, and CI hardening work shipped since v1.0.4.

Validate the release preparation with the repo-managed pre-push suite so version, changelog, Rust, Python, docs, WASM, and API-manifest checks all pass before tagging.

wasm/Cargo.lock

@@ -49,11 +49,11 @@ checksum = "9330f8b2ff13f34540b44e946ef35111825727b38d33286ef986142615121801"
 
 [[package]]
 name = "ferro_ta_core"
-version = "1.0.4"
+version = "1.0.6"
 
 [[package]]
 name = "ferro_ta_wasm"
-version = "1.0.4"
+version = "1.0.6"
 dependencies = [
  "ferro_ta_core",
  "js-sys",

wasm/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "ferro_ta_wasm"
-version = "1.0.4"
+version = "1.0.6"
 edition = "2021"
 description = "WebAssembly bindings for ferro-ta technical analysis indicators"
 license = "MIT"

wasm/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ferro-ta-wasm",
-  "version": "1.0.4",
+  "version": "1.0.6",
   "description": "WebAssembly bindings for ferro-ta technical analysis indicators",
   "main": "pkg/ferro_ta_wasm.js",
   "types": "pkg/ferro_ta_wasm.d.ts",