v0.5.0

.github/workflows/ci.yml

@@ -11,21 +11,20 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Set up Python
-        uses: actions/setup-python@v5
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
         with:
+          enable-cache: true
           python-version: "3.11"
 
       - name: Install dependencies
-        run: |
-          python -m pip install --upgrade pip
-          python -m pip install -e ".[dev]"
+        run: uv sync --extra dev
 
       - name: Run mypy
-        run: mypy tradedesk
+        run: uv run mypy tradedesk
 
       - name: Run ruff
-        run: ruff check tradedesk
+        run: uv run ruff check tradedesk
 
   test:
     name: Test Python ${{ matrix.python-version }}
@@ -39,20 +38,19 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Set up Python
-        uses: actions/setup-python@v5
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
         with:
+          enable-cache: true
           python-version: ${{ matrix.python-version }}
 
-      - name: Install
-        run: |
-          python -m pip install --upgrade pip
-          python -m pip install -e ".[dev]"
+      - name: Install dependencies
+        run: uv sync --extra dev
 
       - name: Run tests with coverage
         run: |
-          pytest \
+          uv run pytest \
             --cov=tradedesk \
             --cov-report=term-missing \
             --cov-report=xml \
-            --cov-fail-under=80
+            --cov-fail-under=85

.github/workflows/publish.yml

@@ -18,16 +18,13 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Set up Python
-        uses: actions/setup-python@v5
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
         with:
           python-version: "3.14"
 
-      - name: Install build dependencies
-        run: python -m pip install --upgrade build
-
       - name: Build package
-        run: python -m build
+        run: uv build
 
       - name: Publish to PyPI
         uses: pypa/gh-action-pypi-publish@release/v1

AGENTS.md

@@ -1,45 +1,3 @@
-## Project Overview
-
-**tradedesk** is the shared research and orchestration layer that underpins multiple trading implementations. It provides common abstractions for data handling, backtesting, portfolio orchestration, analytics, and experiment management.
-
-This codebase is **not broker-specific**. It exists to:
-
-* Enable fast, repeatable strategy research
-* Provide realistic portfolio-level backtesting
-* Act as the canonical home for shared logic and metrics
-
-Downstream projects should depend on *tradedesk*; *tradedesk* should not depend on them.
-
----
-
-## Primary Responsibilities
-
-Agents should treat *tradedesk* as responsible for:
-
-* Backtest orchestration and experiment flow
-* Strategy-agnostic portfolio logic
-* Trade recording, ledgers, and metrics
-* Naming, configuration, and reproducibility conventions
-* Research-grade correctness over execution convenience
-
-If logic is reusable across brokers or execution environments, it likely belongs here.
-
----
-
-## Current Objectives
-
-Typical work includes:
-
-* Closing meaningful unit test coverage gaps
-* Hardening portfolio and analytics logic
-* Simplifying or clarifying orchestration flows
-* Removing legacy or leaked execution concerns
-* Ensuring deterministic, explainable backtest results
-
-Backward compatibility is **not required** unless explicitly stated.
-
----
-
 ## Preferred Way of Working
 
 ### Incremental and Focused
@@ -57,29 +15,22 @@ Backward compatibility is **not required** unless explicitly stated.
 ### Pragmatic Testing
 
 * Tests should defend correctness, not chase coverage
-* Prioritise:
-
-  * Portfolio aggregation logic
-  * Metrics and statistics
-  * Edge cases and boundary conditions
 * Avoid brittle, over-specified tests
+* Use `pytest` not `unittest`
 
 ### Communication Style
 
 * Concise, technical, professional
 * Minimal narration
-* Challenge assumptions where appropriate
+* Challenge assumptions - constructive dialog and pushback is expected
 
 ---
 
 ## Coding Expectations
 
 * Use latest stable Python and dependencies
 * Follow current documentation and APIs
-* No `from __future__ import ...` unless warranted
-* Prefer clarity and correctness over abstraction
-* Avoid premature generalisation
-* Code should meet `ruff check` and `mypy --strict` requirements
+* Code should pass `ruff check` and `mypy --strict` requirements
 * Create commit messages for git following "Conventional Commits" and the current style of the project's git log
   * Do not add author lines to git commits
 * Follow the intentions of the domain architecture encoded in `pyproject.toml`
@@ -89,37 +40,5 @@ Backward compatibility is **not required** unless explicitly stated.
 
 When running code or commands:
 
-* Use the `.venv` directory in the root of the relevant project
-
----
-
-## Domain Assumptions
-
-Agents are expected to understand:
-
-* Backtesting mechanics and common biases
-* Portfolio-level statistics and drawdown analysis
-* Event-driven strategy evaluation
-* The difference between research code and execution code
-
-If a design choice trades realism for speed or simplicity, it should be explicit.
-
----
-
-## What to Avoid
-
-* Broker- or API-specific logic
-* Leaking execution assumptions into research layers
-* Over-engineering for hypothetical future needs
-* Large rewrites without alignment
-
----
-
-## Success Criteria
-
-An agent is succeeding if it:
-
-* Increases confidence in backtest results
-* Improves clarity of portfolio and metrics logic
-* Makes research workflows faster and safer
-* Keeps the codebase cleanly reusable downstream
+* Use `uv` instead of `pip`
+* Always use the `.venv` directory in the root of the project