centaur_technical_indicators 1.2.2__tar.gz → 1.3.1__tar.gz

centaur_technical_indicators-1.3.1/.github/pull_request_template.md

@@ -0,0 +1,26 @@
+## Summary
+- What changed?
+- Why was this change needed?
+
+## Scope
+- Files/modules touched:
+- Intentionally left untouched:
+
+## Compatibility
+- User-facing Python API impact:
+- Migration notes (if any):
+
+## Validation
+- [ ] `maturin develop` (bindings compile cleanly)
+- [ ] `python -m pytest` (all tests pass)
+- [ ] `cargo fmt --all -- --check` (no formatting diffs)
+
+Command output summary (paste the pytest `N passed` line and any gate output):
+
+## Changelog
+- [ ] `CHANGELOG.md` updated under `## [Unreleased]` for user-facing changes (or exempt — non-user-facing)
+- Entry summary:
+
+## Flagged / notes
+- Out-of-scope issues, surprises, or blockers:
+- AI assistance disclosed (per `CONTRIBUTING.md`):

{centaur_technical_indicators-1.2.2 → centaur_technical_indicators-1.3.1}/.github/workflows/CI.yml

@@ -23,6 +23,8 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v6
+      - name: Check Rust formatting
+        run: cargo fmt --all -- --check
       - uses: actions/setup-python@v6
         with:
           python-version: '3.12'

centaur_technical_indicators-1.3.1/AGENTS.md

