Untrack __pycache__ files (supersedes #21)

.github/actions/gitleaks/action.yml

@@ -0,0 +1,39 @@
+name: Gitleaks scan
+description: Downloads a checksum-verified gitleaks release and scans the commits introduced by the current push or pull request for secrets. Extracted so this repo's own CI and monorepo's synced copy of this repo can call the identical steps locally -- see the parent engagement README's "Sharing CI with the monorepo" pattern, established for infrastructure and applied here.
+
+inputs:
+  working-directory:
+    description: Directory whose git history and .gitleaks.toml config to scan
+    required: false
+    default: "."
+
+runs:
+  using: composite
+  steps:
+    - name: Install gitleaks
+      shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: |
+        set -euo pipefail
+        VER=8.21.2
+        curl -sSfL --max-time 60 -o gitleaks.tar.gz "https://github.com/gitleaks/gitleaks/releases/download/v${VER}/gitleaks_${VER}_linux_x64.tar.gz"
+        echo "5bc41815076e6ed6ef8fbecc9d9b75bcae31f39029ceb55da08086315316e3ba  gitleaks.tar.gz" | sha256sum -c -
+        tar -xzf gitleaks.tar.gz gitleaks
+        rm gitleaks.tar.gz
+        ./gitleaks version
+
+    - name: Scan new commits for secrets
+      shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: |
+        set -euo pipefail
+        if [ "${{ github.event_name }}" = "pull_request" ]; then
+          RANGE="${{ github.event.pull_request.base.sha }}..${{ github.sha }}"
+        elif [ "${{ github.event.before }}" = "0000000000000000000000000000000000000000" ]; then
+          RANGE="-1 ${{ github.sha }}"          # first push of a branch: scan tip commit
+        else
+          RANGE="${{ github.event.before }}..${{ github.sha }}"
+        fi
+        echo "Scanning commit range: $RANGE"
+        ./gitleaks detect --source . --log-opts="$RANGE" \
+          --config .gitleaks.toml --redact --verbose

.github/actions/test-minimal-install/action.yml

@@ -0,0 +1,29 @@
+name: Test minimal install
+description: Regression guard for the model_runner lazy-import bug -- a plain `pip install .`, with neither pandas nor pywr present, must still let create-synthetic-model run. Extracted so this repo's own CI and monorepo's synced copy of this repo can call the identical steps locally -- see the parent engagement README's "Sharing CI with the monorepo" pattern, established for infrastructure and applied here.
+
+inputs:
+  working-directory:
+    description: Directory containing the pywr_utils package to test
+    required: false
+    default: "."
+
+runs:
+  using: composite
+  steps:
+    - uses: actions/setup-python@v5
+      with:
+        python-version: "3.12"
+    - shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: pip install .
+    - shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: |
+        pywr-utils create-synthetic-model --zones 2 --transfers 1 --output /tmp/synthetic.json --show-summary
+        test -f /tmp/synthetic.json
+    - name: confirm pandas and pywr are genuinely absent
+      shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: |
+        ! python -c "import pandas" 2>/dev/null
+        ! python -c "import pywr" 2>/dev/null

.github/actions/test/action.yml

@@ -0,0 +1,41 @@
+name: Test
+description: Installs the package with its run/dev extras, runs the pytest suite, and uploads a coverage report. Extracted so this repo's own CI and monorepo's synced copy of this repo can call the identical steps locally -- see the parent engagement README's "Sharing CI with the monorepo" pattern, established for infrastructure and applied here.
+
+inputs:
+  working-directory:
+    description: Directory containing the pywr_utils package to test
+    required: false
+    default: "."
+
+runs:
+  using: composite
+  steps:
+    - uses: actions/setup-python@v5
+      with:
+        python-version: "3.12"
+    - shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      # pywr's lpsolve extension needs headers this runner doesn't have; glpk (also needed) is prebaked into the ci-runners image.
+      env:
+        PYWR_BUILD_LPSOLVE: "false"
+      run: pip install -e ".[run,dev]"
+    - shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: pytest -v
+    - name: write coverage summary
+      # Fully native, no admin-gated feature or third-party action needed: coverage.py's own markdown formatter piped into GitHub Actions' own step-summary mechanism. Shows up on every run's summary page (and one click away from the PR checks list) regardless of whether Code Quality is ever enabled.
+      if: always()
+      shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: |
+        echo '## Coverage' >> "$GITHUB_STEP_SUMMARY"
+        python -m coverage report --format=markdown >> "$GITHUB_STEP_SUMMARY"
+    - name: upload coverage report
+      if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository
+      uses: actions/upload-code-coverage@v1
+      with:
+        file: ${{ inputs.working-directory }}/coverage.xml
+        language: Python
+        label: code-coverage/pytest
+        # TEMPORARY: Code Quality isn't enabled for this repo yet (Settings > Security > Code quality) — that's an org/repo admin action, and neither CI nor a push-only collaborator can do it. Without this, the upload 403s and fails the whole job. Remove fail-on-error once an admin enables Code Quality and this step succeeds for real.
+        fail-on-error: false

.github/actions/typecheck/action.yml

@@ -0,0 +1,40 @@
+name: Typecheck and lint
+description: Runs mypy, ruff, vulture, bandit, and pip-audit against the Python package. Extracted so this repo's own CI and monorepo's synced copy of this repo can call the identical steps locally -- see the parent engagement README's "Sharing CI with the monorepo" pattern, established for infrastructure and applied here.
+
+inputs:
+  working-directory:
+    description: Directory containing the pywr_utils package to check
+    required: false
+    default: "."
+
+runs:
+  using: composite
+  steps:
+    - uses: actions/setup-python@v5
+      with:
+        python-version: "3.12"
+    - shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: pip install -e ".[dev]"
+    - shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: mypy pywr_utils/
+    - name: lint (ruff)
+      shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: ruff check .
+    - name: dead-code scan (vulture)
+      shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: vulture pywr_utils vulture_whitelist.py --min-confidence 80
+    - name: security scan (bandit)
+      shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: bandit -r pywr_utils
+    - name: dependency vulnerability scan (pip-audit)
+      shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      # pip itself is not a declared dependency, just whatever setup-python provisions; keep it current so a stale bundled pip doesn't produce a false CVE finding here.
+      run: |
+        pip install -U pip
+        pip-audit --skip-editable

.github/dependabot.yml

@@ -0,0 +1,23 @@
+version: 2
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    cooldown:
+      default-days: 7
+    groups:
+      python-dependencies:
+        patterns:
+          - "*"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    cooldown:
+      default-days: 7
+    groups:
+      github-actions:
+        patterns:
+          - "*"

.github/workflows/ci.yml

@@ -0,0 +1,36 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request: {}
+  workflow_dispatch: {}
+
+permissions:
+  contents: read
+  code-quality: write
+
+jobs:
+  typecheck:
+    runs-on: gha-ci-runners
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ./.github/actions/typecheck
+
+  test:
+    runs-on: gha-ci-runners
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event.pull_request.head.sha || github.sha }}
+      - uses: ./.github/actions/test
+
+  test-minimal-install:
+    # Regression guard for the model_runner lazy-import bug: a plain `pip install .`, with neither pandas nor pywr present, must still let create-synthetic-model run — only the `run` extra needs either.
+    runs-on: gha-ci-runners
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ./.github/actions/test-minimal-install

.github/workflows/gitleaks.yml

@@ -0,0 +1,22 @@
+name: gitleaks
+
+# Scan only the NEW commits of each push / PR for secrets, matching the pattern already established on cluster-api-v2. No known historical-secret backlog exists in this repo, but scanning new commits only (rather than full history on every run) keeps this consistent with the rest of the org and cheap to run.
+on:
+  pull_request:
+  push:
+    branches: [main]
+  workflow_dispatch: {}
+
+permissions:
+  contents: read
+
+jobs:
+  gitleaks:
+    # Self-hosted fleet: the org's billing block stops GitHub-hosted jobs, and the runner container has no sudo -- the binary runs from the workspace by path.
+    runs-on: gha-ci-runners
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: ./.github/actions/gitleaks