# 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 deliberately NOT pinned: hosts run 0.2.0 built from git commit
# 14266f0 (direct_url.json), but the index CI uses only has 0.1.0/0.1.1, so a
# pin makes resolution impossible. Pin skskills here once 0.2.0 is published to
# the index.
#
# 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.90
skmemory==0.11.160
cloud9==1.2.4
skwhisper==0.6.6
