backtest360 0.1.0__tar.gz

backtest360-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,30 @@
+---
+name: Bug report
+about: Report a problem with the SDK
+title: ''
+labels: bug
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what went wrong.
+
+**Reproduction**
+A minimal code snippet that triggers the issue:
+
+```python
+from backtest360 import Client, Strategy
+# ...
+```
+
+**Expected behavior**
+What you expected to happen.
+
+**Environment**
+- `backtest360` version: <!-- python -c "import backtest360; print(backtest360.__version__)" -->
+- Python version:
+- OS:
+
+**Additional context**
+Any error output (a `Backtest360Error` `status`/`code`/`request_id` is especially
+helpful), logs, or context.

backtest360-0.1.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an improvement or new capability
+title: ''
+labels: enhancement
+assignees: ''
+---
+
+**What problem are you trying to solve?**
+A clear description of the use case or limitation you've run into.
+
+**Proposed solution**
+What you'd like the SDK to do.
+
+**Alternatives considered**
+Any workarounds or alternative approaches you've thought about.
+
+**Additional context**
+Anything else that would help us understand the request.

backtest360-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+## Summary
+
+<!-- What does this PR change, and why? -->
+
+## Type of change
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Documentation
+- [ ] Breaking change
+
+## Checklist
+
+- [ ] Tests added or updated, and `pytest -q` passes
+- [ ] `ruff check src tests` passes
+- [ ] Docs updated (docstrings / `docs/` / `README.md`) if public behaviour changed
+- [ ] `CHANGELOG.md` entry added under `Unreleased`

backtest360-0.1.0/.github/workflows/docs.yml

@@ -0,0 +1,27 @@
+name: Deploy docs
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: write
+
+jobs:
+  deploy:
+    name: Build and deploy MkDocs to GitHub Pages
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install docs dependencies
+        run: pip install -e ".[docs]"
+
+      - name: Build and deploy docs
+        run: mkdocs gh-deploy --force

