# Production dependency set of the fleet runtime: THE single source of truth.
#
# These are the versions installed in ~/.skenv on every chi host (chiap01-04,
# chiap08), verified 2026-10-13. Three consumers read this one file:
#   1. CI installs the package with `pip install -c deploy/fleet-constraints.txt`,
#      so tests run against what production runs, not against the pyproject floor.
#   2. Rollout installs with the same `-c`, so a host is moved to exactly these.
#   3. The rollout gate runs `src/skcapstone/fleet/dependency_parity.py`
#      and halts with DEPENDENCY_DRIFT if an installed version differs.
#
# Scope: only packages CI can install from the same index production used.
# skskills IS pinned as of 2026-11-14: it now has one version source and 1.2.0
# is on PyPI, replacing the 0.2.0 git build the hosts ran.
#
# 2026-11-14, released builds for the rest of the SK set (Chef: "just add the
# packages to it"). Each pin below was dry-run (`pip install --dry-run`) in the
# live venv of every auto-rollout host and moves only the SK package itself,
# replacing the git and editable builds the hosts ran. Held back, because the
# dry run showed them moving third-party packages under running services:
#   skchat-sovereign 0.14.266: Pillow 12 -> 13 and PyJWT everywhere; on
#     chiap08 also fastapi 0.141 -> 0.135 and cryptography 43 -> 50.
#   sksecurity 1.2.8: mcp 1.29 -> 1.30; cryptography on chiap08 and ziowk01.
#   skbrain 1.0.1: downgrades click 8.4 -> 8.1 and typer 0.27 -> 0.12.
#   skvault 0.1.0: would install it plus ten dependencies on hosts that do
#     not use it (only chiap03 and chiap04 have it).
# Pin those in their own PR once the third-party moves are planned.
#
# skwhisper IS pinned as of 2026-10-20. It could not be until then: the index
# carried only 0.1.0 while every chi host ran 0.6.2 from git, because that repo
# had no publish workflow at all. smilinTux/skwhisper#1 added one and a PyPI
# Trusted Publisher was configured, so the fleet release is now on the index
# and the pin matches what the fleet actually runs.
#
# Rules: exact `==` pins only. A pyproject floor must never exceed its pin
# (tests/test_fleet_dependency_parity.py). To bump, see
# docs/fleet/DEPLOY-FROM-MAIN.md "Bumping a fleet dependency": the upstream
# release ships first, then the pin moves in the same PR as the code needing it.
skcoord==0.1.97
skmemory==0.11.162
cloud9==1.2.4
skwhisper==0.6.6
capauth==0.3.14
skseed==0.1.9
skdashboard==0.1.109
skharness==0.3.45
skskills==1.2.0
skcomms==0.2.22
