tolokaforge-models 1.0.0__tar.gz

tolokaforge_models-1.0.0/.gitignore

@@ -0,0 +1,112 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+keys.txt
+keys2.txt
+
+# Virtual environments
+venv/
+ENV/
+/env/
+.venv
+
+# Testing
+.pytest_cache/
+.coverage
+htmlcov/
+.tox/
+.mypy_cache/
+.ruff_cache/
+
+# IDEs
+.idea/
+*.swp
+*.swo
+*~
+
+# Environment
+.env
+.env.local
+
+# Wheel resolver cache
+.workbench/wheel-cache/
+
+# Scratch plans (plans do not live in the repo — architects and milestone
+# integration journals write to ~/.claude/plans/toloka-tolokaforge/ outside
+# the tree; the on-disk artefacts flow into PR bodies via --body-file).
+plans/
+
+# Release build artifacts
+release_output/
+
+# Results and outputs
+results/
+finished_runs/
+amzn_delivery/
+
+# Replay output, wherever the corpus it was read from lives. `retrace`, `reconcile` and judge
+# replay each write under their own --source, which for a committed corpus (tests/data/
+# migration_corpora/**, tests/data/projects/**) is inside the tree — so these are ignored at
+# any depth rather than only under results/. `--dry-run` is the invocation that writes nothing.
+trace_replay/
+reconcile/
+replays/
+
+# Output directory (benchmark results, generated reports)
+# NOTE: output/ is a working directory, not committed
+/output/
+
+# CI shard configs (generated by eval-orchestrator split)
+.ci/
+
+*.log
+!tasks/**/fixtures/*.log
+!tests/canonical/golden/**/*.log
+
+# TypeSense data
+.cache/
+typesense-data/
+
+# Docker
+.docker/
+
+# OS
+.DS_Store
+Thumbs.db
+project-m-copilot-mock-tools.zip
+tau-bench-main.zip
+
+# Internal/local-only workspace artifacts (not part of OSS harness)
+_private/
+
+# Converted task outputs
+converted/
+temp/
+.claude/*
+# Shared agent/skill definitions are part of the repo
+!.claude/agents/
+!.claude/hooks/
+!.claude/skills/
+!.claude/settings.json
+
+# Devcontainer
+devcontainer-lock.json

tolokaforge_models-1.0.0/CHANGELOG.md

@@ -0,0 +1,50 @@
+# Changelog
+
+All notable changes to `tolokaforge-models` are documented in this file.
+The wheel follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html);
+its release cadence is orthogonal to the `tolokaforge` engine wheel's own
+`vX.Y.Z` tag axis. See
+[`docs/RELEASING.md`](https://github.com/Toloka/tolokaforge/blob/main/docs/RELEASING.md#pypi-package--tolokaforge-models-models-vxyz-automated).
+
+## v1.0.0 (unreleased)
+
+Initial release. Publishes the `tolokaforge-models` wheel as a sibling of
+the `tolokaforge` engine wheel, carrying the model-data tables and the
+per-model policy / certificate surface the engine reaches through the
+seam module at
+[`tolokaforge.core.model_data`](https://github.com/Toloka/tolokaforge/blob/main/tolokaforge/core/model_data.py).
+
+### Feat
+
+- **data**: bundles `pricing.json`, `model_presets.yaml`, and
+  `providers.yaml` under
+  [`tolokaforge_models/data/`](https://github.com/Toloka/tolokaforge/tree/main/tolokaforge_models/src/tolokaforge_models/data).
+  The engine resolves them via `bundled_pricing_path()`,
+  `bundled_presets_path()`, and `bundled_providers_path()` — see
+  [`docs/RELEASING.md § Downstream data-resource consumers`](https://github.com/Toloka/tolokaforge/blob/main/docs/RELEASING.md#downstream-data-resource-consumers).
+- **certificates**: exports the 39 `ModelCertificate` entries in
+  `tolokaforge_models.certificates.ALL_MODELS`. The engine's
+  `tolokaforge.testing.certify` seam reads the tuple through
+  `tolokaforge.core.model_data.bundled_certificates()`.
+- **policies**: ships eight per-model policy subclasses across
+  `tolokaforge_models/policies/{gemini,minimax,deepseek,inkling}.py`
+  (`GeminiSchema`, `GeminiRecursiveSchema`, `ScalarArrayDictMapResponse`,
+  `RefResolvingDictMapHints`, `JsonRecursiveCoerceResponse`,
+  `ItemRecursiveUnwrapResponse`, `MinimaxM3TagRecoveryResponse`,
+  `OpenAISummaryReplayReasoningCodec`).
+- **loader**: declares the `tolokaforge.policies` entry-point group
+  (see `[project.entry-points."tolokaforge.policies"]` in
+  `pyproject.toml`). The engine's
+  `tolokaforge.core.model_data.load_policy_registrations()` merges these
+  into `_POLICY_REGISTRIES` at engine import time; duplicate keys or
+  unknown slots fail loud.
+- **api-version**: `__api_version__ = 1` is the integer version of the
+  loader contract between this wheel and the engine. Bumped whenever the
+  engine-side loader must change to keep reading this wheel's
+  registrations.
+- **minimum-engine-version**:
+  `minimum_engine_version = ">=0.17,<1.0"`. The engine reads this PEP
+  440 specifier at `tolokaforge.core.llm.presets` import via
+  `_check_minimum_engine_version()` and refuses to boot on an installed
+  engine that does not satisfy it — see
+  [`docs/RELEASING.md § Bumping minimum_engine_version on the models wheel`](https://github.com/Toloka/tolokaforge/blob/main/docs/RELEASING.md#bumping-minimum_engine_version-on-the-models-wheel).

tolokaforge_models-1.0.0/PKG-INFO

@@ -0,0 +1,17 @@
+Metadata-Version: 2.5
+Name: tolokaforge-models
+Version: 1.0.0
+Summary: Model data and per-model policy subclasses for tolokaforge.
+Author: Renaud de la Gueronniere, Tolokaforge Contributors
+License: Apache-2.0
+Keywords: benchmark,llm,models,tool-use
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.10

tolokaforge_models-1.0.0/pyproject.toml

@@ -0,0 +1,84 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "tolokaforge-models"
+version = "1.0.0"
+description = "Model data and per-model policy subclasses for tolokaforge."
+requires-python = ">=3.10"
+license = {text = "Apache-2.0"}
+authors = [
+    {name = "Renaud de la Gueronniere"},
+    {name = "Tolokaforge Contributors"},
+]
+keywords = ["llm", "benchmark", "tool-use", "models"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Intended Audience :: Science/Research",
+    "License :: OSI Approved :: Apache Software License",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+]
+
+# No hard ``Requires-Dist: tolokaforge`` on purpose. The
+# ``tolokaforge`` Python package this wheel imports at load time is
+# provided by two independent PyPI distributions in different install
+# contexts: the ``tolokaforge`` engine wheel on host installs, and the
+# Docker-only ``tolokaforge-runner-subset`` wheel inside the runner
+# container. A hard pip-level dep on ``tolokaforge`` would refuse to
+# resolve in the subset context (subset's distribution name is
+# ``tolokaforge-runner-subset``). Version pairing is enforced by
+# ``tolokaforge.core.model_data._check_minimum_engine_version`` at import
+# time against :data:`tolokaforge_models.minimum_engine_version` — that
+# gate is fail-loud, actionable, and independent of the pip resolver.
+dependencies = []
+
+[project.entry-points."tolokaforge.policies"]
+# key = "<slot>.<policy-name>" ; value = "<module>:<class>"
+"schema_sanitizer.gemini" = "tolokaforge_models.policies.gemini:GeminiSchema"
+"schema_sanitizer.gemini_recursive" = "tolokaforge_models.policies.gemini:GeminiRecursiveSchema"
+"prompt_policy.dict_map_hints_ref" = "tolokaforge_models.policies.inkling:RefResolvingDictMapHints"
+"response_policy.scalar_array_dict_map" = "tolokaforge_models.policies.gemini:ScalarArrayDictMapResponse"
+"response_policy.minimax_m3_tags" = "tolokaforge_models.policies.minimax:MinimaxM3TagRecoveryResponse"
+"reasoning_codec.openai_summary_replay" = "tolokaforge_models.policies.deepseek:OpenAISummaryReplayReasoningCodec"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/tolokaforge_models"]
+
+# =============================================================================
+# Release tooling (commitizen) — drives the `Release tolokaforge-models
+# (cz bump)` workflow. `cz bump` reads/writes the single version literal in
+# `[project] version`, regenerates `CHANGELOG.md` from Conventional Commits,
+# commits, and tags `models-vX.Y.Z`. Independent of the engine's own
+# `[tool.commitizen]` block in the workspace-root `pyproject.toml`.
+# See `docs/RELEASING.md` ("Cutting a tolokaforge-models release").
+# =============================================================================
+
+[tool.commitizen]
+name = "cz_conventional_commits"
+version_provider = "pep621"          # read/write [project] version in place
+tag_format = "models-v$version"      # matches the `models-v*` trigger in publish-tolokaforge-models.yml
+changelog_file = "CHANGELOG.md"      # relative to this pyproject's directory
+version_files = [
+    "src/tolokaforge_models/__init__.py:__version__",
+]
+update_changelog_on_bump = true
+changelog_incremental = true         # only prepend new sections; never rewrite hand-written history
+bump_message = "chore(models-release): bump tolokaforge-models to $new_version"
+annotated_tag = true
+
+# Keep the workspace-root `uv.lock` in step with the models version bump.
+# `cz bump` writes the new version literal but does not relock; without this
+# the lockfile would pin the previous version. `uv lock` regenerates the
+# workspace root's lock from any workspace member. `pre_bump_hooks` run after
+# the version write and before cz's commit, so cz folds the staged lockfile
+# into the same release commit.
+pre_bump_hooks = [
+    "uv lock",
+    "git add -- ../uv.lock",
+]

tolokaforge_models-1.0.0/src/tolokaforge_models/__init__.py

@@ -0,0 +1,35 @@
+"""Model data and per-model policy subclasses for tolokaforge.
+
+This wheel ships the bundled ``pricing.json``, ``model_presets.yaml``,
+and ``providers.yaml`` tables, plus the per-model policy subclasses
+and the ``ModelCertificate`` registry that
+the engine consumes through its light seam in
+:mod:`tolokaforge.core.model_data`.
+
+The wheel imports no first-party engine module at load time; a repo
+that has never installed :mod:`tolokaforge` can still ``import
+tolokaforge_models`` and read the three constants below.
+"""
+
+from __future__ import annotations
+
+from typing import Final
+
+__all__ = [
+    "__api_version__",
+    "__version__",
+    "minimum_engine_version",
+]
+
+__version__: Final[str] = "1.0.0"
+"""PEP 440 version of the models wheel itself."""
+
+__api_version__: Final[int] = 1
+"""Integer version of the loader contract between this wheel and the
+engine. Bumped whenever the engine-side loader must change to keep
+reading this wheel's registrations."""
+
+minimum_engine_version: Final[str] = ">=0.17,<1.0"
+"""PEP 440 specifier naming the engine range this wheel targets. The
+engine consults this string at import time to refuse to boot against
+an incompatible pair (see :mod:`tolokaforge.core.model_data`)."""

tolokaforge_models-1.0.0/src/tolokaforge_models/certificates/__init__.py

@@ -0,0 +1,14 @@
+"""Registry of :class:`tolokaforge.testing.certify.ModelCertificate` instances.
+
+The engine reaches this tuple through
+:func:`tolokaforge.core.model_data.bundled_certificates`, which is
+re-exposed as :data:`tolokaforge.testing.certify.ALL_MODELS` at the
+public certify seam. Adding a new certificate is an edit to
+:mod:`tolokaforge_models.certificates.registry`.
+"""
+
+from __future__ import annotations
+
+from tolokaforge_models.certificates.registry import ALL_MODELS
+
+__all__ = ["ALL_MODELS"]