docs: standardise language naming + binding security sections (#290)

* docs: standardise language naming and add binding security sections

Canonical binding list everywhere: Rust, Python, Node.js, WASM, C, C++, C#,
Go, Java, R. Use C# (not .NET) as the language label, WASM (not WebAssembly)
in prose, and frame the C ABI as a hub rather than a list item.

- Bump stale indicator counts (200+ -> 514) and family count (sixteen ->
  twenty-four) in the Node/Python/WASM and docs READMEs.
- Add a short Security section to all eight binding READMEs.
- Relabel benchmark rows (C -> C / C++, C# / .NET -> C#).
- Fix the 'language stecker' wording in the C#/Go/R API intros.
- Documentation only; no code or public API changes.

* release.yml: extend install snippets and expose version output

Add the missing registry installs to the release body (dotnet, go, Gradle/
Maven Central, r-universe) alongside cargo/pip/npm, and expose a v-stripped
'version' output from the tag step for the Gradle coordinate. Also fix the
C-ABI language order in the assets note (C# before Go).

* release.yml: correct the release body (10 languages, all registries)

Reframe the tagline to '10 languages' (native Rust/Python/Node.js/WASM + a C
ABI hub for C, C++, C#, Go, Java, R) instead of '4 language registries', note
that C#/Java/Go/R publish to NuGet/Maven/Go/r-universe via their own jobs, and
tidy the Node.js label and the C-ABI hub list.

bindings/csharp/README.md

@@ -1,18 +1,18 @@
-# Wickra — .NET
+# Wickra — C#
 
 [![CI](https://github.com/wickra-lib/wickra/actions/workflows/ci.yml/badge.svg)](https://github.com/wickra-lib/wickra/actions/workflows/ci.yml)
 [![codecov](https://codecov.io/gh/wickra-lib/wickra/branch/main/graph/badge.svg)](https://codecov.io/gh/wickra-lib/wickra)
 [![NuGet](https://img.shields.io/nuget/v/Wickra.svg?logo=nuget&color=blue)](https://www.nuget.org/packages/Wickra)
 [![License: MIT OR Apache-2.0](https://img.shields.io/badge/license-MIT_OR_Apache--2.0-blue)](https://github.com/wickra-lib/wickra#license)
 
-**Streaming-first technical indicators for .NET. `dotnet add package Wickra` —
+**Streaming-first technical indicators for C#. `dotnet add package Wickra` —
 prebuilt native library, no system dependencies.**
 
 Wickra is a multi-language technical-analysis library with a Rust core and
-bindings for Python, Node.js and WebAssembly, plus a C ABI for C/C++, C#, Go, Java, R and any
+bindings for Python, Node.js and WASM, plus a C ABI for C, C++, C#, Go, Java, R and any
 other C-capable language. Every indicator is an O(1)
 streaming state machine, so live trading bots and historical backtests share
-the exact same implementation. This package is the .NET binding; it consumes the
+the exact same implementation. This package is the C# binding; it consumes the
 C ABI hub through `[LibraryImport]` P/Invoke and exposes all 514 streaming-first
 indicators as idiomatic `IDisposable` classes.
 
@@ -73,10 +73,17 @@ the main repository and documentation site:
 - **Docs** (quickstarts, cookbook, TA-Lib migration): <https://docs.wickra.org>
 - **Runnable examples:** [`examples/csharp/`](https://github.com/wickra-lib/wickra/tree/main/examples/csharp)
 
-Wickra ships native bindings for Python, Node.js, WebAssembly and Rust, plus a
-C ABI hub that any C-capable language (C, C++, Go, C#, Java, R) links against —
+Wickra ships native bindings for Python, Node.js, WASM and Rust, plus a
+C ABI hub that any C-capable language (C, C++, C#, Go, Java, R) links against —
 all exposing the same indicators from the shared, `unsafe`-forbidden Rust core.
 
+## Security
+
+Found a security issue? **Please don't open a public issue.** Report it privately
+via the affected repository's *Security* tab (*"Report a vulnerability"*) or email
+**support@wickra.org** with a subject line starting `[wickra security]`. Full
+policy: <https://github.com/wickra-lib/wickra/blob/main/SECURITY.md>.
+
 ## Disclaimer
 
 Wickra is an indicator toolkit, not a trading system. The values it computes