backtest360-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,64 @@
+name: release
+
+on:
+  push:
+    tags:
+      - "v*.*.*"
+
+permissions:
+  contents: write
+  id-token: write  # required for OIDC trusted publishing
+
+jobs:
+  test:
+    uses: ./.github/workflows/test.yml
+
+  publish:
+    name: publish to PyPI
+    needs: test
+    runs-on: ubuntu-latest
+    environment: pypi
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Build
+        run: |
+          pip install build
+          python -m build
+
+      - name: Check dist
+        run: |
+          pip install twine
+          twine check dist/*
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        # OIDC trusted publishing — no token stored
+
+  release-notes:
+    name: GitHub release
+    needs: publish
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Create GitHub release
+        uses: softprops/action-gh-release@v2
+        with:
+          # Release notes are driven by CHANGELOG.md, not auto-generated from
+          # PR/commit history (auto-gen may surface internal commit messages).
+          generate_release_notes: false
+          body: |
+            See [CHANGELOG.md](https://github.com/Backtest360/backtest360/blob/main/CHANGELOG.md) for full release notes.

backtest360-0.1.0/.github/workflows/test.yml

@@ -0,0 +1,60 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_call:
+
+jobs:
+  test:
+    name: "py${{ matrix.python-version }}"
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.9", "3.10", "3.11", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install
+        run: pip install -e ".[dev]"
+
+      - name: Lint (ruff)
+        run: ruff check src tests
+
+      - name: Test
+        run: pytest -q
+
+      - name: Syntax-check examples
+        run: python -m compileall examples/
+
+  integration:
+    # Runs only on pull requests (not push-to-main) to avoid consuming API
+    # quota on every commit. The BACKTEST360_API_KEY secret must be set in
+    # repository Settings → Secrets and variables → Actions. Fork PRs skip
+    # the "Integration tests" step automatically because they cannot access
+    # repository secrets.
+    name: integration
+    runs-on: ubuntu-latest
+    if: github.event_name == 'pull_request'
+    env:
+      BACKTEST360_API_KEY: ${{ secrets.BACKTEST360_API_KEY }}
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install
+        run: pip install -e ".[dev]"
+
+      - name: Integration tests
+        if: env.BACKTEST360_API_KEY != ''
+        run: pytest -q -m integration

backtest360-0.1.0/.gitignore

@@ -0,0 +1,50 @@
+# Python
+__pycache__/
+*.py[cod]
+*.pyo
+*.pyd
+*.so
+*.egg
+*.egg-info/
+dist/
+build/
+.eggs/
+*.whl
+
+# Virtual envs
+.venv/
+venv/
+env/
+
+# Testing
+.pytest_cache/
+.coverage
+htmlcov/
+coverage.xml
+
+# Type checking
+.mypy_cache/
+
+# Ruff
+.ruff_cache/
+
+# Hatch / build
+.hatch/
+
+# Docs
+public/
+site/
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Local agent / assistant config — never commit to this public repo
+CLAUDE.md
+.claude/

backtest360-0.1.0/CHANGELOG.md

@@ -0,0 +1,46 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+---
+
+## [0.1.0] — 2026-06-07
+
+Initial public release.
+
+### Added
+
+- `Client` — synchronous HTTP wrapper over the public Backtest360 API.
+  Methods: `backtest`, `backtest_signals`, `backtest_raw`, `latest_signal`,
+  `validate_strategy`, `list_strategies`, `list_indicators`, `version`, `health`.
+- `Strategy` — strategy builder with boolean expression strings
+  (`long_entry`, `long_exit`, `short_entry`, `short_exit`) and indicator descriptors.
+  Pre-built templates: `rsi_threshold_long`, `rsi_mean_reversion`, `ma_crossover`,
+  `momentum_6m_long`.
+- `Execution` — execution timing dataclass (`entry`, `exit`, `signal_frequency`,
+  `entry_window`, `exit_window`, `entry_fill`, `exit_fill`).
+- `Costs` — transaction costs dataclass (`slippage_bps`, `fee_pct`,
+  `vol_scaled_slippage`, `vol_slippage_lookback`).
+- `Risk` — stop-loss and drawdown protection dataclass (`stop`, `value`,
+  `atr_period`, `reentry`, `cooldown_bars`, `max_drawdown`).
+- `Sizing` — position sizing dataclass (`weight`, `vol_target`,
+  `vol_target_lookback`, `leverage_limit`).
+- `MarketHours` — daily anchor-hour config for sub-daily execution
+  (`open_hour`, `close_hour`, `strict_anchors`).
+- `Settings` — engine-level run settings (`risk_free_rate`, `random_seed`,
+  `on_bad_data`).
+- `Result` — response wrapper with `stats`, `trades`, `strategy_equity`,
+  `benchmark_equity`, `returns`, `signals`, `summary()`, and `raw`.
+- `Backtest360Error` — single exception with `status`, `code`, `body`,
+  `request_id`. Machine-readable codes: `SDK_NO_API_KEY`, `SDK_PATH_FORBIDDEN`,
+  `SDK_INVALID_SIGNALS`, `SDK_MALFORMED_RESPONSE`.
+- `BACKTEST360_API_KEY` and `BACKTEST360_ENGINE_URL` environment variables.
+- `py.typed` marker — first-class mypy / pyright support.
+- MIT license.
+
+<!-- Link references -->
+
+[0.1.0]: https://github.com/Backtest360/backtest360/releases/tag/v0.1.0

backtest360-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,59 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes
+- Focusing on what is best for the overall community
+
+Examples of unacceptable behavior:
+
+- The use of sexualized language or imagery, and sexual attention or advances
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards and
+will take appropriate and fair corrective action in response to any behavior
+that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+**hello@backtest360.com**. All complaints will be reviewed and investigated
+promptly and fairly. Community leaders are obligated to respect the privacy and
+security of the reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+[homepage]: https://www.contributor-covenant.org

backtest360-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,61 @@
+# Contributing
+
+Thanks for your interest in improving `backtest360`. This document covers
+the development setup and the conventions the project follows.
+
+## Development setup
+
+```bash
+git clone https://github.com/Backtest360/backtest360.git
+cd backtest360
+pip install -e ".[dev]"
+```
+
+This installs the SDK in editable mode along with the development tools
+(`pytest`, `pytest-cov`, `ruff`).
+
+## Running the checks
+
+```bash
+pytest -q                 # unit tests
+ruff check src tests      # lint
+```
+
+Both must pass before a pull request can be merged. The unit suite is fully
+mocked — it never makes network calls and does not require an API key.
+
+Live integration tests are excluded from the default run. To exercise them
+against a real engine, set `BACKTEST360_API_KEY` and select the marker:
+
+```bash
+export BACKTEST360_API_KEY=b360_...
+pytest -q -m integration
+```
+
+## Pull requests
+
+- **One topic per branch.** Keep unrelated changes in separate pull requests.
+- **Add tests** for any new behaviour or bug fix.
+- **Update the docs** (`docs/`, docstrings, `README.md`) when you change public
+  behaviour.
+- **Add a `CHANGELOG.md` entry** under the `Unreleased` heading describing the
+  change (`Added` / `Changed` / `Fixed` / `Breaking` / `Removed`).
+- Keep the public surface minimal — this SDK talks to the engine over the
+  versioned HTTP API only.
+
+## Versioning
+
+The project follows [semantic versioning](https://semver.org/): `MAJOR.MINOR.PATCH`.
+Pre-1.0, breaking changes bump the `MINOR` version. Pre-release suffixes are
+`aN` (alpha), `bN` (beta), and `rcN` (release candidate).
+
+## Reporting bugs
+
+Open an issue at
+[github.com/Backtest360/backtest360/issues](https://github.com/Backtest360/backtest360/issues)
+with a minimal reproduction. For security issues, see [SECURITY.md](SECURITY.md)
+— please do not file them publicly.
+
+## Questions
+
+Reach us at hello@backtest360.com.

backtest360-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Backtest360
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.