valcore 0.0.1__tar.gz

valcore-0.0.1/.github/workflows/release.yml

@@ -0,0 +1,117 @@
+name: release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  build-and-publish:
+    runs-on: ubuntu-latest
+    permissions:
+      # Declaring any permissions block replaces the default set, so contents:
+      # read must be listed explicitly -- actions/checkout cannot clone a
+      # private repo without it, and reports the failure as "Repository not
+      # found" rather than as a permission error.
+      contents: read
+      # Required for PyPI trusted publishing (OIDC). No API token is stored.
+      id-token: write
+    steps:
+      - name: Check out the tagged commit
+        uses: actions/checkout@v4
+
+      - name: Verify the tag matches the packaged version
+        run: |
+          # uv build takes the version from pyproject.toml while the formula URL
+          # is derived from the tag. If they disagree, the emitted stanza points
+          # at a file that was never published -- fail here, not after publishing.
+          tag_version="${GITHUB_REF_NAME#v}"
+          pkg_version=$(grep -m1 '^version' pyproject.toml | cut -d'"' -f2)
+          if [ "$tag_version" != "$pkg_version" ]; then
+            echo "::error::tag ${GITHUB_REF_NAME} implies version ${tag_version}, but pyproject.toml declares ${pkg_version}. Bump pyproject.toml or retag."
+            exit 1
+          fi
+          echo "tag and package version agree: ${pkg_version}"
+
+      - name: Set up Node 20
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+
+      - name: Set up Python 3.12
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Build the SPA
+        run: |
+          cd web
+          npm ci
+          npm run build
+
+      - name: Stage the built SPA inside the package
+        run: |
+          mkdir -p src/valcore/web_dist
+          cp -r web/dist/* src/valcore/web_dist/
+
+      - name: Build the wheel and sdist
+        run: uv build
+
+      - name: Verify the wheel ships the API and the built UI
+        run: |
+          contents=$(unzip -l dist/*.whl)
+          echo "$contents"
+          if ! echo "$contents" | grep -q "valcore/api/"; then
+            echo "::error::wheel is missing valcore/api/ — the API layer did not ship"
+            exit 1
+          fi
+          if ! echo "$contents" | grep -q "valcore/web_dist/index.html"; then
+            echo "::error::wheel is missing valcore/web_dist/index.html — the UI did not ship"
+            exit 1
+          fi
+          echo "wheel contains both valcore/api/ and valcore/web_dist/index.html"
+
+      - name: Publish to PyPI (trusted publishing)
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+      - name: Emit the Homebrew formula stanza in the job summary
+        run: |
+          # The formula downloads the PyPI sdist, so hash exactly that file.
+          # These bytes are what the publish step uploaded, and PyPI artifacts
+          # are immutable -- so this sha256 stays valid forever.
+          tarball=$(ls dist/*.tar.gz)
+          sha=$(sha256sum "$tarball" | cut -d' ' -f1)
+          version="${GITHUB_REF_NAME#v}"
+          url="https://files.pythonhosted.org/packages/source/v/valcore/valcore-${version}.tar.gz"
+          {
+            echo "## Homebrew formula stanza"
+            echo ""
+            echo "Paste into \`Formula/valcore.rb\` in duncankmckinnon/homebrew-tap:"
+            echo ""
+            echo '```ruby'
+            echo "  url \"${url}\""
+            echo "  sha256 \"${sha}\""
+            echo '```'
+            echo ""
+            echo "The release does not auto-publish a formula; open that PR by hand."
+          } >> "$GITHUB_STEP_SUMMARY"
+
+      - name: Verify the published sdist matches the hash we emitted
+        run: |
+          # Guards against publishing a formula stanza that brew cannot verify.
+          version="${GITHUB_REF_NAME#v}"
+          url="https://files.pythonhosted.org/packages/source/v/valcore/valcore-${version}.tar.gz"
+          local_sha=$(sha256sum dist/*.tar.gz | cut -d' ' -f1)
+          for attempt in 1 2 3 4 5; do
+            remote_sha=$(curl -sfL "$url" | sha256sum | cut -d' ' -f1) && break
+            echo "sdist not visible on PyPI yet (attempt ${attempt}); waiting…"
+            sleep 15
+          done
+          if [ "$remote_sha" != "$local_sha" ]; then
+            echo "::error::published sdist sha256 ($remote_sha) != built sdist ($local_sha)"
+            exit 1
+          fi
+          echo "published sdist matches: $local_sha"

valcore-0.0.1/.gitignore

@@ -0,0 +1,230 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+.serena/*
+.claude/*
+.workbench/*
+
+docs/superpowers/*
+
+# valcore local state
+valcore.db
+valcore.db-shm
+valcore.db-wal
+valcore.db*
+web/dist/

valcore-0.0.1/.python-version

@@ -0,0 +1 @@
+3.12

valcore-0.0.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

valcore-0.0.1/PKG-INFO

@@ -0,0 +1,131 @@
+Metadata-Version: 2.4
+Name: valcore
+Version: 0.0.1
+Summary: A small, self-contained local tool for developing, improving, and running agentic evaluations.
+License-File: LICENSE
+Requires-Python: >=3.12
+Requires-Dist: click
+Requires-Dist: fastapi
+Requires-Dist: pydantic-ai-harness[code-mode]<1,>=0.12
+Requires-Dist: pydantic-ai<3,>=2.19
+Requires-Dist: pydantic-settings
+Requires-Dist: python-multipart
+Requires-Dist: sqlmodel
+Requires-Dist: uvicorn[standard]
+Description-Content-Type: text/markdown
+
+# valcore
+
+A small, self-contained local tool for developing, improving, and running agentic
+evaluations. Author evaluators in a web UI, run them over datasets from the command
+line, and gate CI on their accuracy.
+
+## Install
+
+With Homebrew:
+
+```bash
+brew install duncankmckinnon/tap/valcore
+```
+
+Or as a `uv` tool:
+
+```bash
+uv tool install valcore
+```
+
+Either way you get an `valcore` command on your `PATH`.
+
+## Quickstart
+
+Store your gateway API key, then start the app:
+
+```bash
+valcore config set-key sk-...
+valcore serve
+```
+
+`serve` starts the web UI and API on <http://127.0.0.1:8000> and opens a browser
+(pass `--no-browser` to skip that, or `--port` to bind elsewhere). Author evaluators
+and datasets in the UI, then drive runs from the command line.
+
+The gateway key is stored in `~/.valcore/config.toml` (mode `0600`) and exported to
+pydantic-ai as `PYDANTIC_AI_GATEWAY_API_KEY` when a command runs. An already-exported
+environment variable always wins over the stored key. Run `valcore config set-key`
+with no argument to be prompted without echoing the key.
+
+## Commands
+
+| Command | What it does |
+| --- | --- |
+| `valcore serve` | Serve the web UI and API (`--port`, `--host`, `--no-browser`). |
+| `valcore list <evaluators\|datasets\|runs>` | List resources as a table or, with `--json`, as JSON. |
+| `valcore run <evaluator> <dataset>` | Run an evaluator version over a dataset. |
+| `valcore export <evaluator>` | Export an evaluator version as a standalone Python script. |
+| `valcore config set-key [KEY]` | Store the gateway API key in the config file. |
+| `valcore config get` | Show the current config (the key is masked unless `--show-key`). |
+| `valcore config path` | Print the path to the config file. |
+| `valcore config edit` | Open the config file in `$EDITOR`. |
+| `valcore version` | Print the installed valcore version. |
+
+Evaluators, versions, and datasets are addressable by name or by a unique id prefix;
+an ambiguous value is an error that lists the candidates. Pass `--db PATH` on the group
+to point at a SQLite database other than the default under `~/.valcore`.
+
+`run` accepts `--version` (defaults to the active version), `--kind`, `--concurrency`,
+`--watch` (one line per completed row), `--json`, and `--min-accuracy`. Progress goes to
+stderr and results go to stdout, so redirecting stdout yields clean JSON. The CLI talks
+to SQLite directly, so `run` works whether or not `serve` is up.
+
+## Using valcore in CI
+
+`run --json` emits a single object with run metadata, metrics, and per-row scores, and
+`--min-accuracy` turns a validation run into a pass/fail gate:
+
+```bash
+valcore run my-evaluator my-dataset \
+  --kind validation \
+  --min-accuracy 0.9 \
+  --json > run.json
+```
+
+Exit codes:
+
+| Exit | Meaning |
+| --- | --- |
+| `0` | The run finished and, if `--min-accuracy` was set, accuracy met the threshold. |
+| `1` | The run failed, or a domain error occurred (printed as `error: <message>` on stderr). |
+| `2` | Accuracy fell below `--min-accuracy`. |
+
+`--min-accuracy` requires a categorical accuracy metric; numeric or unlabeled runs have
+no accuracy and error rather than silently passing.
+
+## `~/.valcore`
+
+All state lives under `~/.valcore` (mode `0700`). Set `VALCORE_HOME` to relocate it.
+
+```
+~/.valcore/              0700
+  config.toml              0600  gateway key + defaults
+  valcore.db             SQLite (plus -wal, -shm)
+  logs/                    serve logs
+```
+
+## Development
+
+```bash
+uv sync                    # install dependencies into a local venv
+uv run pytest              # run the test suite
+```
+
+The web UI is a Vite + React SPA under `web/`:
+
+```bash
+cd web
+npm install
+npm run dev                # Vite dev server, proxying the API
+```
+
+To build the SPA into the wheel, run `npm run build` and copy `web/dist/` into
+`src/valcore/web_dist/` before `uv build`; the release workflow does this automatically
+on a `v*` tag.