@@ -0,0 +1,152 @@
+# AGENTS.md
+
+Guidance for coding agents working in this repository. This file is the
+authoritative source for the repo's standing conventions — pre-PR gates,
+branch/commit format, PR shape, scope discipline, stop-and-report, changelog
+coupling, and worktree isolation. Task briefs defer to it and record only what is
+specific to the task.
+
+## Project at a glance
+- **Repo type:** Python package with a Rust core exposed via PyO3/maturin.
+- **Primary goal:** Keep Python bindings stable while preserving Rust-side correctness and performance.
+- **Main source directories:**
+  - `src/` → Rust implementation + Python bindings
+  - `tests/` → Python-facing smoke/behavior tests for bindings
+
+## Docs to review before coding
+- `docs/REPO_MAP.md`
+- `CONTRIBUTING.md`
+
+## Recommended workflow
+1. **Set up an isolated environment**
+   ```bash
+   python -m venv .venv
+   source .venv/bin/activate
+   python -m pip install --upgrade pip
+   pip install -r test_requirements.txt
+   ```
+2. **Build extension module**
+   ```bash
+   maturin develop
+   ```
+3. **Run tests**
+   ```bash
+   python -m pytest
+   ```
+4. **Check formatting**
+   ```bash
+   cargo fmt --all -- --check
+   ```
+
+These feed the canonical **Pre-PR quality gates** below.
+
+## What to change (and where)
+- Add/update indicator logic in the relevant Rust module under `src/`.
+- Keep API exposure and types consistent through `src/lib.rs`.
+- Add/adjust Python tests in matching files under `tests/`.
+- Update docs (`README.md`) and the changelog when behavior or API changes (see **Changelog coupling**).
+- Touching an indicator module (`src/*_indicators.rs`, `src/chart_trends.rs`, `src/moving_average.rs`, …) also requires running the companion benchmark — see `ai-policy.yaml` and `CONTRIBUTING.md`.
+
+## Coding expectations
+- Preserve the existing **bulk/single** API pattern for indicators.
+- Prefer small, focused diffs over large refactors.
+- Keep naming and argument conventions consistent with neighboring functions.
+- Surface all errors to Python as `PyValueError`, with clear, user-facing messages for invalid inputs.
+
+## Change scope discipline
+- Keep changes minimal and focused on the requested task.
+- Do not include opportunistic refactors unless explicitly requested.
+- If you identify unrelated issues, note them separately instead of bundling them into the same change.
+- Preserve existing file organization and naming conventions unless the task requires a structural change.
+- **Stage only the files the task names; never `git add .`.** Never commit untracked planning/scratch docs (`PLAN.md`, `*_BRIEF.md`, `RESUME.md`).
+- Never hand-edit generated artifacts or test expectations to make a gate pass — `Cargo.lock` is regenerated by the build, and a test value that needs changing is a signal to **stop and report**, not to edit the expectation.
+
+## Backward compatibility rules
+When changing public Python APIs, preserve compatibility unless the task explicitly allows a breaking change:
+
+1. Do not silently change indicator semantics, output ordering, or warmup behavior.
+2. Do not remove or rename public functions, types, enums, or parameters without explicit approval.
+3. If behavior changes are required, document them in docstrings and `CHANGELOG.md` with clear migration notes.
+
+## Branch & commit conventions
+- **Branches:** cut every branch off the latest `origin/main`; never commit on `main`. Name them `<type>/<kebab-slug>`, where `<type>` is a conventional-commit type (`feat`, `fix`, `chore`, `docs`, `ci`, `test`, `style`, `refactor`, `perf`) — e.g. `chore/bump-cti-1.3.0`, `docs/string-aliases`, `ci/add-fmt-check`. First push is `git push -u origin <branch>`.
+- **Commit subjects:** use a conventional-commit prefix (`feat:`, `fix:`, `chore:`, `docs:`, `ci:`, `test:`, `style:`, …), under 72 characters.
+- **Trailer:** end every commit authored with Claude Code with:
+  ```text
+  Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
+  ```
+  This is the canonical trailer for Claude-authored commits; existing lowercase `Co-authored-by:` lines for human or bot co-authors are unaffected.
+
+## Pre-PR quality gates (must pass)
+Run all three inside the repo's `.venv` (the `maturin`/`pytest` binaries are not on `PATH`), in order — `pytest` only passes after a successful `maturin develop`:
+
+1. `maturin develop` — bindings compile and install into the active venv
+2. `python -m pytest` — all tests pass (the pass signal is the `N passed` line; paste it into the PR)
+3. `cargo fmt --all -- --check` — no formatting diffs
+
+Notes:
+- **clippy is intentionally parked** — do not add a clippy gate without maintainer approval.
+- CI enforces all three gates: `.github/workflows/CI.yml`'s `verify` job runs `cargo fmt --all -- --check` (first), then `maturin develop --release` and `python -m pytest`; `python-package.yml` runs the pytest matrix across Python versions. `cargo fmt` is a CI gate, not local-only. If tests are skipped for environmental reasons, say why.
+
+## Stop-and-report
+Stop and report — do not work around, guess, or paper over — when:
+- a pre-PR gate fails unexpectedly, or a test expectation shifts in a way you can't explain;
+- `cargo fmt` produces a change you can't explain as pure formatting (e.g. an rustfmt version skew);
+- the brief or instructions conflict with the repo's actual state.
+
+Surface drift between docs and code rather than silently fixing it. Treat governing docs — CI workflows, licensing, security, and contributor-governance files (`CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, `SECURITY.md`) — as read-only unless the task explicitly authorizes editing them.
+
+## Worktree & isolation
+For parallel or batched work (e.g. running multiple slice briefs):
+- one task per git worktree, cut off fresh `origin/main`;
+- **each worktree gets its own `.venv`** — a shared venv's installed extension gets clobbered by concurrent `maturin develop` runs;
+- when two batches touch the same files, rebase the later one on its predecessor before merge;
+- PRs target `main`; there is no separate long-lived integration branch (the release cut promotes `## [Unreleased]` to the next version).
+
+## Changelog coupling
+- Every **user-facing** change adds an entry under the existing `## [Unreleased]` heading in `CHANGELOG.md`, using Keep a Changelog categories (Added / Changed / Deprecated / Removed / Fixed / Security). Do not add a second `[Unreleased]` heading or hand-cut a version header in a feature branch — the release cut promotes `[Unreleased]` to the next version.
+- **Exception:** formatting-only or otherwise non-user-facing changes (e.g. a `cargo fmt` baseline, or docs such as this file) get **no** changelog entry.
+
+## CI implementation policy
+- Prefer native Python/maturin/cargo commands in workflows.
+- Do not introduce third-party GitHub Actions unless explicitly approved by maintainers.
+
+## Core-crate version & source of truth
+- The binding wraps the published crates.io crate `centaur_technical_indicators`; that core-crate version is the source of truth, and `[package] version` in `Cargo.toml` is normally bumped to match it (see `docs/REPO_MAP.md` for the full rule).
+- `[package] version` need **not** always equal the core-crate version. A **binding-only patch release** — one that changes only the bindings/tooling (e.g. the 1.3.1 security patch: PyO3 and test-tooling bumps, no core-crate code) — may move `[package] version` ahead while the `centaur_technical_indicators` dependency stays put. The version-match rule above is the default; binding-only patches are the documented exception. *(Example: 1.3.1 ships `[package] version = 1.3.1` against core crate `1.3.0`.)*
+
+## Pull request checklist for agents
+- [ ] Scope is minimal and matches the task; only the named files changed.
+- [ ] Rust bindings compile (`maturin develop`).
+- [ ] Tests pass (or skips are documented).
+- [ ] `cargo fmt --all -- --check` clean.
+- [ ] Changelog updated under `## [Unreleased]` (or exempt — see Changelog coupling).
+- [ ] Commit message uses a conventional prefix and the Co-Authored-By trailer.
+- [ ] AI assistance disclosed in the PR description (per `CONTRIBUTING.md`).
+
+## Required PR summary format
+Use this structure in the PR description (mirrors `.github/pull_request_template.md`):
+
+1. **Summary** — what changed and why.
+2. **Scope** — files/modules touched, and what was intentionally left untouched.
+3. **Compatibility** — user-facing behavior/API impact, or explicit "N/A".
+4. **Validation** — paste the actual gate output (`maturin develop`, the pytest `N passed` line, `cargo fmt --all -- --check`).
+5. **Changelog** — the exact `CHANGELOG.md` entry added/updated (or "exempt — non-user-facing").
+
+Also note anything **flagged** — out-of-scope issues noticed, surprises, or blockers — and disclose AI assistance (per `CONTRIBUTING.md`).
+
+## Repository expectations
+- This is a public Python/Rust library. Prioritize correctness, determinism, and backward compatibility.
+- Prefer minimal, focused diffs over broad refactors.
+- Do not add new dependencies unless explicitly requested.
+- Treat public APIs, documented behavior, and examples as stability-sensitive.
+
+## Review guidelines
+- Flag breaking API changes.
+- Flag silent behavior changes in indicator calculations or defaults.
+- Flag documentation drift when public behavior changes.
+- Flag unnecessary allocations or obvious performance regressions in hot paths.
+
+## Change boundaries
+- Do not modify CI, licensing, security, or contributor-governance files unless explicitly requested.
+- Keep unrelated formatting churn to a minimum.

{centaur_technical_indicators-1.2.2 → centaur_technical_indicators-1.3.1}/CHANGELOG.md

@@ -6,7 +6,59 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 ---
 
-## [Unreleased]
+## [1.3.1] - 2026-06-21
+
+### Security
+- Bumped test-only tooling: pytest 8.4.1 → 9.0.3 (resolves GHSA-6w46-j5rx-g56g, vulnerable tmpdir
+  handling) and Pygments 2.19.2 → 2.20.0 (resolves GHSA-5239-wwwm-4pmq, ReDoS in the GUID-matching
+  regex). Development/CI dependencies only — no runtime or API impact on the installed package.
+- Bumped PyO3 from 0.25 to 0.29, resolving GHSA-36hh-v3qg-5jq4 (out-of-bounds read in the
+  `nth`/`nth_back` iterators of `PyList`/`PyTuple`) and GHSA-chgr-c6px-7xpp (missing `Sync` bound
+  on `PyCFunction::new_closure`). Neither vulnerable path is exercised by these bindings; the bump
+  clears both advisories at the dependency level.
+
+### Changed
+- Declared `rust-version = "1.83"` in `Cargo.toml` — the minimum supported Rust the PyO3 0.29
+  bump requires (no impact on prebuilt wheels; relevant only when building from source).
+
+---
+
+## [1.3.0] - 2026-06-20
+
+### Fixed
+- Incorrect `Documentation` URL in package metadata (pointed at the GitHub wiki).
+- README quick-start example called `cti.moving_average(...)` (a submodule, not callable)
+  instead of `cti.moving_average.single.moving_average(...)`.
+- Docstring keyword-name mismatches that could raise `TypeError` (`supertrend`
+  `constant_type_model` → `constant_model_type`; `true_range` `previous_close` → `close`).
+- README "Available Indicators" / "Library Structure" drift and benchmark-vs-list inconsistency.
+- Inherited Rust 1.3.0 behavior changes, now user-visible through the bindings:
+  `chart_trends.peaks` / `chart_trends.valleys` corrected for index-0 and
+  retained-after-monotonic-run extrema; and `aroon_up` / `aroon_down` /
+  `stochastic_oscillator` return `NaN` instead of panicking on all-NaN input.
+
+### Added
+- Python regression tests for inherited Rust 1.3.0 chart-trend / degenerate-input fixes.
+- `chart_trends.peak_favorable_move` and `chart_trends.valley_favorable_move` bindings (maximum
+  favorable excursion over a forward window), mirroring Rust 1.3.0.
+- `cargo fmt --check` step to CI (the `verify` job in `CI.yml`).
+- `docs/2.0.0.md` breaking-change backlog.
+- Tests pinning accepted model-type / deviation-model / moving-average-type string aliases.
+- Documentation of the full accepted string-alias set for each regime (incl. the `sma`→Smoothed
+  / `ma`→Simple aliases), with `from_string` error messages reconciled to match.
+- README scope note: statistical primitives (the Rust `basic_indicators` surface) are
+  intentionally not re-bound.
+- Type stubs (`.pyi`) and a `py.typed` marker (PEP 561 inline typing) for the full API surface.
+- `__version__` on the top-level package, resolved via `importlib.metadata`.
+- Mixed package layout with a hand-authored `__init__.py` (adopts maturin `python-source`).
+
+### Changed
+- Updated `centaur_technical_indicators` Rust crate dependency from `1.2.2` to `1.3.0`.
+- Expanded PyPI classifiers to declare Python 3.10–3.14.
+- Updated ecosystem naming from "Centaur Capital" to "CRT (Centaur Research & Technologies)"
+  and the legacy `centaurlabs.pages.dev` documentation link.
+- Adjusted the indicator-count claim from "60+" to "50+".
+- Exclude internal `docs/` from the source distribution (sdist).
 
 ## [1.2.2] - 2026-04-04
 

centaur_technical_indicators-1.3.1/CLAUDE.md

@@ -0,0 +1,21 @@
+# CLAUDE.md
+
+Claude Code operating notes for this repo. **[`AGENTS.md`](AGENTS.md) is
+canonical** for every standing convention — pre-PR gates, branch/commit format,
+PR shape, scope discipline, stop-and-report, changelog coupling, and worktree
+isolation. This file adds only the Claude-Code-facing bits for running a slice; it
+does not repeat `AGENTS.md`.
+
+## Running a slice
+- Work is organized as slice briefs (`S*_BRIEF.md`) tracked by `PLAN.md`. `PLAN.md` is the planning channel — implement against the briefs; do not edit `PLAN.md`.
+- Read order at session start: the slice brief (it is self-contained) → `AGENTS.md` (standing conventions). You don't need to read `PLAN.md` to execute a self-contained brief.
+- **One slice per session**, in its **own git worktree with its own `.venv`** (per `AGENTS.md` → Worktree & isolation).
+
+## Effort
+Set the session effort from the brief's `Effort:` line (`low` / `medium` / `high`) with `/effort <level>`.
+
+## Plan before auto-editing
+For a non-trivial slice, plan before editing — use plan mode before auto-applying changes. Honor the stop-and-report rule in `AGENTS.md`: when a gate fails unexpectedly or a test value shifts, stop and report rather than working around it.
+
+## Running the gates
+Inside the worktree's `.venv`: `maturin develop` → `python -m pytest` (pass signal `N passed`) → `cargo fmt --all -- --check`. Full gate definitions and the CI-divergence note live in `AGENTS.md`.

{centaur_technical_indicators-1.2.2 → centaur_technical_indicators-1.3.1}/Cargo.lock

@@ -3,52 +3,31 @@
 version = 4
 
 [[package]]
-name = "autocfg"
-version = "1.5.0"
+name = "centaur_technical_indicators"
+version = "1.3.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "c08606f8c3cbf4ce6ec8e28fb0014a2c086708fe954eaa885384a6165172e7e8"
+checksum = "41f1d42ebb4f20df394539be4afd1a21f69a6f18c7ab9ae3a8eaeac7929e1bfb"
 
 [[package]]
 name = "centaur_technical_indicators"
-version = "1.2.2"
+version = "1.3.1"
 dependencies = [
- "centaur_technical_indicators 1.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
+ "centaur_technical_indicators 1.3.0",
  "pyo3",
 ]
 
-[[package]]
-name = "centaur_technical_indicators"
-version = "1.2.2"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "24ae4cb5750fab3c9d2ae9be158158df08bb4b052c6e5c398885be57e0590be9"
-
 [[package]]
 name = "heck"
 version = "0.5.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "2304e00983f87ffb38b55b444b5e3b60a884b5d30c0fca7d82fe33449bbe55ea"
 
-[[package]]
-name = "indoc"
-version = "2.0.6"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "f4c7245a08504955605670dbf141fceab975f15ca21570696aebe9d2e71576bd"
-
 [[package]]
 name = "libc"
 version = "0.2.174"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "1171693293099992e19cddea4e8b849964e9846f4acee11b3948bcc337be8776"
 
-[[package]]
-name = "memoffset"
-version = "0.9.1"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "488016bfae457b036d996092f6cb448677611ce4449e970ceaf42695203f218a"
-dependencies = [
- "autocfg",
-]
-
 [[package]]
 name = "once_cell"
 version = "1.21.3"
@@ -72,36 +51,32 @@ dependencies = [
 
 [[package]]
 name = "pyo3"
-version = "0.25.1"
+version = "0.29.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "8970a78afe0628a3e3430376fc5fd76b6b45c4d43360ffd6cdd40bdde72b682a"
+checksum = "cd274650b21d4bfc26a0a47587962c1edb425f69287324355cd040c3ea66071c"
 dependencies = [
- "indoc",
  "libc",
- "memoffset",
  "once_cell",
  "portable-atomic",
  "pyo3-build-config",
  "pyo3-ffi",
  "pyo3-macros",
- "unindent",
 ]
 
 [[package]]
 name = "pyo3-build-config"
-version = "0.25.1"
+version = "0.29.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "458eb0c55e7ece017adeba38f2248ff3ac615e53660d7c71a238d7d2a01c7598"
+checksum = "c5e2a7d2f0d013342f295c048ad19237add5154a55b1c5a254c0ec93d4109078"
 dependencies = [
- "once_cell",
  "target-lexicon",
 ]
 
 [[package]]
 name = "pyo3-ffi"
-version = "0.25.1"
+version = "0.29.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "7114fe5457c61b276ab77c5055f206295b812608083644a5c5b2640c3102565c"
+checksum = "ca85c467da1bbc8d866eea5deff9cf29ea5f7785054a17da36e65bda9c05845b"
 dependencies = [
  "libc",
  "pyo3-build-config",
@@ -109,9 +84,9 @@ dependencies = [
 
 [[package]]
 name = "pyo3-macros"
-version = "0.25.1"
+version = "0.29.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "a8725c0a622b374d6cb051d11a0983786448f7785336139c3c94f5aa6bef7e50"
+checksum = "9ac53762fd065daa3194dd09337a38bd793a188100fd1a9304c4ab312d901771"
 dependencies = [
  "proc-macro2",
  "pyo3-macros-backend",
@@ -121,13 +96,12 @@ dependencies = [
 
 [[package]]
 name = "pyo3-macros-backend"
-version = "0.25.1"
+version = "0.29.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "4109984c22491085343c05b0dbc54ddc405c3cf7b4374fc533f5c3313a572ccc"
+checksum = "4ca3a1557399783172dc5bf39cfca835157732532cba56b71d2292161e53b362"
 dependencies = [
  "heck",
  "proc-macro2",
- "pyo3-build-config",
  "quote",
  "syn",
 ]
@@ -154,18 +128,12 @@ dependencies = [
 
 [[package]]
 name = "target-lexicon"
-version = "0.13.2"
+version = "0.13.5"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "e502f78cdbb8ba4718f566c418c52bc729126ffd16baee5baa718cf25dd5a69a"
+checksum = "adb6935a6f5c20170eeceb1a3835a49e12e19d792f6dd344ccc76a985ca5a6ca"
 
 [[package]]
 name = "unicode-ident"
 version = "1.0.18"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "5a5f39404a5da50712a4c1eecf25e90dd62b613502b7e925fd4e4d19b5c96512"
-
-[[package]]
-name = "unindent"
-version = "0.2.4"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "7264e107f553ccae879d21fbea1d6724ac785e8c3bfc762137959b5802826ef3"

{centaur_technical_indicators-1.2.2 → centaur_technical_indicators-1.3.1}/Cargo.toml

@@ -1,7 +1,8 @@
 [package]
 name = "centaur_technical_indicators"
-version = "1.2.2"
+version = "1.3.1"
 edition = "2021"
+rust-version = "1.83"
 readme = "README.md"
 
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
@@ -10,5 +11,5 @@ name = "centaur_technical_indicators"
 crate-type = ["cdylib"]
 
 [dependencies]
-pyo3 = "0.25.0"
-centaur_technical_indicators = "1.2.2"
+pyo3 = "0.29"
+centaur_technical_indicators = "1.3.0"

{centaur_technical_indicators-1.2.2 → centaur_technical_indicators-1.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: centaur_technical_indicators
-Version: 1.2.2
+Version: 1.3.1
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Financial and Insurance Industry
 Classifier: Topic :: Software Development :: Libraries
@@ -8,14 +8,19 @@ Classifier: Topic :: Office/Business :: Financial :: Investment
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Programming Language :: Rust
 Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 License-File: LICENSE-MIT
-Summary: A collection of 60+ fully configurable technical indicators for financial analysis, powered by Rust and Python. Part of the Centaur Capital ecosystem.
+Summary: A collection of 50+ fully configurable technical indicators for financial analysis, powered by Rust and Python. Part of the CRT (Centaur Research & Technologies) ecosystem.
 Keywords: finance,technical indicators,analysis,trading,python,rust,quantitative
 Author-email: ChironMind <your@email.com>
 Maintainer-email: ChironMind <your@email.com>
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
-Project-URL: Documentation, https://github.com/chironmind/CentaurTechnicalIndicators-Python/wiki
+Project-URL: Documentation, https://centaurtechnicalindicators-python.readthedocs.io/en/latest/
 Project-URL: Homepage, https://github.com/chironmind/CentaurTechnicalIndicators-Python
 Project-URL: Issues, https://github.com/chironmind/CentaurTechnicalIndicators-Python/issues
 Project-URL: Source, https://github.com/chironmind/CentaurTechnicalIndicators-Python
@@ -33,9 +38,9 @@ Project-URL: Source, https://github.com/chironmind/CentaurTechnicalIndicators-Py
 
 # Centaur Technical Indicators
 
-A production-ready Python library providing 60+ technical indicators for financial analysis, built on a high-performance Rust backend. 
+A production-ready Python library providing 50+ technical indicators for financial analysis, built on a high-performance Rust backend.
 
-Part of the Centaur Capital ecosystem.
+Part of the CRT (Centaur Research & Technologies) ecosystem.
 
 Looking for the Rust crate? See: [ChironMind/CentaurTechnicalIndicators-Rust](https://github.com/ChironMind/CentaurTechnicalIndicators-Rust)
 
@@ -58,7 +63,7 @@ import centaur_technical_indicators as cti
 
 prices = [100.2, 100.46, 100.53, 100.38, 100.19]
 
-ma = cti.moving_average(
+ma = cti.moving_average.single.moving_average(
     prices,
     "simple"
 )
@@ -116,9 +121,14 @@ $ pytest .
 ### Library Structure
 
 - Modules based on their analysis areas (**`moving_average`**, **`momentum_indicators`**, **`strength_indicators`**...)
-- `bulk` & `single` function variants  
+- Most modules have both `bulk` and `single` sub-modules:
   - `bulk`: Compute indicator over rolling periods, returns a list.
   - `single`: Compute indicator for the entire list, returns a single value.
+- **Exceptions (asymmetric shape):**
+  - `chart_trends` — flat module (no `single`/`bulk` sub-modules; functions are top-level).
+  - `volatility_indicators` — `volatility_system` is `bulk` only; `ulcer_index` has both.
+  - `other_indicators`, `strength_indicators`, and `trend_indicators` are asymmetric (not every
+    indicator has both variants).
 - `types` used to personalise the technical indicators (**`moving_average_type`**, **`deviation_model`**, **`constant_model_type`**...)
 
 ---
@@ -138,29 +148,32 @@ $ pytest .
 
 ## 📈 Available Indicators
 
-All indicators are grouped and split into modules based on their analysis area.  
-Each module has `bulk` (list output) and `single` (scalar output) functions.
+All indicators are grouped and split into modules based on their analysis area.
 
 ### Candle Indicators
-- Ichimoku Cloud, Moving Constant Bands/Envelopes, Donchian Channels, Keltner, Supertrend
+- Ichimoku Cloud, Moving Constant Bands/Envelopes, Donchian Channels, Keltner, Supertrend,
+  McGinley Dynamic Envelopes, McGinley Dynamic Bands
 
 ### Chart Trends
-- Trend break down, overall trends, peak/valley trends
+- Trend break down, overall trends, peak/valley trends, peak favorable move, valley favorable move
 
 ### Correlation Indicators
 - Correlate asset prices
 
 ### Momentum Indicators
-- Chaikin Oscillator, CCI, MACD, Money Flow Index, On Balance Volume, ROC, RSI, Williams %R
+- Chaikin Oscillator, CCI, MACD, Money Flow Index, On Balance Volume, ROC, RSI, Williams %R,
+  Stochastic Oscillator, Slow Stochastic, Slowest Stochastic, Percentage Price Oscillator (PPO),
+  Chande Momentum Oscillator (CMO), Signal Line (MACD signal),
+  McGinley Dynamic Commodity Channel Index, McGinley Dynamic MACD Line
 
 ### Moving Averages
 - McGinley Dynamic, Moving Average
 
 ### Other Indicators
-- ROI, True Range, ATR, Internal Bar Strength
+- ROI, True Range, ATR, Internal Bar Strength, Positivity Indicator
 
 ### Strength Indicators
-- Accumulation/Distribution, PVI, NVI, RVI
+- Accumulation/Distribution, PVI, NVI, RVI, Volume Index
 
 ### Trend Indicators
 - Aroon (Up/Down/Oscillator), Parabolic, DM, Volume-Price Trend, TSI
@@ -168,6 +181,10 @@ Each module has `bulk` (list output) and `single` (scalar output) functions.
 ### Volatility Indicators
 - Ulcer Index, Volatility System
 
+**Note on scope:** Statistical primitives available in Python's `statistics` / `math` modules
+(the Rust `basic_indicators` surface) are intentionally not re-bound. Use the standard library
+directly for those.
+
 ---
 
 ## 📊 Performance Benchmarks
@@ -248,7 +265,7 @@ This repository is part of a structured documentation suite:
 - 📕 **Tutorials:** — [See here](https://centaurtechnicalindicators-python.readthedocs.io/en/latest/tutorials/)
 - 📘 **How-To Guides:** — [See here](https://centaurtechnicalindicators-python.readthedocs.io/en/latest/howto/)
 - ⏱️ **Benchmarks:** — [See here](https://centaurtechnicalindicators-python.readthedocs.io/en/latest/benchmarks/)
-- 📙 **Explanations:** — [centaurlabs.pages.dev/](https://centaurlabs.pages.dev/)
+- 📙 **Explanations:** — [tech.centaurresearchtechnologies.com](https://tech.centaurresearchtechnologies.com/)
 - 📗 **Reference:** — [See here](https://centaurtechnicalindicators-python.readthedocs.io/en/latest/api/)
  
 ---

{centaur_technical_indicators-1.2.2 → centaur_technical_indicators-1.3.1}/README.md

@@ -11,9 +11,9 @@
 
 # Centaur Technical Indicators
 
-A production-ready Python library providing 60+ technical indicators for financial analysis, built on a high-performance Rust backend. 
+A production-ready Python library providing 50+ technical indicators for financial analysis, built on a high-performance Rust backend.
 
-Part of the Centaur Capital ecosystem.
+Part of the CRT (Centaur Research & Technologies) ecosystem.
 
 Looking for the Rust crate? See: [ChironMind/CentaurTechnicalIndicators-Rust](https://github.com/ChironMind/CentaurTechnicalIndicators-Rust)
 
@@ -36,7 +36,7 @@ import centaur_technical_indicators as cti
 
 prices = [100.2, 100.46, 100.53, 100.38, 100.19]
 
-ma = cti.moving_average(
+ma = cti.moving_average.single.moving_average(
     prices,
     "simple"
 )
@@ -94,9 +94,14 @@ $ pytest .
 ### Library Structure
 
 - Modules based on their analysis areas (**`moving_average`**, **`momentum_indicators`**, **`strength_indicators`**...)
-- `bulk` & `single` function variants  
+- Most modules have both `bulk` and `single` sub-modules:
   - `bulk`: Compute indicator over rolling periods, returns a list.
   - `single`: Compute indicator for the entire list, returns a single value.
+- **Exceptions (asymmetric shape):**
+  - `chart_trends` — flat module (no `single`/`bulk` sub-modules; functions are top-level).
+  - `volatility_indicators` — `volatility_system` is `bulk` only; `ulcer_index` has both.
+  - `other_indicators`, `strength_indicators`, and `trend_indicators` are asymmetric (not every
+    indicator has both variants).
 - `types` used to personalise the technical indicators (**`moving_average_type`**, **`deviation_model`**, **`constant_model_type`**...)
 
 ---
@@ -116,29 +121,32 @@ $ pytest .
 
 ## 📈 Available Indicators
 
-All indicators are grouped and split into modules based on their analysis area.  
-Each module has `bulk` (list output) and `single` (scalar output) functions.
+All indicators are grouped and split into modules based on their analysis area.
 
 ### Candle Indicators
-- Ichimoku Cloud, Moving Constant Bands/Envelopes, Donchian Channels, Keltner, Supertrend
+- Ichimoku Cloud, Moving Constant Bands/Envelopes, Donchian Channels, Keltner, Supertrend,
+  McGinley Dynamic Envelopes, McGinley Dynamic Bands
 
 ### Chart Trends
-- Trend break down, overall trends, peak/valley trends
+- Trend break down, overall trends, peak/valley trends, peak favorable move, valley favorable move
 
 ### Correlation Indicators
 - Correlate asset prices
 
 ### Momentum Indicators
-- Chaikin Oscillator, CCI, MACD, Money Flow Index, On Balance Volume, ROC, RSI, Williams %R
+- Chaikin Oscillator, CCI, MACD, Money Flow Index, On Balance Volume, ROC, RSI, Williams %R,
+  Stochastic Oscillator, Slow Stochastic, Slowest Stochastic, Percentage Price Oscillator (PPO),
+  Chande Momentum Oscillator (CMO), Signal Line (MACD signal),
+  McGinley Dynamic Commodity Channel Index, McGinley Dynamic MACD Line
 
 ### Moving Averages
 - McGinley Dynamic, Moving Average
 
 ### Other Indicators
-- ROI, True Range, ATR, Internal Bar Strength
+- ROI, True Range, ATR, Internal Bar Strength, Positivity Indicator
 
 ### Strength Indicators
-- Accumulation/Distribution, PVI, NVI, RVI
+- Accumulation/Distribution, PVI, NVI, RVI, Volume Index
 
 ### Trend Indicators
 - Aroon (Up/Down/Oscillator), Parabolic, DM, Volume-Price Trend, TSI
@@ -146,6 +154,10 @@ Each module has `bulk` (list output) and `single` (scalar output) functions.
 ### Volatility Indicators
 - Ulcer Index, Volatility System
 
+**Note on scope:** Statistical primitives available in Python's `statistics` / `math` modules
+(the Rust `basic_indicators` surface) are intentionally not re-bound. Use the standard library
+directly for those.
+
 ---
 
 ## 📊 Performance Benchmarks
@@ -226,7 +238,7 @@ This repository is part of a structured documentation suite:
 - 📕 **Tutorials:** — [See here](https://centaurtechnicalindicators-python.readthedocs.io/en/latest/tutorials/)
 - 📘 **How-To Guides:** — [See here](https://centaurtechnicalindicators-python.readthedocs.io/en/latest/howto/)
 - ⏱️ **Benchmarks:** — [See here](https://centaurtechnicalindicators-python.readthedocs.io/en/latest/benchmarks/)
-- 📙 **Explanations:** — [centaurlabs.pages.dev/](https://centaurlabs.pages.dev/)
+- 📙 **Explanations:** — [tech.centaurresearchtechnologies.com](https://tech.centaurresearchtechnologies.com/)
 - 📗 **Reference:** — [See here](https://centaurtechnicalindicators-python.readthedocs.io/en/latest/api/)
  
 ---